HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
mdn
yari
TypeScript2020–2024
mdn / yari · Archived

yari

The platform code behind MDN Web Docs

17Distinct people
20Mentions
0Explicit recommenders
1.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The platform code behind MDN Web Docs

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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 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 year20 dated mentions

Observed mentions: 2020-10-29 22:46:14 UTC to 2024-06-30 17:16:43 UTC.

0369122020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 11 mentions; 2 submissions, 9 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC312
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC1129
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

20 sources
> “So it tells you wrong answers? Sounds utterly pointless”. I was flabbergasted. Could you tell a bit more about why this objection surprised you so much? I am often seeing this in the same tech circles that rejected the web3 craze; and I have to confess, it does sound reasonable to me. There is a recent PR opened in the MDN docs repository after MDN added the "AI explain" button, pointing out how utterly useless a AI guide is if it gives you incorrect answers and you do not have enough knowledge to catch it [0]. [0] - https://github.com/mdn/yari/issues/9208
In Ask HN: Are people in tech inside an AI echo chamber?
FWIW, 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 information
Instead of creating a new tool to convert MDN's content into HTML, it would probably be easier to modify the official tool, Yari, in order to produce web page with more compatible (and faster) CSS & JS. https://github.com/mdn/yari But I don't think it would be useful unless MDN merges in the changes. My daily web browser struggles with the new MDN rendering unless JS is disabled. So I've lost a few features since the "design change", notably I cannot run the examples. Would I use a cloned site that's faster and where CSS&JS are more compatible? I would loose the external search I'm used to (DuckDuckGo !mdn), so using the clone would require a few changes on my side...
In Mozilla and Open Web Docs Working Together on MDN

Showing the 15 most recent of 20 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.