➪ Before Jumping into React make sure that you're good at Javascript Fundamentals.
⇝ Fundamentals ⇜

➙ Create React app
➙ Function Components
➙ Class Components
➙ JSX
➙ Props
➙ State
➙ useState and useEffect Hooks
➙ Conditional Rendering
➙ Lists and Keys
➙ Building Simple Forms
➙ Composition and Inheritance
⇝ Advanced Topics ⇜

➪ HTTP Requests
➙ Context Refs
➙ Refs
➙ Error Boundaries
➙ Portals

➙ GET
➙ POST
➪ Hooks
➙ useContext
➙ useReducer
➙ useRef
➙ useMemo
➙ useCallback
➙ Custom Hooks

➙ Higher-Order Components
➙ Render Props
➙ Reconciliation
➪ State Management
➙ Redux/Mobx/Recoil
➙ Apollo Client
➙ React Query

➪ Routing
➙ React Location
➙ React Router
➪ Styling
➙ Styled Components
➙ Tailwind CSS
➙ Chakra UI/ Material UI

➪ Forms
➙ Formik
➙ React Hook Form
➪ Testing
➙ Jest + React Testing Library
➙ Cypress

➪ Misc
➙ Gatsby
➙ Next.js
➙ Remix
➙ React native
➪ Resources to Learn React.
https://t.co/gdGj0WZTjy
Inspiration: https://t.co/VzWrITsbLw
🚨 700+ Tools & Resources 🤩
Goldmine🌟 for Developers, Designers, and Creators.

Learn.
Build.
Sell.

I've Curated incredible tools and learning resources for developers, designers & content creators.
https://t.co/2XaQR6ASYw

More from Mohammed Junaid 🎯

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.