Dev Doc Priorities
Help improve Mozilla developer documentation by letting us know what’s most important to you:
- What’s missing that you need
- What’s out of date and needs updating
- What could be better that already exists
Vote for the topics you care about or nominate ones that aren’t listed yet.
If you’re interested in working on a nominated topic, please say so in a comment!
-
Architecture of the browser
From the Documentation Wishlist (https://developer.mozilla.org/Project:en/Documentation_Wishlist)
'Bird's-eye view' articles on the architecture of the browser, of mail&news, etc.
52 votes -
Multithreading in JavaScript
From the Documentation Wishlist (https://developer.mozilla.org/Project:en/Documentation_Wishlist)
51 votes -
MathML Reference
In HTML5, like SVG's, MathML's can be directly inserted into HTML.
There is no reference doc about it, saying what parts of MathML1, 2 and now 3 are implemented in Gecko.
Like HTML, DOM, CSS and SVG, there should be a MathML Reference in the MDN49 votesstarted ·AdminJanet Swisher (Technical Writer/Community Organizer, Mozilla Developer Network) responded
The MathML reference is now in good shape. The only elements that are not documented are ones that are not implemented in Firefox.
-
CSS Reference
From the Documentation Wishlist (https://developer.mozilla.org/Project:en/Documentation_Wishlist)
this is under development already, but could use a lot more content
https://developer.mozilla.org/en/CSS_Reference46 votes -
HTML Reference
From the Documentation Wishlist (https://developer.mozilla.org/Project:en/Documentation_Wishlist)
Per teoli: All HTML elements documented, with styling information (default style on Gecko, usual style) and examples (Even elements that are vendor-specific or deprecated, with an explanation of The Right Way of doing this).
44 votes -
Websockets Tutorial
- Examples of how to use Websockets.
- List of some servers that currently support Websockets and will work with Firefox.35 votes -
Link to cross-browser documentation wikis.
I was referred here by a webmaster to suggest that the documentation include links to wikis about cross-browser client-side technologies and best-practices. Specifically, I'm representing The HTML & CSS Wiki and the JavaScript Wiki, but if Mozilla were to determine that other wiki(s) are more appropriate I expect we would migrate our content there. The URLs are:
31 votes -
SVG tutorial
From the Documentation Wishlist (https://developer.mozilla.org/Project:en/Documentation_Wishlist)
23 votes -
Intro to SVG: Part 1 What is SVG and how do I create SVG content
From the Documentation Wishlist (https://developer.mozilla.org/Project:en/Documentation_Wishlist)
20 votes -
docs for new contributors to core product
In general, my feeling is that there are currently very significant roadblocks for new contributors getting involved in helping work on the core product. Given that the better we do at engaging and growing the community to work the core, the better we can compete, making it significantly easier for newbies to contribute to the core community has an immense amount of leverage. I suggest that fIguring out which scenarios we want to support and then documenting those is very high value. Scenarios that occur to me include "I want to fix a specific bug", and "I just want to… more
19 votes -
17 votes
-
Create (update) XUL cheat sheet
If we prepare (updated) XUL cheet sheet, it will be great help for Mozilla developers, especially for beginner developers I believe.
AFAIK best cheat sheet of XUL is:
http://www.hevanet.com/acorbin/xul/top.xul
but this is unfortunately old and needs updates.And, if we also create printable cheat sheet, it must be helpful too especially for on-site workshops.
16 votes -
Current process for contributing code
From the Documentation Wishlist (https://developer.mozilla.org/Project:en/Documentation_Wishlist)
An up-to-date article outlining the process contributing code, linked from Developing Mozilla (https://developer.mozilla.org/En/Developer_Guide). Making sure the bug you're fixing is not invalid or wontfix, maybe checking that overall direction of the fix is correct (e.g. when implementing UI), making changes, testing, Creating a patch, picking r/sr/ui-r people, getting the patch checked in. See also Hacking Firefox (https://developer.mozilla.org/en/Hacking_Firefox) --Nickolay 01:15, 27 January 2007 (PST)
16 votes -
Client side storage api's
Documentation about how to use and what is avaiable about Web SQL Database, Web Storage and App Cache.
16 votes -
Allow to limit search to specific API and documentation topics
Many developers are only interested in the (previously excellent) DOM documentation. Today, when searching for obvious DOM topics, one gets many irrelevant search results on XUL/XSL/etc, making it pretty hard to find the actual documentation of interest.
Primarily, users should be able to limit the search to the DOM documentation.
btw, what happened to that excellent documentation? Many documentation pages, no longer contain comparisons with other engines/browsers nor any additional hints/information that previously existed. That info was almost unique to MDC and what made it on of the #1 addresses for looking up internals.
15 votesplanned ·
AdminJay Patel
(Product Manager, Mozilla Developer Network) responded
We hope to build better filtering into search for MDN 2.0 (via the Kuma project)
-
Performance issues with processor/RAM-intensive JS
What do we need to be looking out for with processor or RAM intensive Javascript?
-How can we stop memory leaks?
-How can we best help the JIT?
-How to best do dynamic compilation?13 votes -
Modifying object prototypes in JavaScript
From the Documentation Wishlist (https://developer.mozilla.org/Project:en/Documentation_Wishlist)
11 votes -
11 votes
-
Intro to SVG: Part 2 How can I (dynamically) handle/modify SVG content
From the Documentation Wishlist (https://developer.mozilla.org/Project:en/Documentation_Wishlist)
10 votes -
Tips and tricks for creating usable interfaces
From the Documentation Wishlist (https://developer.mozilla.org/Project:en/Documentation_Wishlist)
10 votes
