Note: If you want to use the Trello board to organise yourself, just create a Trello account and ping Jeremie to have him give you write access to the board. To learn a bit more about how to use a Trello board, you can see how the content team uses its board with this article.
|Pages||No tags||Needs* tags||Missing tags||Editorial reviews||Technical reviews||Outdated pages||Documentation requests|
|145||1 (1%)||23 (16%)||42 (29%)||1 (1%)||5 (4%)||6 (5%)||7 (5%)|
See also localization status of this section.
Found 1 pages. Learn more about how to tag pages.
Found 23 pages. Learn more about how to deal with meta-tags.
- How can we design for all types of users?
- How do I set up a basic working environment?
- How do you make sure your website works properly?
- How do you upload files to a web server?
- How much does it cost to do something on the web?
- What are hyperlinks?
- What do common web layouts contain?
- What is a URL?
- What is a domain name?
- What is accessibility?
- What is the difference between webpage, website, web server, and search engine?
- What software do I need to build a website?
- What text editors are available?
At least missing one of the following: Navigation, WebMechanics, Search, Credibility, Security, Composing, Remixing, Design, Accessibility, CodingScripting, Infrastructure, Sharing, Collaborating, Community, Privacy, OpenPractices, junk, Index, MDN
Found 42 pages. Learn more about how to tag pages.
- CSS layout
- Attribute selectors
- Combinators and multiple selectors
- Pseudo-classes and pseudo-elements
- Simple selectors
- A cool looking box
- Fundamental text and font styling
- Styling links
- Styling lists
- Web fonts
- Use CSS to solve common problems
- How do I use GitHub Pages?
- How do you host your website on Google App Engine?
- Quickly Learn Object Oriented Programming
- Understanding Cloud architectures
- What people need to see your web site
- HTML Cheatsheet
- Adding vector graphics to the Web
- Images in HTML
- Video and audio content
- Define terms with HTML
- How to contribute to the Learning Area on MDN
- Storing the information you need — Variables
- WebGL by example
- Basic scissoring
- Boilerplate 1
- Canvas size and WebGL
- Clearing by clicking
- Clearing with colors
- Color masking
- Detect WebGL
- Hello GLSL
- Hello vertex attributes
- Raining rectangles
- Scissor animation
- Simple color animation
- Textures from code
- Video textures
Found 1 pages. Learn more about how to do an editorial review.
Found 5 pages. Learn more about how to do a technical review.
Found 6 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.
Found 7 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.
|993425||A new landing page for the Python Programming Language|
|1063999||Guide to text, text formatting and styling, and text rendering on the Web|
|1171753||"Common Pitfalls to avoid in Web Design" - this page is missing|
|1236263||Not able to configure arm emulation env|
|1249852||Incorrect documentation in Function definition|
|1255775||Some of the advanced level links are very old|
|1281266||Output of two lines of code is wrong in attached doc.|
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|
|de||84||9 (10%)||3 (33%)|
|fr||123||82 (66%)||37 (45%)|
|ru||122||20 (16%)||11 (55%)|
Note: The actual work in progress and priorities are tracked on the community trello board
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.
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:
- All pages must be tagged with a skill level: Beginner, Average or Advanced
- All pages must be tagged with their related Web Literacy Map competency tag.
Making editorial and technical review is also important. Remember that it's more important to be understood than to be technically perfect.
Want to do more? Great, any one who wants to get involved with this project is welcome. Everything is discussed directly on the dev-mdc mailing list. A weekly meeting is held every Monday to discuss the progress and planning of the project.
Jeremie is the resource leading that project, feel free to contact him with any questions. He's available, for sure, on IRC every Monday (European time) on the various MDN channels (#mdn, #mdndev) and more.
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.
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.
We hold a weekly project meeting, which everyone's welcome to attend. The meeting is held in the #mdn IRC channel every Monday at 10:00 AM PDT (18:00 UTC, 19:00 CET).
Agenda and notes: WikiMo
Work in progress
See the trello board and the doc status pages:
- Kick off
- Creating a survey about MDN and third party web sites for beginners
- Gathering initial feedback (We must do things with the webmaker team)
- Spreading the survey (dev-mdc dev-mdn, education, webmaker, engagement-developers, mozillan, reps-general)
- synthesize the survey and the raw feedback
- Spread the survey results: File:Learnin-area-survey-2014.pdf
- Inventory MDN content for beginners, intermediate, and advanced users (considered done even if it will be subject to change)
- Planning meeting with the WebMaker team on May 28/29
- Define how to structure beginner content
- Results of the "Tree of knowledge" workshop during the MDN Work week-end on March 2014
- It will help to tag content with http://goo.gl/vpxkP1 (Webmaker FTW)
- Draft plan is: https://etherpad.mozilla.org/learning-area-structure
- Mock up for a possible Learning Zone landing page: https://moqups.com/JeremiPat/9MbRALc2
- Sort out the results of the code sample survey
- Set up the Documentation status page for the Learning Zone
- Chris Mills awesome work:
- Notes from MozFest 2013: https://teach.etherpad.mozilla.org/scrum7-future?
- WebMaker project info:
- NOTE:This project is a complement to the webmaker initiative, not a competitor. It can be considered as a concrete implementation of some of the webmaker ideas. Due to its nature MDN will focus on the following skills define by the Web Literacy Standard: Web Mechanics, Composing for the Web, Design and Accessibility, Coding/scripting, and Infrastructure.
- Definition of HTML tag by WebMaker: https://etherpad.mozilla.org/simple-mdn
- The Opera Curriculum
- Learning pathway
Existing third party content
These web sites are potential sources of inspiration when creating content for new Web developers.
- https://www.khanacademy.org (not web related but good ideas for inspiration)
- Very cool interactive videos (wich use of the full potential of the web platform)