Ask five different people how to get started with web development and you'll get five different lists of frameworks, each with strong opinions about why theirs is the right first choice. That noise is a big part of why getting started feels so much harder than it needs to.
A simpler way to think about it: strip out the framework debates entirely for a while, and build a solid floor first.
1. HTML and CSS, without a framework
Before reaching for any tool that generates or manages HTML for you, spend real time writing plain HTML and CSS by hand. Build a few static pages — a resume, a simple landing page, a small multi-page site. This is where you learn what a webpage actually is, which makes everything layered on top of it much easier to understand later.
2. Plain JavaScript, in the browser
Next, learn to make a page respond to a click, update text on the screen, and fetch some data, using nothing but JavaScript and the browser — no framework yet. This is the part most commonly skipped, and skipping it is why frameworks feel like magic instead of tools.
3. One framework, chosen and then ignored as a debate
Once the fundamentals are solid, pick one popular framework — almost any mainstream option works — and commit to it for a few months without second-guessing the choice. At this stage, the specific framework matters far less than actually building something real with it.
4. A backend, only once the frontend feels comfortable
Learning how a server stores data and responds to requests is a distinct skill from building interfaces. Trying to learn both at once, from zero, is where a lot of the overwhelm comes from — it's much easier layered on top of a frontend you already understand.
None of this needs to happen quickly. The order matters more than the pace: fundamentals first, one framework at a time, backend once the frontend isn't a struggle anymore.