Skip to content

Commit

Permalink
README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
JosephineHYF authored Aug 16, 2023
1 parent 1fa5e83 commit 1306d7b
Showing 1 changed file with 15 additions and 15 deletions.
30 changes: 15 additions & 15 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,36 +25,36 @@ In order to successfully complete this module you will need to master the follow

This repository consists of 2 essential parts per week:

1. `README`: this document contains all the required theory you need to understand **while** working on the homework. It contains the list of concepts that you will want to study this week and points you to your study book to read all about them. 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 assignment. It contains the list of concepts that you will want to study this week and points you to your study book to read all about them. This is the **first thing** you should start with every week
2. `MAKEME`: this document contains the instructions for each week's assignment. Start with the exercises rather quickly, so that you can ground the concepts you read about earlier.

### How to study

Let's say you are just starting out with the Browsers 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 `Browsers`, 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 JavaScript1 module)
3. On **Friday** you start with the homework, found in the `MAKEME.md`. For the first week of `Browsers`, that would be [Week1 Homework](/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
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 `Browsers`, that would be [Reading W1](/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 assignment (from the JavaScript1 module).
3. On **Friday** you start with the assignment, found in the `MAKEME.md`. For the first week of `Browsers`, that would be [Assignment W1](/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 cohort channel.
6. On **Sunday** you'll attend the session. 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 assignment.
8. **DEADLINE 2**: You submit your assignment 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:

![Weekflow](assets/weekflow.png)

To have a more detailed overview of the guidelines, check your class repository, or ask your mentor/class on Slack!
To have a more detailed overview of the guidelines, check your cohort repository, or ask your mentor/cohort on Slack!

## Planning

| Week | Topic | Reading Materials | Homework |
| Week | Topic | Reading Materials | Assignment |
| ---- | ----- | ----------------- | -------- |
| 1. | Document-Object Model (DOM), DOM manipulation, Presentation Module week 1 | [Reading W1](/Week1/README.md) | [Homework W1](/Week1/MAKEME.md) |
| 2. | Presentation Module week 2, Group project week 1! | [Reading W2](/Week2/README.md) | [Homework W2](/Week2/MAKEME.md) |
| 3. | Group project week 2 | [Reading W3](/Week3/README.md) | No individual homework |
| 1. | Document-Object Model (DOM), DOM manipulation, Presentation Module week 1 | [Reading W1](/Week1/README.md) | [Assignment W1](/Week1/MAKEME.md) |
| 2. | Presentation Module week 2, Group project week 1! | [Reading W2](/Week2/README.md) | [Assignment W2](/Week2/MAKEME.md) |
| 3. | Group project week 2 | [Reading W3](/Week3/README.md) | No individual assignment |

## Finished?

Expand Down

0 comments on commit 1306d7b

Please sign in to comment.