- 1 Project
- 2 Timeline
- 3 Format and Content
- 4 Getting Involved
- 5 Feature Matrix (Week 1)
- 6 Feature Matrix (Week 2)
- 7 Feature Matrix (Week 3)
- 8 Feature Matrix (Week 4)
- 9 Feature Matrix (Week 5)
- 10 Feature Matrix (Week 6)
- 11 Feature Matrix (Week 7)
- 12 Demos (Week 1)
- 13 Demos (Week 2)
- 14 Demos (Week 3)
- 15 Demos (Week 4)
- 16 Demos (Week 5)
- 17 Demos (Week 6)
- 18 Demos (Week 7)
This project is designed to highlight all of the new web developer features in Firefox 3.5 and what you can now do with open web technology. It is developer-focused, not end-user focused.
Every day for 35 days we will:
- Post one in-depth post about one new developer feature in Firefox 3.5.
- One demo that shows what you can do with the open web.
(Note: the demo doesn't have to be related to the feature.)
We're trying to get a bunch of developers who aren't directly part of the Mozilla project to help build these demos and show off what we're capable of.
We'd like to start this slightly before we release Firefox 3.5 in order to build up to the release. Given that we will be starting our posts on June 8th.
Dates for the first week are listed in the chart below. If you're posting you should:
- Have a draft post ready 5 days ahead of the post.
- Have the final post ready 3 days ahead of the post.
Format and Content
The site that will be hosting this will be a WordPress instance at hacks.mozilla.org, with some old-school Mozilla Project branding. There are both posts that describe features and posts that link to demos - please read below about both types.
A post that describes a feature should include complete text, videos and other images. Expect to write at least a few paragraphs that describe:
- How the feature works.
- How that feature compares to other similar features in other browsers.
- Includes a demonstration and/or graphics that describe how it works.
- Links to appropriate documentation in developer.mozilla.org.
Whether you're an active member of the Mozilla project or not we're more than happy to include a note at the top of the post saying who you are and what you do. If you want to include a copy of the post on your own weblog we're also more than happy to link back to your personal or professional weblog in that post. We want to make sure that we're both celebrating the work of individuals and giving credit and traffic where we can. But we also want to make sure that the full text is kept as part of this project as well so expect to make a full cross-post.
Demo posts should include at least:
- An image or video of the demo. (For a video include a flash version for fallback for people stuck on IE, Safari and Chrome. Opera is likely to work with Ogg Theora?)
- If the entire demo can fit into the post, that's great.
- Most demos are complex enough to need their own pages, so a link to the demo at the top of the post.
- A high level technical description of how the demo works.
As with the feature posts above, we're happy to link to other people's posts and give a description of who is doing the work. This is about celebrating the awesome work that's going on on the web today and the people at the leading edges.
Also it's fine if demos overlap on features - if you have something cool, just do it. Doesn't matter if it's the same feature as someone else's. Just that it's different and neat.
For now just add your name to the list of items below if you want to write a post about one of the features or make a demo. There are exactly 35 slots for each, so please don't add for now.
Expect to spend at least a couple of hours on each post or demo. We're looking for quality stuff here so you should be comfortable writing and you should be willing to take the time to research other resources and build graphics to describe the feature.
If we're overloaded with demos we'll set up a queue and go past the 35 days with extra demos. Bonus days, if you will. Or we can move to a contest model where people submit demos and we judge them. But we're not there quite yet.
For more info please ask on the evangelism mailing list.
Feature Matrix (Week 1)
|Mon June 8||createImageData() for canvas||Paul Rouget||
Feature Matrix (Week 2)