Improve Juju Documentation
A core essential piece of growing the Juju community is having engaging docs that allow different types of users to easily find the documentation they need. Furthermore, using the docs should be a positive experience that Juju users enjoy coming back to reference and learn. The docs should be correct, current, and engaging.
--- UDS 1303 Discussion ---
PAD URL: http://
-Leave behind RST!
-pandoc doesn't support some of the newer HTML5 elements (asides, etc)
-Make sure juju.ubuntu.com landing page tell Juju story well (what is it, why should I use it)
-Better references in sidbars with improved navigation
-Annotate Juju deploy command
-Annootate Juju GUI deploy
-Annotate anatomoy of a charm
Would like to have good sidebar notes, screen shots, tips, and examples.
Would like to have knowledge of what I am at in a journey
*Getting Started (Juju deploy)
Need version control
Want Markdown not RST
Get rid of anything marked draft
Need organization of what we currently have.
Evaluate Pandoc instead of Sphinx
Discuss GUI and Charm Browser
--- Immediate Needs ---
Verify the usability of docs (are the instructions correct).
Identify a model for the docs (framework)
*Not docbook - too complicated and print-biased
*Sphinx? Needed since core is now Go?
*Something markdown based?
*13.04 default for Go
*How to use it
-Py and Go living together
--- Organization ---
Local provider configuration
OpenStack provider configuration
EC2 provider configuration
Deploying a Charm
Exposing A charm
* User tutorial - rename to “Using Juju” (should be embeddedd per topic)
The Juju Charm Store (for users)
Handling common errors
Writing a charm
The Juju Charm Store
Charm Store Policy
Charm Quality Rating
Full table of all charm attributes
Full table of all juju commands
Operating Systems - appendix stuff
Relation references - appendix stuff
Evaluate for removal:
About juju - *move to juju.ubuntu.com.
Frequently Asked Questions - DELETE THIS, link to autogenerated FAQ at AU.
juju modules - remove Juju core specific
Drafts - REMOVE.
-content should be covered-
Implementation details - (should be in reference guide for charm attributes)
Commands to work with relation settings and membership (be sure to cover in charm author)
Upgrades - both (be sure how to implement charm upgrade hooks are covered in charm author)
Charm Upgrades (be sure to be covered in Charm Users: deployment)
New relation-ids hook command -(should be covered in charm author)
# Documentation Framework (Courseware)
-Make sure to review the docs point, and have a corrolation betweeen user jouneys and screen casts.
- Put screen cast in docs
-screen casets and docs should reference each other.
0 -- New to Juju
1. [user] Installing and configurating Juju
1. Charm Introduction
1. Charm Discovery/ Charm Store
1. [user] Deploying your first charm (include constraints)
1. [user] How to use relations
1. [user] Service configuration/
1.[user] Scaling services
1. [user] Debugging deployment - debug logs and friends
1. [user] Advanced topics (deploy-to, "jitsu" and friends)
-need to confirm how plug-in model is in Juju 2.0
1- New Charm Author
1. Submitting your first contribution to a charm
1. Writing a new charm from scratch.
a. charm tools
1. Publishing to the Juju Charm Store
1. How to improve your charm using community quality ratings (https:/
d. Handle Data
f. Ease of deployment
g. Responsive to devops needs
1. Getting your work peer reviewed
1. Charm Debugging
- Someone hears about Juju and wants to try it out- they start by reading the docs, and are soon producing world-beating charms and running services which can cure cancer and solve the energy crisis.
- User guide to get new users up and running
- Author's guide to help people write better charms
[OUT OF SCOPE]
- there will be fewer questions on ask.ubuntu about juju which aren't immediately answered by pointing them to a relevant part of the docs
-Embed into docs in the same topic section & have a one general Best Practice section for users and charm authors.
Notes from vUDS 1305: http://
Notes from vUDS 1308: http://
[notes from cloudsprint 2013-05]
Current docs suck, let’s redo them
- Nick has a pre-beta of new-docs: http://
- All in HTML so we don’t have to deal with meta-languages.
- lp:juju-core/doc/*.txt - a bunch of fairly unorganized but very useful internal developer docs that can be helpful (incl. glossary) to evilnick when writing the more end-user friendly docs
mthaddon’s biggest concern, keeping it up to date.
[evilnick] Define structural elements of HTML5 doc: DONE
[evilnick] Create sample "getting Started Guide": DONE
[marcoceppi] Prepare rollout strategy for new docs launch: DONE
[evilnick] Create video/webinar strategy: DONE
[marcoceppi] Propose policy for inclusion of doc contributions as ~charmers contrib: TODO
[jorge] Streamline contributions process in documentation: TODO
[mark-mims] Testing structure for charm documentation: TODO
[marcoceppi] Auto-generate charm interfaces documentation: TODO
[jorge] : Make sure our docs are synced on readthedocs.org: TODO
[jorge] Migrate/Move documentation embedded in juju.ubuntu.com into juju.ubuntu.
[arosales] Get a beta site going for Juju docs.: TODO
[arosales] Get a permanent staging site for the docs: TODO
[jorge] Get UX testing on the docs: TODO
Document local povider: TODO
Document debug-hooks: TODO
Document deploy --to: TODO
Document --constraints: TODO
Document Charm Helpers: TODO
Document Charm Tools: TODO
Document Amulet: TODO
Review drafts from previous docs: TODO
Bring in content from juju-core/doc: TODO
Embed searching into the docs: TODO
Stack Tack integration: TODO
UX feedback on docs: TODO
Improve contributing to the docs including local setup: TODO
More examples from flagbearer charms: TODO
Document juju for private clouds: TODO
* Blueprints in grey have been implemented.