Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/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
https://github.com/asabeneh/30-days-of-react
30dayofjavascript challenge css html html5 javascript js programming react react-router-dom reactjs redux webdevelopment website
Last synced: about 3 hours ago
JSON representation
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
- Host: GitHub
- URL: https://github.com/asabeneh/30-days-of-react
- Owner: Asabeneh
- Created: 2020-09-29T13:38:54.000Z (almost 4 years ago)
- Default Branch: master
- Last Pushed: 2024-04-15T20:43:06.000Z (5 months ago)
- Last Synced: 2024-04-24T15:22:56.771Z (5 months ago)
- Topics: 30dayofjavascript, challenge, css, html, html5, javascript, js, programming, react, react-router-dom, reactjs, redux, webdevelopment, website
- Language: JavaScript
- Homepage:
- Size: 17.6 MB
- Stars: 24,278
- Watchers: 375
- Forks: 6,916
- Open Issues: 221
-
Metadata Files:
- Readme: readMe.md
Awesome Lists containing this project
README
[Day 1 >>](./01_Day_JavaScript_Refresher/01_javascript_refresher.md)
| # Day | Topics |
| ----- | :-------------------------------------------------------------------------------------------------------------------------: |
| 00 | [Introduction](#introduction)
[How to Use Repo](#how-to-use-repo)
[Requirements](#requirements)
[Setup](#setup) |
| 01 | [JavaScript Refresher](./01_Day_JavaScript_Refresher/01_javascript_refresher.md) |
| 02 | [Getting Started React](./02_Day_Introduction_to_React/02_introduction_to_react.md) |
| 03 | [Setting Up](./03_Day_Setting_Up/03_setting_up.md) |
| 04 | [Components](./04_Day_Components/04_components.md) |
| 05 | [Props](./05_Day_Props/05_props.md) |
| 06 | [List, Map and Keys](./06_Day_Map_List_Keys/06_map_list_keys.md) |
| 07 | [Class Components](./07_Day_Class_Components/07_class_components.md) |
| 08 | [States](./08_Day_States/08_states.md) |
| 09 | [Conditional Rendering](./09_Day_Conditional_Rendering/09_conditional_rendering.md) |
| 10 | [React Project Folder Structure](./10_React_Project_Folder_Structure/10_react_project_folder_structure.md) |
| 11 | [Events](./11_Day_Events/11_events.md) |
| 12 | [Forms](./12_Day_Forms/12_forms.md) |
| 13 | [Controlled and Uncontrolled Component](./13_Day_Controlled_Versus_Uncontrolled_Input/13_uncontrolled_input.md) |
| 14 | [Component Life Cycles](./14_Day_Component_Life_Cycles/14_component_life_cycles.md) |
| 15 | [Third Party Packages](./15_Third_Party_Packages/15_third_party_packages.md) |
| 16 | [Higher Order Components](./16_Higher_Order_Component/16_higher_order_component.md) |
| 17 | [React Router](./17_React_Router/17_react_router.md) |
| 18 | [Fetch versus Axios](./18_Fetch_And_Axios/18_fetch_axios.md) |
| 19 | [Projects](./19_projects/19_projects.md) |
| 20 | [Projects](./20_projects/20_projects.md) |
| 21 | [Hooks](./21_Introducing_Hooks/21_introducing_hooks.md) |
| 22 | [Forms Using Hook](./22_Form_Using_Hooks/22_form_using_hooks.md) |
| 23 | [Fetching Data Using Hooks](./23_Fetching_Data_Using_Hooks/23_fetching_data_using_hooks.md) |
| 24 | [Project using Hooks](./24_projects/24_projects.md) |
| 25 | [Custom Hooks](./25_Custom_Hooks/25_custom_hooks.md) |
| 26 | [Context](./26_Context/26_context.md) |
| 27 | [Ref](./27_Ref/27_ref.md) |
| 28 | [project](./28_project/28_project.md) |
| 29 | [Explore](./29_explore/29_explore.md) |
| 30 | [Conclusions](./30_conclusions/30_conclusions.md) |
🧡🧡🧡 HAPPY CODING 🧡🧡🧡
Support the author to create more educational materials
---
- [Introduction](#introduction)
- [Requirements](#requirements)
- [How to Use Repo](#how-to-use-repo)
- [Star and Fork this Repo](#star-and-fork-this-repo)
- [Clone your Fork](#clone-your-fork)
- [Create a New Branch](#create-a-new-branch)
- [Structure Exercise Solutions](#structure-exercise-solutions)
- [Commit Exercise Solutions](#commit-exercise-solutions)
- [Update your Fork Daily](#update-your-fork-daily)
- [Setup](#setup)
- [Install Node.js](#install-nodejs)
- [Browser](#browser)
- [Installing Google Chrome](#installing-google-chrome)
- [Opening Google Chrome Console](#opening-google-chrome-console)
- [Writing Code on Browser Console](#writing-code-on-browser-console)
- [Console.log](#consolelog)
- [Console.log with Multiple Arguments](#consolelog-with-multiple-arguments)
- [Comments](#comments)
- [Syntax](#syntax)
- [Arithmetics](#arithmetics)
- [Code Editor](#code-editor)
- [Installing Visual Studio Code](#installing-visual-studio-code)
- [How to Use Visual Studio Code](#how-to-use-visual-studio-code)
---
## Introduction
**Congratulations** on deciding to participate in 30 days of React programming challenge. In this challenge you will learn everything you need to use to develop a React application. In the end of the challenge you will get a 30DaysOfReact programming challenge completion certificate. In case you need help or if you would like to help others you may join the [telegram group](https://t.me/thirtydaysofreact).
**A 30DaysOfReact** challenge is a guide for both beginners and advanced JavaScript and React developers. Welcome to 30 Days Of React. React is a JavaScript library. I enjoy using and teaching React and I hope you will do so too.
In this step by step 30 Days React challenge, you will learn React which is one of most popular user interface JavaScript libraries.
React can do everything that JavaScript can do. React can be used **_to add interactivity to websites, to develop mobile apps, desktop applications, games_**.
I believe you will learn quite a lot in the next 30 days and your programming and problem solving skills will also be improved significantly.
I will use conversational English and less jargons to write this challenge. The content will be continuously updated. If you find a typo or grammar mistakes don't be surprised because I don't do any proof read before I publish it. I would recommend you to focus on the main message of the challenge instead of the English and some minor mistakes. I really appreciate if you send me pull requests for improvement and remember to pull first from master before you send pull requests. Most of the images I have used in this challenge came from 30DaysOfJavaScript challenge therefore you may need to rename file names and folders 30DaysOfReact.
If you are good at arrays, loops, functions, objects, functional programming, destructuring and spreading and class then you will be able to follow the challenge properly. Otherwise, I strongly recommend you to check [30DaysOfJavaScript](https://github.com/Asabeneh/30-Days-Of-JavaScript).
Before you dive into this course, you may check the [review](https://t.me/thirtydaysofreact) of 30 Days Of React.
This challenge is easy to read, written in conversational English, engaging, motivating and at the same time, it is very demanding. You need to allocate much time to finish this challenge. If you are a visual learner, you may get the video lesson on Washera YouTube channel. Subscribe the channel, comment and ask questions on YouTube vides and be proactive, the author will eventually notice you.
The author likes to hear your opinion about the challenge, share your thoughts about the 30DaysOfJavaScript challenge. You can leave your testimonial on this [link](https://testimonial-vdzd.onrender.com/)
## Requirements
To get along with the challenge you need to have the following:
1. Motivation
2. A computer
3. Internet
4. A browser
5. A code editor
6. HTML, CSS and JavaScript intermediate level skill
## How to Use Repo
### Star and Fork this Repo
Star this repo to support this work and Fork the repo to create your own copy to work from.
### Clone your Fork
You should always work directly from your forked copy.
```bash
# note that an `ssh` link is used here, but an `https` link will work the same
git clone [email protected]:username/30-Days-Of-React.git
cd 30-Days-Of-React
```
### Create a New Branch
To complete daily exercises, my suggestion is to create a separate branch to house your exercise folder or any other changes you make. This will keep your master branch clean at all times, which means your master will always be similar to the original master.
```bash
git checkout -b exercise-solutions # `-b` creates the branch if it does not exist
```
### Structure Exercise Solutions
In your new branch, you can use files/folders to structure your solutions to daily exercises
```bash
mkdir -p solutions/day-01 # `-p` helps create nested directories
touch solutions/day-01/level1.js # touch creates a file
```
### Commit Exercise Solutions
Commit your solutions to your Fork
```bash
git add solutions/day-01/level1.js
git commit -m "chore: exercise level1 complete"
git push origin exercise-solutions # branch `exercise-solutions` was created earlier
```
### Update your Fork Daily
This repo will be updated daily throughout the month. When a new day's content becomes available, you can update your forked copy with the steps below.
```bash
# 1. switch to master branch
git checkout master
# 2. check if your local copy has a link to original `...Asabeneh/30-Days-Of-React.git`
git remote -v
# 3. if not, add a link to original, you can choose any name for the link or use `upstream`
git remote add upstream [email protected]:Asabeneh/30-Days-Of-React.git
# 4. check again to confirm link added
git remote -v
# 5. now you can fetch updates from original repo, assuming you named this `upstream`
git fetch upstream
# 6. merge the updates to your local master branch
git merge upstream/master master
# 7. push the merged updates to your Forked copy on GitHub
git push origin master
```
> Note that the updates are only applied to the master branch. If you wish to update any other branch, repeat steps 6-7 with the branch name. See snippet below for `exercise-solutions` branch
```bash
git merge upstream/master exercise-solutions
git push origin exercise-solutions
```
## Setup
I believe you have the motivation and a strong desire to be a developer, a computer and Internet. In addition to that basic to intermediate level HTML, CSS and JS. If you have those, then you have everything to get started.
### Install Node.js
You may not need node.js right now but you may need it for later. Install [node.js](https://nodejs.org/en/).
After downloading double click and install
We can check if node is installed on our local machine by opening our device terminal or command prompt.
```sh
asabeneh $ node -v
v12.14.0
```
When making this tutorial I was using node version 12.14.0, but now the recommended version of node.js for download is 12.17.0.
### Browser
There are many browsers out there. However, I strongly recommend Google Chrome.
#### Installing Google Chrome
Install [google chrome](https://www.google.com/chrome/) if you do not have one yet. We can write small JavaScript code on the browser console, but we do not use the browser console to develop applications.
#### Opening Google Chrome Console
You can open Google Chrome console either by clicking three dots at the top right corner of the browser, selecting _More tools -> Developer tools_ or using a keyboard shortcut. I prefer using shortcuts.
To open the Chrome console using a keyboard shortcut. It is good to know the shortcut too as a JavaScript and React developer you will spend much time on a browser console and don't be lazy to open it during development.
```sh
Mac
Command+Option+J
Windows/Linux:
Ctl+Shift+J
```
After you open the Google Chrome console, try to explore the marked buttons. We will spend most of the time on the Console. The Console is the place where your JavaScript code goes. The Google Console V8 engine changes your JavaScript code to machine code.
Let us write a JavaScript code on the Google Chrome console:
#### Writing Code on Browser Console
We can write any JavaScript code on the Google console or any browser console. However, for this challenge, we only focus on Google Chrome console. Open the console using:
```sh
Mac
Command+Option+I
Windows:
Ctl+Shift+I
```
##### Console.log
To write our first JavaScript code, we used a built-in function **console.log()**. We passed an argument as input data, and the function displays the output. We passed 'Hello, World' as input data or argument in the console.log() function.
```js
console.log('Hello, World!')
```
##### Console.log with Multiple Arguments
The **console.log()** function can take multiple parameters separated by comma. The syntax looks like as follows:**console.log(param1, param2, param3)**
```js
console.log('Hello', 'World', '!')
console.log('HAPPY', 'NEW', 'YEAR', 2020)
console.log('Welcome', 'to', 30, 'Days', 'Of', 'JavaScript')
```
As you can see from the snippet code above, _console.log()_ can take multiple arguments. It is recommended to use as many console.log() prints to check what is happening in your code but don't keep all console.log() tests on your code forever. Make your life easy by keeping the browser console open.
##### Comments
We add comments to our code. Comments are very important to make code more readable and to leave remarks in our code. JavaScript does not execute the comment part of our code.In JavaScript, any text line starting with // in JavaScript is a comment, and anything enclosed like this /\* \*/ is also a comment.
**Example: Single Line Comment**
// This is the first comment
// This is the second comment
// I am a single line comment
**Example: Multiline Comment**
/\*
This is a multiline comment
Multiline comments can take multiple lines
JavaScript is the language of the web
\*/
##### Syntax
Programming languages are similar to human languages. English or many other language uses words, phrases, sentences, compound sentences and other more to convey a meaningful message. The English meaning of syntax is _the arrangement of words and phrases to create well-formed sentences in a language_. The technical definition of syntax is _the structure of statements in a computer language._ Programing languages have syntax. JavaScript is a programming language and like other programming languages it has its own syntax. If we do not write a syntax that JavaScript understands, it will raise different types of errors. We will explore different kinds of JavaScript errors later. For now, let us see syntax errors.
I made a deliberate mistake. As a result, the console raises syntax errors. Actually, the syntax is very informative. It informs what type of mistake was made. By reading the error feedback guideline, we can correct the syntax and fix the problem. The process of identifying and removing errors from a program is called debugging. Let us fix the errors:
```js
console.log('Hello, World!')
console.log('Hello, World!')
```
So far, we saw how to display text using the _console.log()_. If we are printing text or string using _console.log()_, the text has to be inside the single quotes, double quotes, or a backtick quotes.
**Example:**
```js
console.log('Hello, World!')
console.log('Hello, World!')
console.log(`Hello, World!`)
```
#### Arithmetics
Now, let us practice more writing JavaScript codes using _console.log()_ on google chrome console for number data types.
In addition to the text, we can also do mathematical calculations using JavaScript. Let us do the following simple calculations.
The console can directly take arguments without the **_console.log()_** function. However, it is included in this introduction because most of this challenge would be taking place in a text editor where the usage of the function would be mandatory. You can play around directly with instructions on the console.
```js
console.log(2 + 3) // Addition
console.log(3 - 2) // Subtraction
console.log(2 * 3) // Multiplication
console.log(3 / 2) // Division
console.log(3 % 2) // Modulus - finding remainder
console.log(3 ** 2) // Exponentiation 3 ** 2 == 3 * 3
```
### Code Editor
We can write our codes on the browser console, but it won't do for bigger projects. In a real working environment, developers use different code editors to write their codes. In this 30 days JavaScript challenge, we will be using Visual Studio Code.
#### Installing Visual Studio Code
Visual studio code is a very popular open-source text editor. I would recommend to [download Visual Studio Code](https://code.visualstudio.com/), but if you are in favor of other editors, feel free to follow with what you have.
If you installed Visual Studio Code, let us start using it.
#### How to Use Visual Studio Code
Open the Visual Studio Code by double-clicking its icon. When you open it, you will get this kind of interface. Try to interact with the labeled icons.
Congratulations! You have completed the setup you need to get started with React, but before we dive into React let's do a JavaScript refresher. If you are very comfortable with JavaScript you may skip day 1 JavaScript refresher. The JavaScript refresher section is vast and it may take more than one day. From my experience people usually get stuck in React because their JavaScript knowledge is very shallow therefore to fill that gap all the necessary JavaScript features which can be used in React are covered in the JavaScript refresher section. There are many exercises but you are not required to solve them. Click [here](../30-Days-Of-React/02_Day_Introduction_to_React/02_introduction_to_react.md) if you want skip JavaScript and jump directly into React.
🎉 CONGRATULATIONS ! 🎉
[Day 1 >>](./01_Day_JavaScript_Refresher/01_javascript_refresher.md)
