vets-who-code/web-curriculum

subjects and project boards for Vets Who Code troops

Vets Who Code 🔥

Technologies used 🛠️

• HTML 🚀
• CSS 🚀
• JavaScript 🚀
• SASS 🚀

---

How To Use

Install the dependencies

Using NPM:

# Install dependencies
$ npm install

# Listen to changes in CSS Preprocessor files ( SASS files )
$ npm run compile:scss

Once you run npm run compile:scss, then open the index.html inside your favorite browser or using the live server extension.

web-curriculum's Issues

Block 2's Markdown content

Add Block 2's Markdown content

Base README Table of Contents

Overview

Table of Contents helps to provide a simple interface for navigating a file. I propose that the Table of Contents links to the headings in the base README.

Inconsistent formatting in base readme

Overview

The base README has inconsistent formatting. Also, some sections link some don't. The linking strategy should be consistent.

Block 3's Markdown content

Add Block 3's Markdown content

Each week should have a main file

Overview

Each week should have a main file. That way we could standardize links from other places. For example, we could standardize links from the base README to each week's README i.e. [## Week 2 - HTML && CSS](week-01/README.md)

Currently each week's files are broken up by day. I think it's unrealistic to have the curriculum broken up that granularly.

I propose each week have a README.md

Week numbering isn't consistent

Overview

The week numbering isn't consistent and doesn't show in a particular order in the Github repo when looking at the folders. Make the folder naming consistent so that they list from top to bottom.

Recommend consistent naming convention (kebab case for file naming)
https://stackoverflow.com/questions/7273316/what-is-the-javascript-filename-naming-convention

example:

• week-01
• week-02
• week-03

Migrate FE Op Qual Base Readme to web-curriculum

Overview

FE Op Qual was a project developed as a v2 of the web-curriculum. It turned into an over engineered MVP. We'd like to take the good content out of the base readme and move it here.

Out of Scope

Moving modules/activities/md parsing tools over.

test

Divops/Serverless connection

Blocks 1/2 focus mainly on Frontend and building UIs. However, when we hit block 3 we introduce Docker. You can't really dockerize UIs because they're ran in browsers. So what really needs dockerization when it comes to frontend?

• An idea is that we start the course off by having students download and run their dev envs from a Docker container (so as not to even have node on their computers).

Block 1 Markdown Content

Add Block 1's Markdown content