Menu

What's a sensible DOM-first ordering of JavaScript topics for project-based learning?

Reading 0:00
15s threshold

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?…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.