![Page 1: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/1.jpg)
Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles
Write the Docs EU 2016
@rachwhitton
![Page 2: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/2.jpg)
@rachwhitton
● Support background in web services● Began working on docs as a side project● Self-learning developer● Joined Pantheon in 2014 ● Automation and workflow enthusiast
About Me
![Page 3: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/3.jpg)
Docs or it didn’t happen!
![Page 4: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/4.jpg)
@rachwhitton
Requiring docs within releases
![Page 5: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/5.jpg)
@rachwhitton
Reality check
Docs won’t block releases until trust in delivery is established.
![Page 6: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/6.jpg)
Releasing software should be easy. It should be easy because you have tested every single part of the process hundreds of times before. It should be as simple as pressing a button.
— David Farley Continuous Delivery: Reliable Software Releases through Build, Test, and
Deployment Automation
![Page 7: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/7.jpg)
@rachwhitton
Docs must meet the same standards of reliability and repeatability before they can be enforced as a part of the release cycle.
Establishing Trust
![Page 8: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/8.jpg)
@rachwhitton
The Big Picture Milestones for Delivering High-Velocity Docs
Increase Project Visibility
Simplify Peer Reviews
Automate Grunt Work
1
2
3
![Page 9: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/9.jpg)
@rachwhitton
Increase Project Visibility
![Page 10: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/10.jpg)
@rachwhitton
Centralized Workflow
Collaborate across teams.
Work multiple issues simultaneously without blocking deployments.
Track issues and progress from a central location.
![Page 11: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/11.jpg)
@rachwhitton
Allow public contributions and document upcoming features in the open.
Open Source
![Page 12: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/12.jpg)
@rachwhitton
Integrate services such as GitHub within communication tools like Slack.
Dependable Notifications
![Page 13: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/13.jpg)
@rachwhitton
Simplify Peer Reviews
![Page 14: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/14.jpg)
@rachwhitton
Make Success Easy Prioritize the contributor experience of all roles and make improvements iteratively. Focus efforts on paths most traveled.
Simplify Peer Reviews
![Page 15: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/15.jpg)
@rachwhitton
Automate Grunt WorkBuilding and publishing content must be a repeatable and reliable process - started with the click of a button
![Page 16: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/16.jpg)
@rachwhitton
Automation
![Page 17: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/17.jpg)
@rachwhitton
Bots Handle the Grunt Work
Automated Deployment PipelineStage content on isolated environments w/public URLs automatically.Deploy to production with a single click.
Establish Trust with Automated TestsNo more surprises.
![Page 18: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/18.jpg)
@rachwhitton
Bells and Whistles
![Page 19: Delivering High-Velocity Docs that Keep Pace with Rapid Release Cycles](https://reader031.vdocuments.net/reader031/viewer/2022030309/58f2cb2e1a28ab596b8b4579/html5/thumbnails/19.jpg)
@rachwhitton
Next Steps
Continuous integration for docs isn’t the end of the road - it’s an essential tool for building trust.
For docs to truly become an enforced requirement of the release cycle, it needs buy in from everyone.