Skip to Content

MDN Front‑End Development Curriculum: Context, History, and Implementation Guide

24 February 2026 by
Suraj Barman

Context & History

MDN launched its Learn web development portal in 2019 to give newcomers a clear entry point into front‑end technologies. After several years of steady traffic—about 10 % of all MDN page views—the team recognized a gap: learners needed a concise, up‑to‑date curriculum that maps industry expectations to MDN resources. In early 2023 an extensive survey of students, educators, and hiring managers identified missing topics, preferred learning paths, and soft‑skill requirements. The result is a single, freely available curriculum document that lists core and supplemental topics, each linked to vetted MDN articles and external references.

Implementation & Best Practices

Creating and maintaining the curriculum follows a three‑phase roadmap: research, drafting, and community validation. First, the research team aggregates survey data, industry job postings, and existing curricula to define a high‑level topic map. Next, writers draft concise descriptions, assign priority levels, and attach reference links. Finally, the draft is published in a public GitHub repository where contributors can open issues, propose edits, or add resources. Throughout, clear versioning and transparent decision logs ensure that updates reflect evolving web standards.

Phase 1: Research and Topic Mapping

Use the survey insights to group topics into foundational (HTML, CSS, JavaScript), tooling (build systems, package managers), and professional skills (code review, accessibility mindset). Prioritize items that appear in at least 70 % of job listings and that have strong MDN coverage.

Phase 2: Drafting the Curriculum Document

Write one‑sentence goals for each topic, then attach a primary MDN article and a secondary external source for deeper study. Keep language consistent and avoid jargon that can confuse beginners. Mark each entry with core or supplementary tags to guide learners.

Phase 3: Community Review via GitHub

The curriculum lives in the mdn/curriculum repository. Contributors should open issues under “General feedback” for overall structure or “Topic coverage” for specific sections. Use sub‑issues to track discussions, assign reviewers, and merge pull requests after consensus.

Key Takeaways

  • Align curriculum updates with quarterly MDN releases to keep examples current.
  • Encourage feedback loops by tagging contributors and summarizing decisions in the repository’s README.
  • Document soft‑skill recommendations (communication, growth mindset) alongside technical topics.