MDN's content now lives in a GitHub repository, completing a migration Mozilla had been describing publicly for some time as part of a new back-end and front-end architecture.
From wiki to pull request
The shift replaces MDN's wiki model with a pull request workflow. As Chris Mills put it:
We will be using GitHub's contribution tools and features, essentially moving MDN from a Wiki model to a pull request (PR) model. This is so much better for contribution, allowing for intelligent linting, mass edits, and inclusion of MDN docs in whatever workflows you want to add it to (you can edit MDN source files directly in your favorite code editor).
Concretely, a documentation page such as the one for :focus-within gains a button that points to its file in the repo — for example files/en-us/web/css/_colon_focus-within/index.html — instead of opening the wiki editor. Edits can happen in the GitHub UI or through any Git workflow, which also makes them editable in a local code editor. Saving a change becomes a Pull Request automatically, and a team is expected to review incoming PRs.
Mozilla's stated turnaround for changes is aggressive:
We think that your changes should be live on the site in 48 hours as a worst case scenario.
Editorial implications
The content model itself is the notable part of the change. One criticism: the sources are HTML with specialized classes rather than Markdown, though that could evolve after such a large one-shot migration. The more significant question is who writes the docs. Mozilla laid off MDN's entire writing team in August 2020, so the strategy now rests on opening documentation creation and editing to the wider developer community.
There is a precedent, and not a reassuring one: the similarly community-driven "Web Platform Docs" did not succeed. MDN, however, starts with far more content, mindshare and momentum. The likely outcome is that maintenance of existing docs works well, new material on currently popular topics works reasonably, and aging, unglamorous subjects get less attention. Firing the writers before the model had proven itself also signals the product direction plainly: paying a content creation team directly is not part of the plan.




