Skip to content

Commit

Permalink
add progress3
Browse files Browse the repository at this point in the history
  • Loading branch information
firasm committed Jun 8, 2024
1 parent 95afbe7 commit 9c93c8c
Show file tree
Hide file tree
Showing 2 changed files with 64 additions and 0 deletions.
1 change: 1 addition & 0 deletions _toc.yml
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,7 @@ parts:
- file: notes/project/team_formation
- file: notes/project/progress01
- file: notes/project/progress02
- file: notes/project/progress03

- caption: Course Feedback
chapters:
Expand Down
63 changes: 63 additions & 0 deletions notes/project/progress03.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
# Progress 3

## Project Requirements:

Must be completed with your group before Workshop 4.

- Begin to **add Redux** to your app. Think of the main type of data you will be storing (e.g. list of recipes, list of songs) and think about how you would like this data to be “connected” to your components.
- Put some **default data** in your reducer(s). (Later it will be stored in the DB.)
- Connect the default data to at least one component in order to **display** it. Note: You have probably already made some components from the previous project work, so now just make sure at least one of them is rendering based on what is in your store.
- Create a minimum of **3 actions** that manipulate your store (e.g. adding a message, deleting a message, etc.)
- Finally, be able to demonstrate that you have made progress toward completing more of your **minimal goals**!

```{note}
You may certainly borrow code from your assignment, but make sure you’re showing us new code that you’ve written specifically for your project!
```

```{tip}
Remember: These requirements are very minimal and are here to make sure that you are making forward progress on the project. We encourage you to make progress beyond the requirements in order to create an awesome project!
```

## How to hand in:

When you are ready, create a branch titled “project_3. Push your finalized code to that branch. Do not push to this branch after 10AM PT on the day of Workshop 4.















## First steps

Set up your project with React. Use Vite to set up a React project following the instructions in Workshop 2. Once the boilerplate code has been set up, do an initial push to your project repo that you have set up with your group. It could take some git gymnastics to make it work. Make sure your README does not get overwritten! (Or copy it over to a new repo)


## Project Requirements:

Must be completed with your group before Workshop 3.

- Begin to flesh out the **component structure** of your app, focusing on one key task. <u>For now, you will start with the view, and don’t have to worry about the functional aspects</u>.
- Create a **component** for the main “item” in your app and display it (e.g. recipe, song listing, posting, event) _Note: If you don’t have a main “item” in your app, then pick an aspect to focus on + really develop the UI for it._

- Add effective **styling** for this “main item”. Try to “complete” a piece of your prototypes.
- In total, have a minimum of **5 components** other than App.js. (One of them will be your “main item” mentioned above.)

- Finally, be able to demonstrate that you have made progress toward completing one (or some) of your minimal goal(s)!

- [OPTIONAL] Begin to add Redux setup to your app.

**Note:** You may certainly borrow code from your assignment, but make sure you’re showing us new code that you’ve written specifically for your project!

**Remember:** These requirements are __very__ **minimal** and are here to make sure that you are making forward progress on the project. We encourage you to make progress beyond the requirements in order to create an awesome project!

## How to hand in:
When you are ready, create a branch titled “project_2”. Push your finalized code to that branch. Do not push to this branch after 10AM PT on June 8th (beginning of Workshop 3).

0 comments on commit 9c93c8c

Please sign in to comment.