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: CONTRIBUTING.md
+12-11Lines changed: 12 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -1,30 +1,26 @@
1
1
<!-- omit in toc -->
2
+
2
3
# Contributing to js-coding-challenges
3
4
4
5
First off, thanks for taking the time to contribute! ❤️
5
6
6
7
All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
7
8
8
9
> And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
10
+
>
9
11
> - Star the project
10
12
> - Tweet about it
11
13
> - Refer this project in your project's readme
12
14
> - Mention the project at local meetups and tell your friends/colleagues
@@ -58,11 +54,13 @@ Depending on how large the project is, you may want to outsource the questioning
58
54
## I Want To Contribute
59
55
60
56
> ### Legal Notice <!-- omit in toc -->
57
+
>
61
58
> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.
62
59
63
60
### Reporting Bugs
64
61
65
62
<!-- omit in toc -->
63
+
66
64
#### Before Submitting a Bug Report
67
65
68
66
A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
@@ -79,16 +77,18 @@ A good bug report shouldn't leave others needing to chase you up for more inform
79
77
- Can you reliably reproduce the issue? And can you also reproduce it with older versions?
80
78
81
79
<!-- omit in toc -->
80
+
82
81
#### How Do I Submit a Good Bug Report?
83
82
84
83
> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to .
84
+
85
85
<!-- You may add a PGP key to allow the messages to be sent encrypted as well. -->
86
86
87
87
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
88
88
89
89
- Open an [Issue](https://github.com/ComputeNepal/js-coding-challenges/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
90
90
- Explain the behavior you would expect and the actual behavior.
91
-
- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
91
+
- Please provide as much context as possible and describe the _reproduction steps_ that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
92
92
- Provide the information you collected in the previous section.
93
93
94
94
Once it's filed:
@@ -99,12 +99,12 @@ Once it's filed:
99
99
100
100
<!-- You might want to create an issue template for bugs and errors that can be used as a guide and that defines the structure of the information to be included. If you do so, reference it here in the description. -->
101
101
102
-
103
102
### Suggesting Enhancements
104
103
105
104
This section guides you through submitting an enhancement suggestion for js-coding-challenges, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
106
105
107
106
<!-- omit in toc -->
107
+
108
108
#### Before Submitting an Enhancement
109
109
110
110
- Make sure that you are using the latest version.
@@ -113,6 +113,7 @@ This section guides you through submitting an enhancement suggestion for js-codi
113
113
- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
114
114
115
115
<!-- omit in toc -->
116
+
116
117
#### How Do I Submit a Good Enhancement Suggestion?
117
118
118
119
Enhancement suggestions are tracked as [GitHub issues](https://github.com/ComputeNepal/js-coding-challenges/issues).
-[Eloquent JavaScript by Marijn Haverbeke ](https://eloquentjavascript.net/)
29
+
-[JavaScript: The Good Parts by Douglas Crockford ](https://cdn.tc-library.org/Rhizr/Files/daaz74mzphKfnHsen/files/JavaScript-%20The%20Good%20Parts.pdf)
30
+
-[You Don't Know JS" series by Kyle Simpson](https://github.com/getify/You-Dont-Know-JS)
If you are a beginner looking to learn JavaScript, this guide is for you. While it may not ensure instant mastery, it will provide you with a roadmap to progress systematically. With dedication and effort, you can achieve success in your JavaScript learning journey. However, you will need to personalize your schedule and timings based on your individual needs and availability.
4
+
5
+
## Here's a detailed schedule for learning JavaScript:
6
+
7
+
### Weeks 1-2: Introduction to JavaScript Basics
8
+
9
+
- Learn about the syntax, variables, data types, operators, and basic control flow (if statements, loops) in JavaScript.
10
+
- Complete online tutorials and coding exercises to practice - writing simple JavaScript programs.
11
+
- Build small projects, such as a calculator or a simple interactive webpage, to apply the concepts learned.
12
+
13
+
### Weeks 3-4: Deep Dive into JavaScript Fundamentals
14
+
15
+
- Study more advanced topics like functions, arrays, objects, and string manipulation in JavaScript.
16
+
- Learn about concepts like scope, hoisting, and closures in JavaScript.
17
+
- Practice using built-in JavaScript methods and functions to manipulate data and perform common programming tasks.
18
+
- Complete coding exercises and small projects that involve working with functions, arrays, and objects.
19
+
20
+
### Weeks 5-6: Asynchronous Programming and DOM Manipulation
21
+
22
+
- Learn about asynchronous programming in JavaScript using concepts like callbacks, promises, and async/await.
23
+
- Study the Document Object Model (DOM) and learn how to manipulate web page elements using JavaScript.
24
+
- Practice building interactive web pages by adding event listeners, handling form submissions, and manipulating the DOM.
25
+
- Build small projects that involve asynchronous programming and DOM manipulation, such as a weather app or a simple interactive form.
26
+
27
+
### Weeks 7-10: Advanced JavaScript Concepts and Project Work
28
+
29
+
- Study more advanced JavaScript concepts such as ES6+ features, error handling, and performance optimization.
30
+
- Learn about JavaScript modules, classes, and prototypes.
31
+
- Dive into more specialized topics like regular expressions, closures, and advanced DOM manipulation.
32
+
- Work on larger projects to apply the concepts learned, such as a todo list app, a simple game, or a web-based calculator.
33
+
- Collaborate with other developers, participate in coding challenges, and practice debugging and troubleshooting JavaScript code.
34
+
35
+
### Weeks 11-12: JavaScript Frameworks and Libraries
36
+
37
+
- Explore popular JavaScript frameworks and libraries such as React, Angular, or Vue.
38
+
- Learn the basics of using a framework or library, including components, state management, and routing.
39
+
- Build a small project using a JavaScript framework or library to gain hands-on experience.
40
+
- Review and reinforce your knowledge of JavaScript concepts by working with real-world projects and solving practical problems.
41
+
42
+
### Beyond Week 12: Continuous Learning and Real-World Application
43
+
44
+
- JavaScript is a constantly evolving language, so continue to stay updated with the latest developments, best practices, and tools in the JavaScript ecosystem.
45
+
- Keep practicing and applying JavaScript concepts by working on real-world projects, contributing to open-source projects, and participating in coding communities and forums.
46
+
- Explore other areas of JavaScript, such as server-side programming with Node.js, mobile app development with React Native, or data visualization with D3.js, based on your interests and career goals.
47
+
48
+
## Conclusion
49
+
50
+
Don't feel overwhelmed by this schedule; remember that learning takes time. Just be consistent and you will achieve your goals. Avoid falling into the trap of tutorial hell, instead, apply what you're learning and keep moving forward towards your destination.
0 commit comments