Writing Backwards: Documenting the End-of-Life of a Product
summary
Manages the documentation for the end of Red Hat Network and the migration to Red Hat Subscription Management and shows concrete steps: a phased shutdown: UI then update infrastructure then API, an FAQ kept as a living document, a product page with banners and linked migration guides, and cross‑team work with marketing support QA. Measures success by tracked migrations and active account numbers and by spikes after email blasts. Schedules docs three to six months ahead and preserves final end‑state pages so users can find the last supported instructions.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:44"Regular Genres" for Documentation
- 3:13Migration vs. Total Shutdown
- 5:20Service vs. Product
- 7:16"Genres" for EOL Documentation
- 11:11Resources for Documenting This Way
- 15:52Red Hat Subscription Management
- 18:39Thank you!
related talks
23mDocumenting your software’s last days
26mEvolution of Product Documentation
41mLong-term Documentation Maintenance
31mHow We Deprecated 500+ Articles: Cleaning Up Documentation at Scale
30mBuilding technical documentation as a product at scale
40mFrom resistance to adoption: navigating the challenges of docs-like-code
40mThe Rocky Road to DocOps
37mTaking a step back: Analysing your documentation