Here's a growing list of what I'm noodling on of late. I've been trying to answer the question of what an ideal Agile platform should have, to support fast and lean documentation (both creation and maintenance).
Much is shaped by my observations of how merging docs into a larger self-serve/community support site raises the bar on what we can and should demand. What goodies am I missing?
Agile implementation
- Easy to access (cloud; single-sign-on)
- Easy to scale to more users, higher usage
- Easy to selectively secure (serve both customer and internal needs)
- Easy to support (hosted; no customizations to stop upgrades)
- Easy to brand, set to custom domain, extend non-destructively (API)
- Easy to reskin (without update breakage)
Agile authoring
- Easy to create
- Easy to import rich content created elsewhere
- Easy to update
- Easy to release (for SaaS, queue up changes for release-day publication)
- Easy to revert, compare history
- Easy to reuse content (variables, conditions)
- Easy to embed media (screenshots, diagrams, slides, video)
Agile response
- Link to/from support cases
- Easy participation by Support
- Notifications of changes, comments
- Analytics reporting
Agile self-service
- Single-sign-on with entire community/product/support site
- Search across docs, blogs, forums
- Easy to print
- Easy to export
- Easy to subscribe
- Commenting, feedback
- Translate on demand
- Good findability via search engines
Comments