MDN/Development/Offsites/Toronto 2012/Features
From MozillaWiki
< MDN | Development | Offsites(Redirected from MDN/Development/Offsites/Toronto 2012/Projects)
In August 2012, we met in Toronto to discuss some features that we would like to focus on over the next few months. The discussions are captured in our meeting notes. This page breaks those discussions into individual features and tasks.
Features and tasks
The individual features that we discussed are outlined below. Larger features will be broken down as more detail becomes apparent and necessary.
Priority |
Component |
Feature |
Notes |
Tasks |
API | Get a doc from a search term | |||
API | Research: What else does DevHub need? | |||
API | API call for getting everything before the first heading | |||
API | API control panel |
|
||
API | Write API |
|
||
P1 | API | Argument for limiting items in Feeds API | ||
API | Default of 50 items shown in Feeds API |
|
||
P1 | API | Research: How can we make the Feeds API more useful? |
|
|
Code examples | Research: How can we meet some must-have code example requirements? |
|
| |
Collaboration | Sending messages between users |
|
||
P1 | Collaboration | Watching groups | ||
P1 | Collaboration | Watching individual people | ||
Collaboration | Messaging/communication system | |||
Collaboration | Ability to send broadcast messages to all editors | |||
Dashboards | Recent changes | |||
P1 | Dashboards | A dashboard minimally viable product |
|
|
Dashboards | Research: What's important |
|
||
Dashboards | What has changed |
|
||
Dashboards | Articles with specific tags/flags | |||
Dashboards | Content/translation age (freshness) | |||
Dashboards | Following users |
|
||
Dashboards | Research: What did we mean by "Review – workflow +1+1 - include in Dashboard review" |
|
||
Dashboards | Content review |
|
||
Dashboards | Dashboard preferences / configuration | |||
P1 | Dashboards | Recent changes |
|
|
Dashboards | Link to the doc tracker | |||
Dashboards | Email notifications |
|
||
Dashboards | Filters |
|
||
P1 | Dashboards | What to update |
|
|
P2 | Dashboards | Watchlist items | ||
P2 | Dashboards | Changed from watched people | ||
P2 | Dashboards | Changes from watched groups | ||
Dashboards | Personal stats | |||
Dashboards | Link to user's own profile | |||
Dashboards | Notifications |
|
||
Dashboards | Custom saved search | |||
Dashboards | Page stats (popular, liked, etc.) | |||
Dashboards | Style guide | |||
P1 | Dashboards | What to translate | ||
Dashboards | Language-specific links |
|
||
Dashboards | Localization progress | |||
Dashboards | Large deletions | |||
Dashboards | New users | |||
Dashboards | First edits | |||
Dashboards | First uploads | |||
Dashboards | Permission requests | |||
Dashboards | Site stats |
|
||
Dashboards | Items marked as spam | |||
Dashboards | Site stats | |||
Dashboards | KumaScript errors | |||
Dashboards | Template validation errors | |||
Design / user experience | Highlight Firefox OS | |||
Design / user experience | Highlight Apps and the Marketplace | |||
Design / user experience | Mobile friendly website | |||
Design / user experience | Section editing | |||
Editing | Research: What did we mean by "Code playground" |
In Toronto, we mentioned building a "Code playground". What did we mean by this? |
||
Editing | Find and replace |
|
||
Editing | Moving pages | |||
Editing | Easily display demos in MDN documentation | |||
Editing | Display XTags demos within MDN documentation |
|
||
Editing | Research: Should we switch to another WYSIWYG editor? |
Some possibilities: |
||
Editing | Revert /to/ revision |
|
||
Editing | A better review and approval workflow | |||
File attachments | Deleting attached files | |||
File attachments | Research: How should we manage file attachment permissions. |
|
||
File attachments | Interface improvements for attaching a file | |||
P1 | KumaScript | wiki.subpages |
This is breaking the JavaScript reference. |
|
Other | Master compatibility table |
|
||
Other | postmodernizr.net | |||
Other | Research: What did we mean by "Code snippet - in view source in dev tools." | |||
P3 | Other | Event manager improvements |
|
|
Other | Research: Pulling in documentation from external resources |
This research will feed into our actual work for the feature. |
| |
Other | Pull in documentation from external resources |
|
||
P3 | Other | Offline browsing | ||
Other | RSS feed of changes in all locales. | |||
Other | RSS feed generator |
|
||
Other | Style guides for trees of documentation |
|
| |
Other | Site map | |||
Other | Make Kuma standalone, so that other organizations could install it | |||
Other | Documented policies | |||
SEO | Better page titles | |||
SEO | Better keywords and metadata | |||
SEO | Standardize terms with industry | |||
SEO | SEO Analytics |
| ||
P1 | SEO | Prevent search engines from indexing API results | ||
User management | Permissions on subtrees of documents | |||