Feature Page Structure: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (Created page with "{| class="fullwidth-table" |- | style="font-weight: bold; background: #DDD;" | Feature | style="font-weight: bold; background: #DDD;" | Status | style="font-weight: bold; backgro...")
 
m (Replaced content with "The old format for the feature pages is now deprecated and should no longer be used at all! We have a much better and lovelier system for creating, editing, and organizing f...")
 
(30 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{| class="fullwidth-table"
The old format for the feature pages is now deprecated and should no longer be used at all!
|-
| style="font-weight: bold; background: #DDD;" | Feature
| style="font-weight: bold; background: #DDD;" | Status
| style="font-weight: bold; background: #DDD;" | ETA
| style="font-weight: bold; background: #DDD;" | Owner
|-
<section begin="status" />
| [[Feature Page Structure]]
| {{StatusHealthy|status=One or two sentence status report.}}
| YYYY-MM-DD
| Owner Name
<section end="status" />
|-
|}


== Summary ==
We have a much better and lovelier system for creating, editing, and organizing feature pages now, and it all begins here: [[Features/Create new | Create new feature page]].
One or two paragraphs outlining what we're building and why.  Should be enough so that uninvolved readers will know whether or not they want to learn more about the project.


== Release Requirements ==
If you have any questions, contact [[User:Dria|Deb]].  Thanks!
Complete checklist of items that need to be satisfied before we can call this feature "done". 
 
== Next Steps ==
Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished.
 
== Related Bugs & Dependencies ==
Links to the feature tracking bug & other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.
 
== Team ==
Should start with a short intro explaining that this is the current set of team leads, but anyone is welcome to dive in and help out.
 
Team list should make it clear who to ask about what, and who to ping when they're needed.  Not all team members will be actively involved with the project at all times, but we should have an idea of who will be the touchpoint for each involved group (PM, marketing, devs, UX, graphic design, services, webdev, QA, etc etc)
 
Team info should include notes about where they hang out in IRC, if there's a mailing list, etc.
 
== Designs ==
Any and all mockups, design specs, tech specs, etc.  Either inline or linked to.
 
== Goals/Use Cases ==
The high level goals for the feature (which the release requirements checklist should fulfill).  These are the guiding light and overall vision for the feature.  Refer to this if there is confusion or are disputes about direction, designs, planning, etc.
 
== Non-Goals ==
Things we are specifically not doing or building as part of this feature.
 
== Other Documentation ==
Can include things like:
* Competitive landscape
* Research & references
* Whatever else is useful to the project.
 
__NOTOC__
 
Please remove this line and any non-relevant categories below.  Add whatever other categories you feel are appropriate.
 
[[Category:Feature]]
[[Category:Firefox]]
[[Category:Performance]]
[[Category:Polish]]
[[Category:Priority 1]]
[[Category:Priority 2]]
[[Category:Priority 3]]
[[Category:Unprioritized]]

Latest revision as of 18:46, 6 July 2011

The old format for the feature pages is now deprecated and should no longer be used at all!

We have a much better and lovelier system for creating, editing, and organizing feature pages now, and it all begins here: Create new feature page.

If you have any questions, contact Deb. Thanks!