Rename homework to assignments

Author: robvk

.gitignore

@@ -1,6 +1,6 @@
 .DS_Store
 bin
-homework-solution
+assignments-solution
 node_modules
 npm-debug.log
 package-lock.json

.vscode/launch.json

@@ -7,20 +7,20 @@
     {
       "type": "node",
       "request": "launch",
-      "name": "Launch Week 1 - Homework",
-      "program": "${workspaceFolder}/week1/homework/src/index.js",
-      "cwd": "${workspaceFolder}/week1/homework"
+      "name": "Launch Week 1 - Assignments",
+      "program": "${workspaceFolder}/week1/assignments/src/index.js",
+      "cwd": "${workspaceFolder}/week1/assignments"
     },
     {
       "type": "node",
       "request": "launch",
-      "name": "Launch Week 1 - Homework Tests",
-      "program": "${workspaceRoot}/week1/homework/node_modules/ava/profile.js",
+      "name": "Launch Week 1 - Assignments Tests",
+      "program": "${workspaceRoot}/week1/assignments/node_modules/ava/profile.js",
       "args": [
         "--concurrency=1",
         "--no-color",
         "--serial",
-        "${workspaceRoot}/week1/homework/test/server.test.js"
+        "${workspaceRoot}/week1/assignments/test/server.test.js"
       ],
       "skipFiles": [
         "<node_internals>/**/*.js"

README.md

@@ -43,22 +43,22 @@ Verify the installation by running `node -v` (-v is short for version) from the
 
 This repository consists of 3 essential parts:
 
-1. `README`: this document contains all the required theory you need to understand **while** working on the homework. It contains not only the right resources to learn about the concepts, but also lectures done by HackYourFuture teachers. This is the **first thing** you should start with every week
-2. `MAKEME`: this document contains the instructions for each week's homework. Start with the exercises rather quickly, so that you can ground the concepts you read about earlier.
+1. `README`: this document contains all the required theory you need to understand **while** working on the assignments. It contains not only the right resources to learn about the concepts, but also lectures done by HackYourFuture teachers. This is the **first thing** you should start with every week
+2. `MAKEME`: this document contains the instructions for each week's assignments. Start with the exercises rather quickly, so that you can ground the concepts you read about earlier.
 3. `LESSONPLAN`: this document is meant for teachers as a reference. However, as a student don't be shy to take a look at it as well!
 
 ### How to study
 
 Let's say you are just starting out with the Node.js module. This is what you do...
 
 1. The week always starts on **Wednesday**. First thing you'll do is open the `README.md` for that week. For the first week of `Node.js`, that would be [Week1 Reading](./week1/README.md)
-2. You spend **Wednesday** and **Thursday** going over the resources and try to get a basic understanding of the concepts. In the meanwhile, you'll also implement any feedback you got on last week's homework (from the Using API's module)
-3. On **Friday** you start with the homework, found in the `MAKEME.md`. For the first week of `Node.js`, that would be [Week1 Homework](/week1/MAKEME.md)
+2. You spend **Wednesday** and **Thursday** going over the resources and try to get a basic understanding of the concepts. In the meanwhile, you'll also implement any feedback you got on last week's assignments (from the Using API's module)
+3. On **Friday** you start with the assignments, found in the `MAKEME.md`. For the first week of `Node.js`, that would be [Week1 Assignments](/week1/MAKEME.md)
 4. You spend **Friday** and **Saturday** playing around with the exercises and write down any questions you might have
 5. **DEADLINE 1**: You'll submit any questions you might have before **Saturday 23.59**, in the class channel
 6. On **Sunday** you'll attend class. It'll be of the Q&A format, meaning that there will be no new material. Instead your questions shall be discussed and you can learn from others
-7. You spend **Monday** and **Tuesday** finalizing your homework
-8. **DEADLINE 2**: You submit your homework to the right channels (GitHub) before **Tuesday 23.59**. If you can't make it on time, please communicate it with your mentor
+7. You spend **Monday** and **Tuesday** finalizing your assignments
+8. **DEADLINE 2**: You submit your assignments to the right channels (GitHub) before **Tuesday 23.59**. If you can't make it on time, please communicate it with your mentor
 9. Start the new week by going back to point 1!
 
 In summary:
@@ -83,10 +83,10 @@ Learn from Andrej in the following playlist of videos he has made for you! (Clic
 
 ## Planning
 
-| Week | Topic                               | Readings                       | Homework                       | Lesson Plan                           |
-| ---: | ----------------------------------- | ------------------------------ | ------------------------------ | ------------------------------------- |
-|   1. | Client-server model, HTTP & Express | [Readings W1](week1/README.md) | [Homework W1](week1/MAKEME.md) | [Lesson Plan W1](week1/LESSONPLAN.md) |
-|   2. | REST, CRUD, API calls, Testing      | [Readings W2](week2/README.md) | [Homework W2](week2/MAKEME.md) | [Lesson Plan W2](week2/LESSONPLAN.md) |
+| Week | Topic                               | Readings                       | Assignments                       | Lesson Plan                           |
+| ---: | ----------------------------------- | ------------------------------ | --------------------------------- | ------------------------------------- |
+|   1. | Client-server model, HTTP & Express | [Readings W1](week1/README.md) | [Assignments W1](week1/MAKEME.md) | [Lesson Plan W1](week1/LESSONPLAN.md) |
+|   2. | REST, CRUD, API calls, Testing      | [Readings W2](week2/README.md) | [Assignments W2](week2/MAKEME.md) | [Lesson Plan W2](week2/LESSONPLAN.md) |
 
 ## Finished?
 

hand-in-homework-guide.md renamed to hand-in-assignments-guide.md

@@ -1,18 +1,18 @@
-# How to hand in homework
+# How to hand in assignments
 
-In this module you'll submit your homework only using GIT and GitHub.
+In this module you'll submit your assignments only using GIT and GitHub.
 
 1. [GitHub](https://www.github.com/HackYourFuture/Node.js)
 
-## 1. GitHub homework guide
+## 1. GitHub assignments guide
 
-<a href="http://www.youtube.com/watch?feature=player_embedded&v=CpYARPYGQU8" target="_blank"><img src="./assets/submit-homework.png" width="400" height="250" alt="HYF Video" /></a>
+<a href="http://www.youtube.com/watch?feature=player_embedded&v=CpYARPYGQU8" target="_blank"><img src="./assets/submit-assignments.png" width="400" height="250" alt="HYF Video" /></a>
 
-Watch the video (by clicking the image) or go through the following walk-through to learn how to submit your homework:
+Watch the video (by clicking the image) or go through the following walk-through to learn how to submit your assignments:
 
 ONE TIME ONLY (START OF EVERY MODULE)
 
-1. Create a [fork](https://help.github.com/en/articles/fork-a-repo) of the homework module repository. For Node.js, the homework module repository is `https://www.github.com/HackYourHomework/Node.js-classXX` where XX is your class number. You do this by using the `fork` option on the top right
+1. Create a [fork](https://help.github.com/en/articles/fork-a-repo) of the assignments module repository. For Node.js, the assignments module repository is `https://www.github.com/HackYourAssignment/Node.js-classXX` where XX is your class number. You do this by using the `fork` option on the top right
 2. Navigate to the URL of the cloned repository (it should be in your personal GitHub account, under "repositories")
 3. Clone the repository, using SSH, to your local machine. You can do this by typing in `git clone <git url>` in the command line
 4. On your local machine, navigate to the folder using the command line
@@ -21,19 +21,18 @@ ONE TIME ONLY (START OF EVERY MODULE)
 EVERY WEEK
 
 1. Do a `git pull` on your main branch to get the latest version.
-2. Create a new branch for each week you have homework. For example, for the week 1 homework for Node create a branch called `YOUR_NAME-w1-Node`. Don't forget to checkout this branch after creating it.
-3. Make your homework!
-4. Once you're finished, add your homework to a commit. Make sure you *only* commit your homework files and nothing else. You can use `git add -p` if you only want to add a couple files. You can always check what is happening with the `git status` command (as one of our mentors always says, it is the console.log of git!). 
-5. Create the commit (`git commit`). Make the commit message meaningful, for example `finished project for homework week1`.
+2. Create a new branch for each week you have assignments. For example, for the week 1 assignments for Node create a branch called `YOUR_NAME-w1-Node`. Don't forget to checkout this branch after creating it.
+3. Make your assignments!
+4. Once you're finished, add your assignments to a commit. Make sure you _only_ commit your assignments files and nothing else. You can use `git add -p` if you only want to add a couple files. You can always check what is happening with the `git status` command (as one of our mentors always says, it is the console.log of git!).
+5. Create the commit (`git commit`). Make the commit message meaningful, for example `finished project for assignments week1`.
 6. Push the branch to your forked repository
 7. On the GitHub page of your forked repository, click on the `create pull request` button. Make sure the `base repository` is your teacher's repository, on branch master
 8. Give the pull request a title in the following format:
 
 ```markdown
-Homework week 1 <Your name>
+Assignments week 1 <Your name>
 ```
 
 9. Submit the pull request from your forked repository branch into the `main` branch
 
 If you have any questions or if something is not entirely clear ¯\\\_(ツ)\_/¯, please ask/comment on Slack!
-

week1/LESSONPLAN.md

@@ -33,7 +33,7 @@ Node.js is a server-side platform, that allows us to use JavaScript to write bac
 Show students how to use Node.js to execute JavaScript files. Start with the following simple example, but explain how this log will be found inside of the command line instead of
 
 ```js
-console.log('Hello World!');
+console.log("Hello World!");
 ```
 
 #### Exercise
@@ -42,14 +42,14 @@ In a new JavaScript file write a function that returns true if a day is a weeken
 
 ```javascript
 function isWeekend(dayOfWeek) {
-  if (dayOfWeek === 'Saturday') return true;
-  if (dayOfWeek === 'Monday') return false;
+  if (dayOfWeek === "Saturday") return true;
+  if (dayOfWeek === "Monday") return false;
   // fill in the rest
 }
 
-console.log('Tuesday is a ' + (isWeekend('Tuesday') ? 'weekend' : 'week day')); // week day
-console.log('Friday is a ' + (isWeekend('Friday') ? 'weekend' : 'week day')); // week day
-console.log('Sunday is a ' + (isWeekend('Sunday') ? 'weekend' : 'week day')); // weekend
+console.log("Tuesday is a " + (isWeekend("Tuesday") ? "weekend" : "week day")); // week day
+console.log("Friday is a " + (isWeekend("Friday") ? "weekend" : "week day")); // week day
+console.log("Sunday is a " + (isWeekend("Sunday") ? "weekend" : "week day")); // weekend
 ```
 
 Execute the file with `node` in the command line.
@@ -153,11 +153,11 @@ In a new folder:
 Create a JavaScript file called `server.js`, with the following code:
 
 ```javascript
-const express = require('express');
+const express = require("express");
 const app = express();
 const PORT = 3000;
 
-app.get('/', (req, res) => res.send('Hello World!'));
+app.get("/", (req, res) => res.send("Hello World!"));
 
 app.listen(PORT, () => console.log(`Example app listening on port ${PORT}!`));
 ```
@@ -176,7 +176,7 @@ Write an Express app that serves the following HTML:
   <body>
     <h1>Things to do</h1>
     <ul>
-      <li>Write homework</li>
+      <li>Write assignments</li>
       <li>Buy groceries</li>
       <li>Prepare dinner</li>
       <li>Watch movie</li>
@@ -185,32 +185,38 @@ Write an Express app that serves the following HTML:
 </html>
 ```
 
-
 #### Essence
 
 Express.js is used to easily create web servers, that allow us (among other reasons) to serve HTML so our browser can read it. The browser sends a request to a specific address, like `/`, and our server (through Express) responds with an HTML file.
 
 ### 5. Serving static files with Express
 
 #### Explanation
+
 Motiviation based on previous exercise where HTML code is put in the javascript. Instead of doing this, the HTML can be saved in a file in the project and then send with express when needed.
 
 #### Example
+
 Save the HTML content in a new file in the project e.g. `index.html`. Then modify the javascript code to serve the HTML from the file instead of having it hardcoded.
+
 ```javascript
-const express = require('express');
+const express = require("express");
 const app = express();
 const PORT = 3000;
 
-app.get('/', (req, res) => res.sendfile('index.html'));
+app.get("/", (req, res) => res.sendfile("index.html"));
 
 app.listen(PORT, () => console.log(`Example app listening on port ${PORT}!`));
 ```
 
 #### Exercise
+
 ```css
-li:nth-child(even) {background-color: #CCC}
+li:nth-child(even) {
+  background-color: #ccc;
+}
 ```
+
 If time left: Save the above css in a file `style.css`.
 Link the stylesheet in the HTML file. Extend the express app to return the sylesheet for route `\style.css`.
 

week1/MAKEME.md

@@ -1,4 +1,4 @@
-# Homework Node.js Week 1
+# Assignments Node.js Week 1
 
 ## Todo List
 
@@ -46,7 +46,7 @@ Inside of your `Node.js` fork, go to the folder `week1`. Inside of that folder,
 
 ## **5. PROJECT: HackYourTemperature I**
 
-> In this part of the homework you'll be setting up the basis of your project: `HackYourTemperature`. Inside the folder `homework`, create a new folder called `hackyourtemperature`. You'll add to it every week.
+> In this part of the assignments you'll be setting up the basis of your project: `HackYourTemperature`. Inside the folder `assignments`, create a new folder called `hackyourtemperature`. You'll add to it every week.
 
 In this module you'll be building the simplest of API's, starting from scratch.
 
@@ -76,9 +76,9 @@ If you are tired of constantly restarting your server, google the `nodemon` pack
 
 ## **SUBMIT YOUR HOMEWORK!**
 
-After you've finished your todo list it's time to show us what you got! Have a look at the following [guide](../hand-in-homework-guide.md) to see how it's done.
+After you've finished your todo list it's time to show us what you got! Have a look at the following [guide](../hand-in-assignments-guide.md) to see how it's done.
 
-The homework that needs to be submitted is the following:
+The assignments that needs to be submitted is the following:
 
 1. Project: HackYourTemperature I
 

week1/README.md

@@ -44,7 +44,7 @@ It is time to start practicing interviews as it is a big part of the hiring proc
 You don't have to do all of this at this moment. This week you will get a message in your class channel about when the Career Training 2 session will be. _Before_ that session make sure to have:
 
 - Read the whole [‘Interview Preparation’ Repo](https://github.com/HackYourFuture/interviewpreparation).
-- Done the homework: make a copy of [this file](https://docs.google.com/document/u/2/d/114rTGS4eG6tpkrMAyVIdvgTrnpmkRL6ax_smkw1B0HI/copy) and submit your answers to the team [here](https://hackyourfuture.typeform.com/to/s6zYAugm).
+- Done the assignments: make a copy of [this file](https://docs.google.com/document/u/2/d/114rTGS4eG6tpkrMAyVIdvgTrnpmkRL6ax_smkw1B0HI/copy) and submit your answers to the team [here](https://hackyourfuture.typeform.com/to/s6zYAugm).
 
 ## Extra reading
 

week2/MAKEME.md

@@ -1,4 +1,4 @@
-# Homework Node.js Week 2
+# Assignments Node.js Week 2
 
 ## Todo List
 
@@ -25,7 +25,7 @@ Inside of your `Node.js` fork, go to the folder `week2`. Inside of that folder,
 
 So far you've build a basic web server. We've loaded in the necessary modules. We have an `end point`, which is `/`. We have activated the server, by `listening` to a port number. And we have created a `POST` request to handle input from the user.
 
-This week's homework we will expand on that, in 2 parts:
+This week's assignments we will expand on that, in 2 parts:
 
 1. We will connect our API to an external API to grab the data we want.
 2. We are going to add tests to our API to ensure that it works as intended.
@@ -143,7 +143,7 @@ Enjoy!
 Remember that the Career Training 2 session is coming up (check your class channel on slack for the exact date). Before the session make sure you have:
 
 - Read the whole [‘Interview Preparation’ Repo](https://github.com/HackYourFuture/interviewpreparation).
-- Done the homework: make a copy of [this file](https://docs.google.com/document/u/2/d/114rTGS4eG6tpkrMAyVIdvgTrnpmkRL6ax_smkw1B0HI/copy) and submit your answers to the team [here](https://hackyourfuture.typeform.com/to/s6zYAugm).
+- Done the assignments: make a copy of [this file](https://docs.google.com/document/u/2/d/114rTGS4eG6tpkrMAyVIdvgTrnpmkRL6ax_smkw1B0HI/copy) and submit your answers to the team [here](https://hackyourfuture.typeform.com/to/s6zYAugm).
 
 ## **6. Optional: Side project ideas**
 
@@ -169,9 +169,9 @@ We focused solely on the REST way of building an API, but there is a different w
 
 After you've finished your todo list it's time to show us what you got! Upload all your files to your forked repository (same as week 1). Then make a pull request to it.
 
-If you need a refresher, take a look at the following [guide](../hand-in-homework-guide.md) to see how it's done.
+If you need a refresher, take a look at the following [guide](../hand-in-assignments-guide.md) to see how it's done.
 
-The homework that needs to be submitted is the following:
+The assignments that needs to be submitted is the following:
 
 1. Project: HackYourTemperature II