Learning Area documentation status

This page tries to track ongoing documentation work in the MDN Learn section.


Pages No tags Needs* tags Missing tags Editorial reviews Technical reviews Outdated pages Documentation requests
297 17 (6%) 18 (7%) 141 (48%) 34 (12%) 43 (15%) 26 (9%) 16 (6%)

See also localization status of this section.

No tags

Found 17 pages. Learn more about how to tag pages.

Needs* tags

Found 18 pages. Learn more about how to deal with meta-tags.

Missing tags

At least missing one of the following: , , , , , , , , , , , , , , , , , ,

Found 141 pages. Learn more about how to tag pages.

Editorial reviews

Found 34 pages. Learn more about how to do an editorial review.

Technical reviews

Found 43 pages. Learn more about how to do a technical review.

Outdated pages

Found 26 pages. These pages haven't been updated in over a year. Outdated pages can have problems with both content and format. Look at these pages and consider: Is this page talking about the Web of today? Does it look consistent with newer pages in this topic area? If not, make any needed changes.

Documentation requests

Found 16 bugs. Documentation request bugs can contain various kinds work related to MDN pages. Read through the bug and ask questions in the bug if in doubt.

Bug Summary
993425 A new landing page for the Python Programming Language
1255775 Some of the advanced level links are very old
1281266 Output of two lines of code is wrong in attached doc.
1352742 Example 2: Breaking to a label
1388806 Getting an Apache server running is not beginner friendly
1415193 Navigation side bar links Client-side web APIs incorrect
1420495 No articles for "Client-side storage APIs" and "Device APIs" listed on Learn/JavaScript/Client-side_web_APIs
1424807 Offer translated example pictures in zh-CN
1433069 Create page: Create page: https://developer.mozilla.org/en-US/docs/Learn/Drafts/Python_on_the_client/Accessing_the_DOM
1433071 Create page: Create page: https://developer.mozilla.org/en-US/docs/Learn/Drafts/Python_on_the_client/Using_JavaScript_libraries
1450579 Add documentation on client-side web frameworks
1461362 creation of test users does not work
1465325 не найдены страницы в модуле мультимедиа и встраивание
1474228 TypeError: views/book_list.pug: 10 " | (#{book.author.name}) " Cannot read property 'name' of null
1509475 XMLHttpRequestUpload
1509819 "WebGL: Graphics processing" link in side bar is a 404

Browse as bug list.


Please help us to localize this documentation into different languages. Read more about how to translate.

Language Pages Translated Translations up to date
bn 238 13 (5%) 4 (30%)
de 297 59 (19%) 7 (11%)
es 238 136 (57%) 36 (26%)
fa 238 18 (7%) 2 (11%)
fr 241 181 (75%) 66 (36%)
it 238 57 (23%) 9 (15%)
ja 42 11 (26%) 8 (72%)
ko 238 114 (47%) 30 (26%)
pl 238 38 (15%) 15 (39%)
pt-BR 238 103 (43%) 36 (34%)
pt-PT 238 55 (23%) 9 (16%)
ru 270 177 (65%) 45 (25%)
vi 238 42 (17%) 15 (35%)
zh-CN 238 218 (91%) 110 (50%)
zh-TW 238 110 (46%) 35 (31%)

How to contribute

The learning area on MDN is brand new and offer a lot of opportunities for contribution from small tasks to large ones. Here's a list of all what you can do to help.

Writing learning articles

Expected time: A few hours

This is the core of the Learning Area. Those article are self teaching material which details a given skills to learn. A learning article focus on a single topic to learn and follow a strict structure which include. Read "Write an article to help learn about the Web" to learn how to structure such an article.

As an example, you can be inspired by the "Understanding URLs and their structure" article. See the Writing priorities section to know what is needed.

Creating "Active learning" material

Expected time: A few days

A TextBook article always need to be linked to some Active Learning materials. Those are projects, exercises, interactive code samples or everything that allows the reader to interact with a topic details into a TextBook. Such learning material is as important as any TextBook.

To create such Active Learning material, you are free to use any tools you wish. Nonetheless we strongly encourage you to use the WebMaker tools (especially Thimble) to do so as it provides various features very helpful for beginners and allows anyone to remix any content to learn from.

Creating learning pathways

Expected time: From a few hours to a few days

We also call them "learning tutorials". A learning pathways, explain how to complete a task and will link to all the necessary TextBook articles. As it is a pathways, it will also tell in which order the various TextBook need to be read to be able to complete the task. This is the backbone of the Learning Area as it provides guidance on what to learn first to do something.

Improve the glossary

Expected time: From a few minutes to a few hours

Our glossary is one of the key element for the Learning Area, see its dedicated doc status page for details on how to contribute.

Handle tagging

Expected time: From a few minutes to a few hours

Tagging is very important on the Learning Area. We should not have pages without tags. At minimum, a page in the Learning Area should have two tags:

Making editorial and technical review is also important. Remember that it's more important to be understood than to be technically perfect.

Get involved

Want to do more? Great, any one who wants to get involved with this project is welcome. Everything is discussed directly on MDN discussion forum.

Chris Mills is the resource leading this project; feel free to contact him with any questions. He's available, for sure, on Matrix  (UK time) in the MDN Web Docs room.



The overall goals of the project are:

  • Improve the discoverability of beginner contents: We have some existing contents but it is pretty hard to find. We need to organize it in a better way for beginners.
  • Improve the quantity of beginner contents: While writing we mainly focus on average and advanced users. As a consequence, we lack some serious beginner oriented contents. We need to write those missing contents and organize them with the existing contents to make easier for everybody to access and contribute to them.
  • Improve the quality of beginner contents: Still, we have some existing content for beginners but we need to organize it, complete it and make it more appealing.
  • Make sure beginners are taught well during their journey to the Web: MDN is not the only resource out there to learn the Web. Beyond our own contents, it's part of the Mozilla mission to help discover and found useful good resources to learn about the web.

Success metrics

In order to get some rational measurement about the success of our actions, the following metrics are suggested:

  • Measure the increase number of unique visitors on beginner contents:
    That would be a good sign that our beginner contents is easier to reach. For 2015, we expect to get 580 000 unique visitors to our Learn zone and Glossary by the end of the year.
  • Measure the increase number of returning visitors on beginner contents:
    That would be a good sign that the beginners content is appealing for them.
  • Measure the increase of time per page on the beginners content:
    That would be a sign that more beginners read and learn from that content.
  • Measure the decrease of bounce rate on the beginners content:
    That would be a sign that more beginners read and learn more from content on MDN
  • Measure bounce to third party resources we selected:
    That would be the sign that more users trust MDN as a reliable source of information regarding third party content.
  • Measure the increase of incoming links to MDN beginner contents:
    That would be the sign that MDN is considered as a trustable resource for beginners.

In addition, we should try to gather direct feedback on the improvements which are to be made.

Current available metrics are available on WikiMo.

Note: This project is action-driven, not time-driven. This means that we will do what needs to be done to create this content, regardless of how long it takes. However, to avoid being bogged down in this project forever, it is broken down into small, actionable steps which let us measure progress frequently.

Project status

2014 Archives

Status reports


Existing third party content

These web sites are potential sources of inspiration when creating content for new Web developers.

Contact us