{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigsemkpisvxc7rhqmoj3kmjh4nplzca3fn7q7x5q7vmr5qccxulsm",
    "uri": "at://did:plc:zoasrjjpgvvxrrzcpaf24bsn/app.bsky.feed.post/3mkbxhsnvcqa2"
  },
  "path": "/notebook/links/under-the-hood-of-mdns-new-frontend/",
  "publishedAt": "2026-04-24T12:05:00.000Z",
  "site": "https://www.aaron-gustafson.com",
  "textContent": "This is a fascinating look at how MDN rebuilt its frontend around server-rendered HTML, web components, and a clear understanding of where interactivity actually belongs (and how to deliver it).\n\nI particularly appreciated how plainly this post describes a mismatch a lot of teams create for themselves: wrapping largely-static content in an app shell, then shipping a pile of JavaScript just to re-assert what the server already knew. MDN’s new approach feels refreshing, despite being grounded in age-old best practices: Keep the content first-class, treat interactivity as optional (and isolated), and only ship what the page actually needs.\n\nThere’s a lot to like here, but more than anything I love seeing MDN embrace an architecture that’s truly aligned with the platform it documents.",
  "title": "🔗 Under the hood of MDN’s new frontend"
}