Learn to design, plan and build frontend applications using a Component-Based approach. You will explore the ReactJS library which is designed to make Component-Based design easy and efficient.
Priorities: 🥚, 🐣, 🐥, 🐔 (click to learn more)
There is a lot to learn in this repository. If you can't master all the material at once, that's expected! Anything you don't master now will always be waiting for you to review when you need it. These 4 emoji's will help you prioritize your study time and to measure your progress:
- 🥚: Understanding this material is required, it covers the base skills you'll need for this module and the next. You do not need to finish all of them but should feel comfortable that you could with enough time.
- 🐣: You have started all of these exercises and feel you could complete them all if you just had more time. It may not be easy for you but with effort you can make it through.
- 🐥: You have studied the examples and started some exercises if you had time. You should have a big-picture understanding of these concepts/skills, but may not be confident completing the exercises.
- 🐔: These concepts or skills are not necessary but are related to this module. If you are finished with 🥚, 🐣 and 🐥 you can use the 🐔 exercises to push yourself without getting distracted from the module's main objectives.
- recreate an HTML/CSS web page using pure functions components and encapsulated styles
🥚 JSX : you can ...
- Write elements with JSX syntax
- functional React components
- render a static page with provided data
- component props
- splitting components with design in mind
🥚functional React components: you can ...
-
Create a React function component (both function definition and arrow function styles)
-
Import/export components between files
🥚 Render data: you can
- Use interpolation ({}) to insert JavaScript expressions into JSX
- Render a list using the
.mapmethod
🥚 Components and props : you can ...
- create small, reusable components
- how to pass props into React components
🥚 Create reusable components: you can ...
- Nest components within other components
- one folder with a main component
- sub-components for your convenience (not part of public contract)
- VDOM
- what is a hook
useStateuseEffect(any side-effect)- component lifecycle
🥚VDOM : you ....
- can differenciate the real dom from the virtual dom
- know what reconciliation process is ..
🥚 Hook
- simple, just enough for the flavor
- the react docs "rules of hooks"
🥚 use-state
🥚 use-effect
🥚 component lifecycle
- create components that manage internal state and emit custom events
- handling events
- build reusable components that take functions as arguments
- child components communicating with parent components
- passing functions as props
- splitting components with logic in mind
- why create dumb components when hooks can be anywhere?
- re-render cycles (all children)
- why putting state at lower levels is efficient
- why not to use everything in global state
- fetch and use API data in components
- async
useEffectcallbacks
- react router
- being careful about what you put in
useContext- only move data to context when it's necessary
- store and manage global app state shared between components
useContext- shared state, not the same as
useState
- shared state, not the same as
- other state management systems/strategies exist
React is a big library with a lot of history and different ways of doing things. To help you be productive faster, you'll only be learning a small part of everything React can do.
JSX is not actually part of React, but they're almost always used together
- props
- importing local style sheets
- handling
- dispatching
useStateuseContextuseEffect
not part of the core React library
The wild world of React is full of different ways to structure applications and organize your code. You'll be learning one way to do things, this architecture is simple enough to learn in a couple weeks and capable enough to build a final project.
/react project
/public
/src
/api-calls
- functions that fetch and process API data
/components
- React components
- more important to talk about the decision process
than suggesting a specific folder structure
/shared
don't force it, let it happen
/Component
Component.jsx
SubComponent.jsx
styles.css
App.jsx
<header>
<routes>
<footer>
/context
- initialize React context with ../data
/data
- initial app state
/utils
- testable logic functions
/LICENSE
/package.json
/README.md- React component files are Pascal Case
- React component functions are Pascal Case
- React component files have the .jsx extension
- all other files & folders are Kebab Case
- all other functions are Camel Case
expand/collapse
- Don't rush, understand! Programming is hard.
- The examples and exercises will still be there to study later.
- It's better to fail tests slowly and learn from your mistakes than to pass tests quickly and not understand why.
- Don't skip the examples! Understanding and experimenting with working code is a very effective way to learn programming.
- Write lots of comments in the examples and exercises. The code in this repository is yours to study, modify and re-use in projects.
- Practice Pair Programming: two people, one computer.
- Take a look through the Learning From Code guide for more study tips
Creating a project board on your GitHub account for tracking your study at HYF
can help you keep track of everything you're learning. You can create the board
at this link: https://github.com/your_user_name?tab=projects.
These 4 columns may be helpful:
- todo: material you have not studied yet
- studying: material you are currently studying
- to review: material you want to review again in the future
- learned: material you know well enough that you could help your classmates learn it
You will need NPM installed on your computer to study this material
- Clone this repository:
- using SSH:
git clone --depth 1 [email protected]:HackYourFutureBelgium/component-based-design.git
- using SSH:
- navigate to the cloned repository
cd component-based-design
- Install dependencies:
npm install