# Asabeneh/30-Days-Of-React: A 30-Day Markdown Course for Learning React > The repository is a day-by-day React curriculum written as Markdown lessons, from a JavaScript refresher to hooks and context. It is a reading-and-exercise course, not a package, and its value depends on whether you want a fixed 30-day path or a reference you dip into. **Asabeneh/30-Days-Of-React** — 30 Days of React challenge is a step by step guide to learn React in 30 days. These videos may help too: https://www.youtube.com/channel/UC7PNRuno1rzYPb1xLa4yktw - Repository: https://github.com/Asabeneh/30-Days-Of-React - Stars: 27,506 · Forks: 7,665 - Language: JavaScript - License: not declared - Published: 2026-09-21 · Updated: 2026-09-21 · Language: en - Canonical page: https://hysenlabs.com/projects/asabeneh-30-days-of-react ## What 30 Days Of React Is, and Who It Is Written For This is a curriculum stored as a repository. The table in readMe.md maps 30 numbered days to topics: Day 1 is a JavaScript refresher, Day 2 introduces React, Day 3 covers setup, and the sequence runs through components, props, list rendering and keys, class components, state, conditional rendering, events, forms, controlled versus uncontrolled inputs, component life cycles, third-party packages, higher order components, React Router, fetch versus Axios, two project days, hooks, forms with hooks, fetching data with hooks, a hooks project, custom hooks, context, refs, a further project, an explore day, and conclusions. The intended reader is someone who can already write JavaScript and wants a fixed order rather than a topic index. The author is named in the README as Asabeneh Yetayeh, with the material dated October 2020. That date matters more than any feature list: the lesson plan predates a large part of the modern React API surface, and the repository carries no releases, so there is no changelog telling you which lessons were revised and which were left as written. It is also explicitly a challenge format. The README's own workflow section tells you to star and fork the repository, clone your fork, create a new branch, structure your exercise solutions, commit them, and update your fork daily. The course expects you to produce artifacts in your own fork, not just read. ## How the Course Is Structured: Markdown Files, One Folder Per Day There is no build system, no package.json at the root, and no application to run. The top level of the repository is 30 numbered directories, from 01_Day_JavaScript_Refresher through 30_conclusions, plus an images directory, a .github directory, a .gitignore, and readMe.md. Each directory holds the lesson for that day, and the lesson files are Markdown: 01_javascript_refresher.md, 02_introduction_to_react.md, 03_setting_up.md, 04_components.md, 05_props.md, and so on through the sequence. The flow is therefore manual and linear. You open a file, read the explanation, and where the lesson asks for code you write it yourself, either in the browser console as the setup section describes or in your own project. The README's table of contents links each day to its Markdown file, and the first link at the top of the README points to Day 1, so the intended entry point is the beginning rather than a search. The exercises are what make it a course rather than a set of notes. The README devotes a section to structuring exercise solutions and committing them, which implies the author expects a per-day commit history in your fork. That is a reasonable design for accountability, but it also means the repository's own contribution model is about your fork, not about pull requests back into the course. ## Setting Up and Starting Day 1 in Practice Because this is a reading course, getting started means cloning your fork and opening the first lesson. The README's workflow section covers starring and forking the repo, cloning your fork, creating a new branch, structuring exercise solutions, committing them, and updating your fork daily. The README does not print the literal git commands, so the concrete first step it describes is the fork on GitHub followed by a clone of your own copy. The README's Setup section is titled Install Node.js, and the browser subsection walks through installing Google Chrome, opening the Chrome console, and writing code there. The console examples start with console.log, then console.log with multiple arguments, comments, and syntax, before moving into arithmetic. Day 1 itself is the JavaScript refresher, so the first real use is not React at all: you open the refresher file and work through it. The lesson files are named in the repository's directory listing, so the entry point for Day 1 is 01_Day_JavaScript_Refresher/01_javascript_refresher.md, and the React-specific setup arrives later, in 03_Day_Setting_Up/03_setting_up.md. The README does not document a single scaffolding command for the whole course. Expect to create project directories yourself as the later days require them, and expect the browser console described in the setup section to be where the earliest examples run. ## The Version Gap Is the Real Limitation The README dates the material to October 2020, and the day list reflects that. Day 14 is Component Life Cycles, Day 16 is Higher Order Components, and the hooks material does not begin until Day 21. Class components get a full day of their own on Day 7, before state on Day 8. A reader in 2026 will spend a meaningful share of the course on patterns that are now taught mainly for reading legacy code rather than for writing new code. That is not a defect in the writing, but it is a constraint on how you use it. If your goal is to be productive in a current React codebase in 30 days, the ordering works against you: hooks, context and custom hooks sit in the final third, after two project days and a life cycle day. A reader who stops at Day 15 has learned class components and third-party packages and almost no hooks. The second limitation is the absence of releases. There are no release notes to tell you what changed after 2020, and the README does not document a revision history for individual lessons. You cannot tell from the repository metadata whether Day 21 was updated for a newer API or left as originally written. Treat every code example as a 2020 example and check it against current documentation before copying it into a project you intend to maintain. The third limitation is scope. There is no testing day, no TypeScript day, and no build-tooling day in the list. If your team's React work happens in a typed codebase with a test suite, this course does not cover the parts you will spend most of your time on. ## How It Compares to the Official React Documentation The alternative most readers should weigh is the official React documentation, which is maintained by the React team and tracks the current API. The difference in approach is structural rather than editorial. The official docs are organized by concept and are revised alongside releases; this repository is organized by day and is frozen at a 2020 snapshot with no releases. That gives each a different job. The official documentation is the right place to check whether a specific hook or API still behaves the way a lesson says it does, because it is the source that changes when React changes. This repository is the right place to get a fixed sequence with exercises and a commit-per-day rhythm, because the order never shifts under you mid-course. The practical arrangement is to use this course for the schedule and the official documentation for verification. The repository's own README points readers to an accompanying YouTube channel for videos, which suggests the author intended the text to be paired with outside material rather than used alone. ## Maintenance, Licence and Upgrade Cost The repository is not archived, and the last push was on 2026-08-27, so it is still receiving changes. That is a weaker signal than it sounds. There are no retrieved releases, so there is no versioned artifact to upgrade and no changelog to read. Your upgrade cost is the cost of re-reading lessons that changed since you last opened them, and the repository gives you no release notes to make that cheap. If you fork it, you can diff your fork against master, which is the only reliable way to see what moved. The licence is listed as unknown in the repository metadata, and the README does not state one. That is a real consideration rather than a formality: without a licence file, the default copyright position applies, and reusing the lesson text in your own training material or internal documentation is not something the repository grants you permission to do. Check the repository for a licence before you republish any part of the lessons. This is not legal advice, and if you plan to redistribute the content you should get your own answer. The README describes sponsorship through GitHub Sponsors and PayPal, which tells you how the author funds the work but does not change the licence position of the text. ## Conclusion Use it if you already know some JavaScript and want a dated, sequential curriculum you can read and fork, with a Git workflow built into the instructions. Do not adopt it if you need versioned release notes, a package you can install, or a course that tracks React 19 API changes, because the repository has no releases and its lessons were authored in October 2020. Before committing 30 days, open 21_Introducing_Hooks/21_introducing_hooks.md and 26_Context/26_context.md and check whether the examples match the React version you actually intend to ship. ## FAQ ### Can I learn React in 3 months with Asabeneh/30-Days-Of-React? The repository is built as a 30-day sequence, with one folder per day from a JavaScript refresher through hooks, context and refs, so a three-month pace gives you roughly three days per lesson if you want to spread it out. The README does not prescribe a pace beyond the daily framing, and the exercise workflow expects you to commit solutions to your own fork. ### Is learning React still worth it in 2026 if I follow this course? The repository does not make a claim about React's current standing, and the course material is dated October 2020. What it does offer is a fixed order of topics, from components and props through hooks, React Router and fetch versus Axios, with project days at 19, 20, 24 and 28. Whether that order matches what you need depends on your target codebase. ### Can I learn React in 1 week with Asabeneh/30-Days-Of-React? The course is structured as 30 days, with the first day a JavaScript refresher and the React introduction on Day 2, so compressing it into a week means skipping the pacing the repository was designed around. You could read the Markdown files faster, but the exercise workflow in the README assumes you commit solutions day by day. ### Is React 18 end of life, and does this course cover it? The repository does not discuss React 18 or its support status, and the README dates the material to October 2020, which predates that release. The day list covers class components, life cycles, hooks, context and refs, but it does not name a React version anywhere. ## Sources - [Asabeneh/30-Days-Of-React on GitHub](https://github.com/Asabeneh/30-Days-Of-React) - [Issues](https://github.com/Asabeneh/30-Days-Of-React/issues) - [README](https://github.com/Asabeneh/30-Days-Of-React/blob/master/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/asabeneh-30-days-of-react