What you build
A phone-friendly quiz app
A quiz that feels like an app on your phone: big buttons, one question per screen, a score at the end. It runs in any browser, so there is nothing to install.
JavaScript learning path
The short answer
Learn a little HTML and CSS first, then plain JavaScript in the browser: variables, conditions, loops and functions, then arrays and objects, then events and the DOM. Build and publish one small interactive project before you touch React or any other framework. With regular practice the basics come in weeks; using JavaScript confidently on your own projects takes months.
JavaScript is the language every browser runs, and it led the language list in the Stack Overflow 2026 Developer Survey. This is the order ZAM mentors use to teach it to complete beginners: the JavaScript part of the web path our free roadmap tool builds.
Two private classes, no card. Updated 18 November 2026 by Azzam Makki, founder of ZAM Academy.
The path
Each step says what you learn, why it comes at this point, and a first task small enough to start today. A back end and a database come after this; the web development path covers them.
Step 1
Structure and style web pages that work on any screen. Every web project starts here, and it's the quickest way to see your code turn into something you can click. First step: Build a one-page "about me" site with a heading, a photo and a list, then style it.
Step 2
Make pages respond: logic, events and the DOM. JavaScript is the language every browser runs. React and every other frontend framework is JavaScript underneath, so this is the part that lasts. First step: Add a button to a page and make it change some text when it's clicked.
Step 3
Save your work properly and share it. Every code review and every team works through Git. It's easiest to learn on a project of your own. First step: Create a GitHub account, put one project in a repository and write a three-line README.
Step 4
Build something small from a blank file, without a tutorial. Tutorials show you code. A project makes you write it, and that's where the knowledge starts to stick. First step: Write down the three things your project must do, then build only the first one.
Step 5
Put your project online for real users. Software isn't finished until someone else can use it. First step: Deploy the smallest working version of your project, even if it's unfinished.
Inside JavaScript
Each one builds on the one before. Use each one on a page straight away.
01
Numbers, text and true or false, stored with let and const.
02
if and else to choose what happens, and loops to repeat work without copying code.
03
Name a piece of logic once and reuse it. Most of the JavaScript you write lives in functions.
04
Lists and records: how real data, like a list of products or a user, is shaped.
05
Find elements on the page, change them, and react to clicks and typing.
06
Read errors in the console and step through your code with the browser developer tools.
07
Ask an API for data with fetch, wait for it with async and await, and show it on the page.
08
Split code into files and install packages once your projects grow. React comes after this, not before.
How long it takes
At 6 to 12 focused hours a week, most beginners get through the basics, from variables to the DOM, in a few weeks. Using JavaScript confidently on projects of your own takes a few months.
Being ready for a junior front-end or full-stack job takes longer, because it also needs HTML, CSS, Git and usually a framework. A common estimate for a junior-level portfolio is 400 to 600 focused hours in total.
Your first project
It uses every concept up to the DOM, and you can send the link to someone the day you finish.
What you build
A quiz that feels like an app on your phone: big buttons, one question per screen, a score at the end. It runs in any browser, so there is nothing to install.
What it practises
Every one of these comes up again in larger projects, so practising them on something small pays off later.
When it works
Save the best score in the browser so it's still there tomorrow.
Ignore for now
All three are worth learning, and all three are JavaScript underneath. They make sense once plain JavaScript feels comfortable.
Starting another course feels like progress, but it resets you each time. Finish the stage you're on first.
Any free editor on the computer you already have is enough. You can tune your setup once you know what you need.
A finished project shows far more than a certificate does. Build first; certify later if a job asks for it.
Questions
Write it in the browser, on small projects of your own. Learn one concept, use it on a page straight away, and read the errors in the console. Courses help, but most of the learning happens when you build something no tutorial walked you through.
The basics take most beginners a few weeks at 6 to 12 focused hours a week, and using it confidently on your own projects takes a few months. Job-ready front-end or full-stack skills take longer, often put at 400 to 600 focused hours in total.
Yes, the basics. On the web, JavaScript changes HTML and CSS, so you need to know what you are changing. A week or two of HTML and CSS is enough to start.
JavaScript if you want to build websites and web apps; Python if you want automation, data or AI. Either is a good first language, and the ideas carry over to the second.
After plain JavaScript feels comfortable: functions, arrays, objects, events and the DOM. React is JavaScript underneath, so learning it first means learning two things at once.
Yes. Free curricula such as freeCodeCamp and The Odin Project cover it, and ZAM's free build challenge has you build a small JavaScript app in your browser. A mentor helps when you are stuck or want someone to review your code.
Keep reading
Start with two free classes
The first class maps your goal, level and weekly hours. The second is a real coding session with feedback. Then your mentor recommends one plan, and you decide.