You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+20-5Lines changed: 20 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,10 @@
1
-
### How to setup your development environment?
1
+
# How to start working
2
+
3
+
1. Fork this repo and clone it locally. Click [here](https://github.com/developer-job-simulation/html-css-js/fork) to fork this repo.
4
+
2. Fix the issue
5
+
3. Create Pull Request to this repository
6
+
7
+
# How to setup your development environment?
2
8
Before you can begin, you will need git, node, and a text editor.
3
9
4
10
If you are running Windows, we recommend you install and use [Windows Subsystem for Linux](https://docs.microsoft.com/en-us/windows/wsl/about). From your WSL terminal, follow the linux instructions linked below.
@@ -8,7 +14,7 @@ If you are running Windows, we recommend you install and use [Windows Subsystem
8
14
-[Install Text Editor (VSCode)](https://www.theodinproject.com/lessons/foundations-text-editors#vscode-installation)
9
15
10
16
11
-
###How to launch the app locally?
17
+
# How to launch the app locally?
12
18
1. If you haven't already, ensure that your development environment is set up properly. Refer to the section above for tips.
13
19
14
20
2. Fork this repository to your Github account.
@@ -44,17 +50,26 @@ npm run start-json-server
44
50
npm run start
45
51
```
46
52
47
-
###How to start working on an issue?
53
+
# How to start working on an issue?
48
54
49
55
1. If you haven't already, ensure that your app runs locally successfully. Refer to the section above for tips.
50
56
2. Go to `Issues` tab in the repository and pick an issue. If you are just getting started, consider picking one of the issues that are marked as `Easy`.
51
57
3. Thoroughly read issue description and make sure you understand it.
52
58
4. Before writing/modifying any code, create a new branch in your local git. This is best practice in the industry - to create a separate branch for each issue you are working on.
53
59
54
-
### How to send us you work for review
60
+
# Stack
61
+
62
+
This project was built using
63
+
64
+
- Vanilla Javascript
65
+
- HTML
66
+
- CSS
67
+
- Webpack
68
+
69
+
# How to send us you work for review
55
70
Create and submit a pull request to this repository. We personally review each pull request and share our feedback.
56
71
57
-
###How to get help?
72
+
# How to get help?
58
73
59
74
The best way is to ask a question in our Discord community.
0 commit comments