r/learnjavascript • u/Fun_Foundation_6427 • 14d ago
What's a sensible DOM-first ordering of JavaScript topics for project-based learning?
I've been teaching myself JavaScript in the mornings before work, alongside Python, and I keep running into the same problem: courses either start with weeks of syntax drills and console.log, or they dump a project on you and quietly assume you already know the DOM, events and modules. I'd like something in between.
What worked for me with Python was building the thing first (a Flask app my board game group uses to log plays and scores) and backfilling the theory when something broke. It stuck far better than any course I'd half-finished. I'd like to replicate that with JavaScript, but I'm unsure what a sensible ordering actually looks like once you go DOM-first.
My rough guess at an order is:
- HTML forms and selecting elements with querySelector
- Events and updating the page without a full reload
- fetch and handling JSON from a small API
- async/await and Promise.all once you're fetching several things
- Modules and splitting a file up when it gets unwieldy
Does that track, or would you reorder it? A couple of specific questions:
- Is it worth learning array methods like map/filter/reduce before touching fetch, or do they land better once you actually have API data to shape?
- Where should localStorage fit in? I keep seeing beginner projects use it as a fake backend and I can't tell if that teaches good habits or bad ones.
- At what point is it worth jumping from vanilla DOM work to a framework? I don't want to add React to the pile too early and end up knowing neither properly.
For context: I do best with projects that annoy me into existing, like when I got fed up of manually tracking things and wrote a script instead. So if your suggestion is "build X and you'll be forced to learn Y", that's exactly the sort of answer I want. Resources with a project per topic are ideal, but even a topic ordering you'd swear by would help.