Closed Bug 584183 Opened 14 years ago Closed 13 years ago

Community documentation flow - wiki, docs, and blog post

Categories

(Add-on SDK Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: dbuchner, Assigned: fiveinchpixie)

References

Details

We need to generate a detailed, documentation walk-through wiki page to describe how community members should document their own add-ons and libraries. The wiki should show by example how and why they should document their work in accordance with our documentation standards.

An accompanying blog post is also needed to announce to the community this documentation flow, and direct them to the wiki for more details. I would include a small, documented code example in the post.

Looking for this to be done (save the final draft of the blog post) by August 10th.
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product.

To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
Version: Trunk → unspecified
We don't currently have a mechanism for addon authors to document their addons.  It seems useful to add one, but it probably belongs to Builder and/or AMO (or is cross-product).  We should have more discussions to figure out what we're going to do before we start filing bugs on specific implementation details.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.