App developer docs: roadmap
We already have a session about adding more code examples to our docs, but it'd be good to also talk more generally about what we want to do in our app development docs.
Blueprint information
- Status:
- Not started
- Approver:
- Jono Bacon
- Priority:
- Undefined
- Drafter:
- Daniel Holbach
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
Other work items which are WIP:
- tutorial html5 Import from Content Hub
- tutorial html5 Export to Content Hub
- tutorial html5 Export to Facebook with Online Accounts
- guide/primer Online Accounts
- html5 Online Accounts tutorial
- guide/primer Alarms
Examples with discussion
We've discussed and agreed on the need for a new category of doc on the portal: code sample (branch) with discussion. these will live in Tutorials but are not not procedural. they are often more tightly focused than an on ramp tutorial.
Work Items
Work items:
[knitzsche] guide/primer Online Accounts: TODO
[mhall119] Add AskUbuntu button to API website pages: TODO
[mhall119] Add email link to WP pages: TODO
[dholbach] set up schedule for weekly bug reviews of the dev docs: TODO
[dholbach] set up meeting (wk 13) to review ubuntudeveloper
[dholbach] set up meeting (wk 14) to review QML docs in detail: INPROGRESS
[dholbach] set up meeting (wk 15) to review /publish docs in detail: INPROGRESS
[knitzsche] Set up spreadsheet to track which bits still need information from engineering: TODO
[dholbach] set up meeting (wk 16) to identify missing docs from engineering in detail: INPROGRESS
[dholbach] announce dev docs initiative: INPROGRESS
[mhall119] Remove /api/devel/
[mhall119] Redirect /api/devel/
[dholbach] set up meeting with Kyle to discuss which docs can be translated soon: DONE
