Prerequisites Basic computer literacy and a willingness to document experiments.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn HTML semantics and document outline DOM, CSSOM and render pipeline Forms, labels and browser validation Accessibility landmarks and keyboard flow Frontend Development specialization: Track-specific focus: Frontend Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Web Development.
Tools HTML Browser developer tools MDN documentation
Hands-on exercise Build a semantic multi-page document and test it using keyboard navigation and browser inspection. Context for this route: Track-specific focus: Frontend Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Web Development.
Suggested project An accessible information site with forms and responsive content structure. The outcome must directly demonstrate Frontend Development, not merely list tools.
Learning resources Completion criteria The page has meaningful landmarks, labels, valid structure and keyboard access. Evidence must be reproducible and tied to Frontend Development.
Next: CSS layout, responsive design & motion
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Cascade, specificity and custom properties Flexbox, Grid and intrinsic sizing Responsive breakpoints and fluid type Reduced motion and focus states Frontend Development specialization: Track-specific focus: Frontend Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Web Development.
Tools CSS Grid/Flexbox Browser devtools Design tokens
Hands-on exercise Recreate a complex responsive component without fixed-width layout assumptions. Context for this route: Track-specific focus: Frontend Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Web Development.
Suggested project A responsive component library with mobile, tablet and desktop variants. The outcome must directly demonstrate Frontend Development, not merely list tools.
Learning resources Completion criteria Layouts remain usable at narrow widths, zoom and reduced-motion settings. Evidence must be reproducible and tied to Frontend Development.
Next: JavaScript modules & browser APIs
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn ES modules and lexical scope Promises, async/await and fetch Events, forms and DOM state Storage, URL and error handling Frontend Development specialization: Track-specific focus: Frontend Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Web Development.
Tools JavaScript Browser devtools ESLint
Hands-on exercise Build a client-side interaction that consumes a public API and handles loading, empty and error states. Context for this route: Track-specific focus: Frontend Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Web Development.
Suggested project A small interactive feature with modular JavaScript and input validation. The outcome must directly demonstrate Frontend Development, not merely list tools.
Learning resources Completion criteria The UI handles network failures and invalid input without uncaught errors. Evidence must be reproducible and tied to Frontend Development.
Next: Component architecture & application state
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Component composition and props Local and shared state Routing and data lifecycle Rendering, keys and side effects Frontend Development specialization: Track-specific focus: Frontend Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Web Development.
Tools Framework CLI or build tool React/Vue/Angular as applicable Component devtools
Hands-on exercise Create a searchable list/detail view with predictable state transitions. Context for this route: Track-specific focus: Frontend Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Web Development.
Suggested project A routed single-page application with reusable components and empty/loading states. The outcome must directly demonstrate Frontend Development, not merely list tools.
Learning resources Completion criteria Components have clear contracts and state changes are testable. Evidence must be reproducible and tied to Frontend Development.
Next: Forms, data integration & accessibility
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Form state and schema validation REST data fetching and caching Authentication-aware UI states Accessibility and localisation Frontend Development specialization: Track-specific focus: Frontend Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Web Development.
Tools Fetch client Form validation library Accessibility inspector
Hands-on exercise Implement a multi-step form with client-side validation and server error mapping. Context for this route: Track-specific focus: Frontend Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Web Development.
Suggested project A data-backed workflow with accessible validation and translated labels. The outcome must directly demonstrate Frontend Development, not merely list tools.
Learning resources Completion criteria Errors are announced clearly and no private data leaks into browser logs. Evidence must be reproducible and tied to Frontend Development.
Next: Testing, performance & frontend security
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Unit and component tests Browser end-to-end tests Bundle analysis and lazy loading XSS, CSP, dependency hygiene Frontend Development specialization: Track-specific focus: Frontend Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Web Development.
Tools Playwright or Cypress Testing Library Lighthouse
Hands-on exercise Automate a critical user journey and record a performance baseline. Context for this route: Track-specific focus: Frontend Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Web Development.
Suggested project A test suite, accessibility findings and a measured optimisation report. The outcome must directly demonstrate Frontend Development, not merely list tools.
Learning resources Completion criteria Critical flows pass reliably and performance changes have evidence. Evidence must be reproducible and tied to Frontend Development.
Next: Build, delivery & runtime operations
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Build output and environment configuration SSR/SSG where the chosen stack supports it CDN, cache and asset strategy Release checks and rollback Frontend Development specialization: Track-specific focus: Frontend Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Web Development.
Tools Build pipeline Web server or hosting CI workflow
Hands-on exercise Deploy a preview build and verify headers, asset caching and runtime configuration. Context for this route: Track-specific focus: Frontend Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Web Development.
Suggested project A production-ready deployment checklist and versioned release. The outcome must directly demonstrate Frontend Development, not merely list tools.
Learning resources Completion criteria Builds are reproducible and environment-specific values are not committed. Evidence must be reproducible and tied to Frontend Development.
Next: Capstone: accessible product experience
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn User journey and acceptance tests Component/API boundaries Accessibility and responsive QA Portfolio narrative and demo Frontend Development specialization: Track-specific focus: Frontend Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Web Development.
Tools Chosen frontend framework Playwright Git and issue tracker
Hands-on exercise Run a usability walkthrough and resolve issues discovered at mobile and desktop sizes. Context for this route: Track-specific focus: Frontend Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Web Development.
Suggested project A polished multi-route web application backed by real data or a clearly documented API. The outcome must directly demonstrate Frontend Development, not merely list tools.
Learning resources Completion criteria The application is accessible, responsive, tested and straightforward to maintain. Evidence must be reproducible and tied to Frontend Development.
End of roadmap: Complete the final project and build your portfolio.
✓ Mark this node as complete