What

The Mozilla Developer Network (MDN) team is holding a "doc sprint": a short period when people come together to create resources for the MDN site. This can include documents such as guides and reference pages, but also code examples and demos. It's all about making stuff to help people use open Web technologies.

Schedule

• Starting 31 May, 15:00 UTC (8:00 a.m. Pacific Time)
• Ending 1 June, 23:59 UTC (5:00 p.m. Pacific Time)

You're welcome to start earlier or finish later than the "official" time span. MDN never closes.

Location

You can participate from anywhere. Just sign in to MDN and get started.

We use this etherpad to coordinate and track what's been done.

But part of what makes a doc sprint fun is collaborating with other people. Even if you're working on something solo, it's more fun to chat with people who are doing similar things. We use the #devmo channel on irc.mozilla.org for live chat during the sprint. Learn about IRC if you're not familiar with it.

There are also in-person meetups in two locations for this sprint: San Francisco and Paris.

San Francisco

Mozilla's SF office

• Friday: Golden Gate Bridge conference room (319)
• Saturday: Community space (7th floor)

Paris

Mozilla's Paris office

• Saturday: from 9AM to 6PM Paris time.

If you plan to attend the Saturday's meeting in Paris, please add yourself to this Lanyrd board: http://lanyrd.com/2013/newonmdn/

Topics

The main topical focus for this sprint is Web devices APIs. We especially need helpful code examples for these APIs. Another timely topic is Mixed content blocking, especially a guide to "how to fix my site".

However, you are welcome to work on any topic that fits on MDN, including Web standards (HTML, CSS, JavaScript, SVG, MathML, etc.), Mozilla technology (apps, Persona, Firefox OS, etc.) or the Mozilla project itself (building, testing, localizing).

Here are some ideas for things to do:

• MDN documentation wishlist
• Firefox issues with doc impacts
• Add browser compatibility tables to CSS, DOM, and JavaScript reference pages.
• Fill out browser compatibility tables on reference pages where they exist, based on info from caniuse.com and quirksmode.org.
• Pages that need technical review.
• Pages that need editorial review
• David Bruant's TODO list (mostly JS-related stuffs)
• Add live samples to existing articles on CSS, HTML, and JavaScript.
• Make videos showing how to get and build Firefox code.

Suggest a topic, either that you want to work on, or that you'd like to see done by someone.

Helpful information

• Our list of subject-matter experts.
• Our list of topic drivers. These are people that organize specific areas of our documentation.
• How to add live samples to articles.

Sign up to help

If you're planning to participate, please add your name, IRC nickname and/or MDN user name, and what you'd like to work on, below (you need to create an account on this (spam-free) wiki in order to edit it):