snorlaxmorlax
Joined 4 years ago
Joined 4 years ago
Would you mind creating an issue for this page using the link below? It helps us track and prioritize updates more effectively: https://github.com/mdn/content/issues/new?template=page-repo...
We actively monitor feedback on GitHub, so if you have more detailed suggestions or broader ideas, feel free to start a conversation on GitHub Discussions → https://github.com/orgs/mdn/discussions
We’d love to hear more from you and identify areas we can improve together.
All MDN content remains human-written, maintained by our team and contributors, and based on real browser implementations. You can always view the source and track changes on our GitHub repository for content.
Here's a wikihistory for the lexical grammar page → https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
I hear you on the complaints, I'll take this to the team. You might like this, in case you'd still like to learn building Firefox extensions → https://extensionworkshop.com/
You're absolutely right that the old `mdn/sprints` repo is no longer the active channel for suggesting or discussing content changes. These days, we encourage folks to file issues directly in the mdn/content¹ GitHub repository. That’s where all our documentation now lives, and it’s actively maintained by MDN staff and contributors.
If you spot inaccuracies, outdated examples, or unclear distinctions on any page, we now have a way to report straight from the page, you can find this at the bottom of every page → "Report a problem with this content." Please feel free to open an issue² or even suggest edits directly via pull request. We also try to prioritize fixes based on how widely used or confusing a topic might be, so calling attention to edge cases or under-documented differences is genuinely helpful.
Let me know if you’d like help filing an issue or want to connect with the folks maintaining a specific area of the docs. We’d love to have you involved again!
¹ https://github.com/mdn/content ² https://github.com/mdn/content/issues/new/choose
Re: “Who is this for?” Most of our reference pages are grounded in real-world browser implementations. Rather than documenting specs in isolation, we focus on features that have been implemented across browsers. We aim to present this information in a clear, neutral way, accessible to developers at any stage of their journey.
That said, we have expanded our efforts to create more learning-focused content, free resources designed to support new developers through a structured curriculum. Additionally, we’ve started publishing more in-depth guides on niche topics on our blog, which complements our core documentation but serves a slightly different purpose from what you mentioned.
If you'd like to take a look at our partners page → https://developer.mozilla.org/en-US/about#our_partners