I do found more minor errors in MDN compared to other official documentation (like Python), but it's kinda understandable.
And it sometimes takes months to get things fixed (after reporting or providing PR at https://github.com/mdn/content).
I've learned to always test myself when it comes to pesky/obscure behavior(s) of JS.
In MDN Playgroundmdn
content
Markdown2020–2026
mdn / content
content
The official source for MDN Web Docs content. Home to over 14,000 pages of documentation about HTML, CSS, JS, HTTP, Web APIs, and more.
45Distinct people
51Mentions
0Explicit recommenders
11.1KGitHub stars
What to know before exploring
What it is
The official source for MDN Web Docs content. Home to over 14,000 pages of documentation about HTML, CSS, JS, HTTP, Web APIs, and more.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:45:45 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year51 dated mentions
Observed mentions: 2020-11-03 11:06:07 UTC to 2026-09-25 21:42:17 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 7 | 3 | 4 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 8 | 0 | 8 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 5 | 1 | 4 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 10 | 3 | 7 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 9 | 0 | 9 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 8 | 1 | 7 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Welcome to MDN Web Docs
MDN Web Docs is an open-source, collaborative project that documents web technologies including CSS, HTML, JavaScript, and Web APIs.
Alongside detailed reference documentation, we provide extensive learning resources for students and beginners getting started with web development.
MDN's mission
MDN's mission is to provide a blueprint for a better internet and empower a new generation of developers and content creators to build it.
The strength of MDN Web Docs lies in its vast community of active readers and contributors.
Since 2005, approximately 45,000 contributors have created the documentation we know and love.
Together, contributors have created over 45,000 documents that make up an up-to-date, comprehensive, and free resource for web developers worldwide.
In addition to English-language articles, over 35 volunteers lead translation and localization efforts for Chinese, French, Japanese, Korean, Portuguese, Russian, and Spanish.
Build the site
To set up the site locally, you need to have Node.js installed, which comes bundled with npm.
You can check if these are installed by running the following commands:
node -v
npm -v
After you have installed Node.js, you can install the dependencies using npm install and start the local preview:
npm i
npm start
Once started, a live preview is available at http://localhost:5042/.
Contribute to MDN Web Docs
You can contribute to MDN Web Docs and be a part of our community through content contributions, engineering, or translation work.
The MDN Web Docs project welcomes contributions from everyone who shares our goals and wants to contribute constructively and respectfully within our community.
To find out how to get started, see the CONTRIBUTING.md document in this repository.
By participating in and contributing to our projects and discussions, you acknowledge that you have read and agree to our Code of Conduct, which means adhering to Mozilla's Community Participation Guidelines.
Get in touch
You can communicate with the MDN Web Docs team and community using the communication channels.
Read the full README on GitHubWhat Hacker News says
5 sourcesFWIW, OWD writes open source technical content and is not responsible for the design of MDN nor the blog, ads, or login and membership features of the site. That is done by Mozilla.
The OWD team writes technical documentation on APIs, HTML, and JS. OWD also works on information architecture and browser compatibility data. They contribute mainly to https://github.com/mdn/content/ and https://github.com/mdn/browser-compat-data/.
Mozilla, not OWD, is responsible for Yari, the platform behind MDN Web Docs (https://github.com/mdn/yari). The MDN blog, ads, AI and design, the MDN infrastructure, are fully owned and controlled by Mozilla.
I know some folks who work on this content and TBH it’s the folks we’d want working on this content.
In MDN can now automatically lie to people seeking technical informationMDN – Remove docs for the element
2 points · Open discussionI tracked down the Git history where the phrase "essentially a buzzword" was introduced in this pull request:
https://github.com/mdn/content/pull/5116/files#diff-7cfca62e...
I agree that it's unnecessarily dismissive.
In I just learned about HTML redirects (2020)I just don't see how you interpreted the remark in the way you did. Regardless, I've filed a PR to make the docs clearer [0] so neither of us has to waste any more time on this.
[0] https://github.com/mdn/content/pull/25925
In Safari releases are development hell