Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit be20d9c

Browse files
committed
Removed outdated Step 2 (was: reorg GitHub repo)
1 parent ba46b43 commit be20d9c

File tree

1 file changed

+16
-19
lines changed

1 file changed

+16
-19
lines changed

Week1/MAKEME.md

Lines changed: 16 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,14 @@
22

33
```
44
Topics discussed in class this week:
5-
• Capturing user input
6-
• Basic DOM manipulations [img src, innerHTML]
7-
• Code debugging using the browser
5+
• Capturing user input
6+
• Events
7+
• Basic DOM manipulations (img src, innerHTML)
8+
• Code debugging using the browser
89
• Code commenting
910
• Structuring code files
10-
Scope
11-
State
11+
Code formatting
12+
Handing in homework via PR
1213
```
1314

1415
>[Here](/Week2/README.md) you find the readings you have to complete before the second lecture.
@@ -43,6 +44,7 @@ Week 4
4344
- [Code commenting](./../../../../fundamentals/blob/master/fundamentals/code_commenting.md)
4445
- Structuring code files
4546
- [Code formatting](./../../../../fundamentals/blob/master/fundamentals/code_formatting.md)
47+
- [Handing in homework via PR](../../..//fundamentals/blob/master/fundamentals/homework_pr.md)
4648

4749

4850
## Step 1: Implement feedback
@@ -54,33 +56,27 @@ Your fellow students have provided you with feedback in Trello.
5456
- Implement both feedback from Trello and Github.
5557
- Check on one of your fellow students code and issues and see if her or she implemented their feedback correctly. If there are some things that can be improved make an issue suggesting further improvements. If you think that the feedback has been implemented correctly create a issue saying something like: "nice work you can clear your issues".
5658

57-
## Step 2: Reorganize your GitHub
58-
59-
_Deadline Monday_
60-
61-
Your Github should contain a repository called `hyf-javascript1`. Inside this JavaScript repository you should have three folders, called week1, week2, and week3 (or something similar). Inside these folders you should have the different assignments (a file per exercises). Try and find proper names for the exercises that reflect somehow what is going on in the code. Avoid using spaces in your file names, this makes it harder to "run" you files. Also make sure that all your JavaScript files have a `.js` extension.
62-
63-
## Step 3: Custom DOM manipulation challenge :mortar_board:
59+
## Step 2: Custom DOM manipulation challenge :mortar_board:
6460

6561
_Deadline Saturday_
6662

6763
> **Preparation**: Fork this repository and use the [Homework Pull Request Workflow](../../../../fundamentals/blob/master/fundamentals/homework_pr.md) to hand in your homework.
6864
6965
Modify the (mostly empty) files in the `Week1/homework` folder for this step.
7066

71-
**3.1** Open the `apps.js` and start by declaring an array that contains 10 strings. These strings should be of book titles you have read (or made up) and be lowercase without spaces so that you can use these later as HTML `id` attributes. (Example: _Harry Potter's - The Chamber of Secrets_ -> `harry_potter_chamber_secrets`). Add a console.log statement to output this array to console. (This is for debugging and making sure everything is in order. Delete it later when you're done :))
67+
**2.1** Open the `apps.js` and start by declaring an array that contains 10 strings. These strings should be of book titles you have read (or made up) and be lowercase without spaces so that you can use these later as HTML `id` attributes. (Example: _Harry Potter's - The Chamber of Secrets_ -> `harry_potter_chamber_secrets`). Add a console.log statement to output this array to console. (This is for debugging and making sure everything is in order. Delete it later when you're done :))
7268

73-
**3.2** Open the empty `index.html` and add the required HTML to load the `app.js` file. Open `index.html` in the browser and confirm that the `console.log` statement shows the array. (Open the Chrome Developer Tools and inspect the console.)
69+
**2.2** Open the empty `index.html` and add the required HTML to load the `app.js` file. Open `index.html` in the browser and confirm that the `console.log` statement shows the array. (Open the Chrome Developer Tools and inspect the console.)
7470

75-
**3.3** Remove the temporary `console.log` from step 3.1. Make a function (or functions) that generate a `ul` with `li` elements for each book ID in the array using a `for` loop. Make sure that the function names you choose are an accurate reflection of what they do. As a reminder, here are the recommended [Naming Conventions](https://github.com/HackYourFuture/fundamentals/blob/master/fundamentals/naming_conventions.md).
71+
**2.3** Remove the temporary `console.log` from step 2.1. Make a function (or functions) that generate a `ul` with `li` elements for each book ID in the array using a `for` loop. Make sure that the function names you choose are an accurate reflection of what they do. As a reminder, here are the recommended [Naming Conventions](https://github.com/HackYourFuture/fundamentals/blob/master/fundamentals/naming_conventions.md).
7672

77-
**3.4** Make an object (_not an array!_) containing information for each book. Each property of this object should be another (i.e., nested) object with the book ID you thought up in step 3.1 as a key, and at least the following properties: `title`, `language` and `author`.
73+
**2.4** Make an object (_not an array!_) containing information for each book. Each property of this object should be another (i.e., nested) object with the book ID you thought up in step 2.1 as a key, and at least the following properties: `title`, `language` and `author`.
7874

79-
**3.5** Now change the function from step 3.3 that you used to display the book ID's in a list to take the actual information about the book from the object and display that. Make sure you choose the correct HTML elements for each piece of info, for instance, a heading for the title.
75+
**2.5** Now change the function from step 2.3 that you used to display the book ID's in a list to take the actual information about the book from the object and display that. Make sure you choose the correct HTML elements for each piece of info, for instance, a heading for the title.
8076

81-
**3.6** Beautify your html page with css (use the `style.css` file for that), add sources and alts to each of the images.
77+
**2.6** Beautify your html page with css (use the `style.css` file for that), add sources and alts to each of the images.
8278

83-
**3.7** Find and download book covers for each book and construct a new object which has as keys the book IDs again, and as value the path to the image source (e.g. `{ harry_potter_blabla: './img/harry_potter_blabla.jpg', ... }`).
79+
**2.7** Find and download book covers for each book and construct a new object which has as keys the book IDs again, and as value the path to the image source (e.g. `{ harry_potter_blabla: './img/harry_potter_blabla.jpg', ... }`).
8480

8581
Loop over these entries (_hint: `Object.keys(objectName)` gives you an array containing the keys_). Then write a function which places an image at the corresponding `li` element. Remember that objects are not ordered, so you cannot guarantee that the first key is the first `li` element. (_Hint: you could give each `li` item an `id` tag by modifying the function you made before._)
8682

@@ -94,6 +90,7 @@ Go over your homework one last time:
9490
- Have you used `const` and `let` and avoided `var`?
9591
- Do the variable, function and argument names you created follow the [Naming Conventions](../../../../fundamentals/blob/master/fundamentals/naming_conventions.md)?
9692
- Is your code well-formatted (see [Code Formatting](../../../../fundamentals/blob/master/fundamentals/naming_conventions.md))?
93+
- Have you resolved all issues flagged by ESLint and the spell checker (no wavy red and green underlines in VSCode)?
9794

9895
If the answer is 'yes' to all preceding questions you are ready to follow these instructions:
9996

0 commit comments

Comments
 (0)