Learn the web platform first (HTML, CSS, JavaScript, how HTTP works), then one frontend framework, then a backend with a database, and build a real project at each stage. If you already know WordPress, you are not starting over: your HTML, CSS and PHP experience transfers.
What people tell me
I am a student, or I already build WordPress sites, and I want to become a proper web or full-stack developer. There are so many roadmaps, courses and frameworks that I do not know what to learn first, and I find learning difficult when I jump between topics. Some of us want to move from WordPress into modern stacks like MERN, and some want to know whether WordPress itself can be a real career.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- Order matters more than the resource: platform fundamentals, then a framework, then backend and data.
- Build one real project at every stage instead of finishing more courses.
- WordPress experience is a head start, not a dead end; it can be a career on its own or a bridge to modern stacks.
- Git, deployment and debugging are part of the core skill set from day one.
- Choose one stack and go deep before comparing alternatives.
Order beats resources
When students ask me for a web development roadmap, the resource is rarely the real problem. Plenty of free material is excellent. The problem is order: jumping into React before understanding JavaScript, or into a backend framework before understanding HTTP, and then feeling that learning is "difficult" when the missing piece was a foundation.
So here is an order that works, with what to build at each stage.
The roadmap at a glance
| Stage | Learn | Build to prove it | Rough time at 10 to 15 hours a week |
|---|---|---|---|
| 1. The web platform | HTML (semantic, forms, accessibility), CSS (box model, flexbox, grid, responsive design), how browsers and HTTP work | A responsive multi-page site with a working contact form | 4 to 6 weeks |
| 2. JavaScript properly | Variables, functions, arrays and objects, DOM, events, fetch, promises and async/await, modules | An interactive app using a public API, such as a weather or book search app | 6 to 8 weeks |
| 3. Tools you use daily | Git and GitHub, the terminal, npm, browser dev tools, deploying a static site | Everything so far on GitHub with a live link | Alongside stages 2 and 3 |
| 4. One frontend framework | React (with TypeScript once comfortable): components, state, effects, routing, forms | A multi-page app with authentication from a hosted service | 6 to 8 weeks |
| 5. Backend and databases | Node.js with Express or a similar framework, REST API design, authentication, SQL (PostgreSQL) or MongoDB, validation | A REST API with a database, auth and tests | 6 to 8 weeks |
| 6. Full-stack integration | Connecting frontend and backend, environment variables, error handling, deployment, basic security | One complete product deployed end to end | 4 to 6 weeks |
| 7. Depth | Performance, testing, a meta-framework such as Next.js, caching, basic system design | Improve your full-stack project with measured results | Ongoing |
Timings are rough and depend heavily on your starting point. Moving slower but finishing each stage beats rushing through all seven.
Why this order
- Frameworks change; the platform does not. HTML, CSS, JavaScript and HTTP knowledge still applies when today's popular framework is replaced.
- Frameworks hide details. If you learn React first, bugs that are really JavaScript or network issues will feel mysterious.
- Backend makes more sense after frontend. Once you have consumed APIs, designing one is intuitive.
Stack choice without overthinking
| If you want | A sensible first stack |
|---|---|
| The broadest job market for web | JavaScript and TypeScript, React, Node.js, PostgreSQL |
| MERN specifically | MongoDB, Express, React, Node.js, but still learn basic SQL at some point |
| Freelance websites for small businesses | WordPress, plus strong HTML, CSS and PHP |
| A backend-heavy career | Pick Python, Java or C# for the backend, keep a simple frontend |
Pick one row and stay with it for at least six months. Comparing stacks every week is how months disappear.
If you are coming from WordPress
You have more than you think. You already understand hosting, themes, HTML, CSS, some PHP and, importantly, what clients actually ask for.
WordPress as a career is real, especially in freelancing and agencies. To stand out, go beyond page builders: custom theme development, custom plugins, the block editor with React, performance optimisation and security hardening. Developers who can build custom functionality are paid far more than those who only configure themes.
Moving to MERN or modern full stack is a natural next step. Your fastest path:
- Deepen JavaScript (stage 2 above). This is usually the real gap.
- Learn React. The WordPress block editor itself uses React, so you can even practise inside a familiar environment.
- Learn Node.js and a database, then build a project a WordPress site could not easily do, such as a real-time dashboard or a multi-user app.
- Present both skill sets together. "WordPress and React developer" is a genuinely marketable combination.
What your portfolio should look like by the end
- One polished full-stack project with authentication, a database, tests and a live link
- One frontend project that looks and performs well on mobile
- Clean GitHub repositories: READMEs, no committed
node_modules, meaningful commit messages - Short write-ups of the decisions you made and problems you solved
Two or three strong projects are better than ten cloned tutorials.
How to learn without getting stuck
- Follow one course per stage and finish it before starting another.
- After each tutorial, rebuild the project without watching, and add one feature of your own.
- When stuck, spend 30 to 45 minutes trying, then look for a hint, then rebuild the solution from memory.
- Use AI tools to explain errors and concepts, not to write whole features you do not understand.
- Share progress on LinkedIn; it builds visibility long before you apply.
If you are still stuck
Web development habits that outlast the framework covers what to practise once the basics are in, and how to start your career as a software engineer covers the job side. The resource library has courses and references for each stage. For a plan built around where you are right now, book a free 1:1 session.
Was this answer helpful?
Read next
- Thirteen Web Development Habits That Outlast the FrameworkThe web moves faster than any curriculum written about it, so every list of what to learn is stale by the time it reaches you. What survives is the set of situations that keep recurring: a slow page, a form that lets something through, state stored in two places that has started to disagree with itself. Thirteen of those, with the move that usually works.
- How to Start Your Career as a Software EngineerA practical route into the first software engineering job: pick one language and stop shopping, build things too big for a tutorial, learn the five fundamentals you cannot skip, get your code in front of a human, and apply earlier than you feel ready. Includes a twelve month shape to work to and an honest read on what the current entry level market has changed.
- The Fundamentals Worth Learning as a Software EngineerFrameworks are the fastest moving and least valuable part of what you know. This is the layer underneath: how a computer runs your code, data structures as trade offs, complexity at conversational depth, storage, networks, concurrency, version control, testing as a design tool, and the two skills engineers skip that decide how far they get.
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open to X and Instagram followers and university students. Prefer to talk? A free call works too.