javascript-tutorial / javascript-tutorial/en.javascript.info
Would it be possible to split some of the sections in the data types chapter into smaller subsections, with tasks for each?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 25.5k
- Forks
- 4k
- PR merge metrics
- No merged PRs in 30d
Description
I feel like these sections are covering a ton of information in each one. Currently spending maybe 3~ days on each, having to use chatgpt to help create tasks for me and split the thing up?
Its easier for me to focus on getting thru a section a day and then doing the tasks to reinforce what I've learned. Better workflow that way, but since getting to this chapter I have been finding it extremely difficult
I realize I could rely on other sources, but I chose this tutorial and I am going to stick with it until I get thru the thing I don't want to start over somewhere else and go over concepts I've already put a lot of effort into learning.
My general workflow has been to take hand written notes on the sections, trying to restate basically every peice of information there in my own words, then I'll pick out what ever important bits I should really now and put them into my notion database for easy refrence afterwards, and then being sure to play with each new concept as I am reading.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the data types chapter and identify sections that contain too much information for a single study session. Define smaller subsections and a reinforcing task for each; done means the chapter is reorganized into these focused units with tasks that cover the material.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100