Release documentation is often written late in the development process; we think we can't start to write content until the software is stable, tested and ready for release. But that's the worst time to access SMEs, do the research, and write good-quality content, as we create content in a rush, or release it late. It’s a lose-lose scenario for both writers and readers. If we look at code development, we see that Continuous Integration (CI) and Continuous Delivery (CD) practices solve a similar problem. David will describe how he is adopting a CI/CD solution for documentation management, by "shifting down" to turn everyone into writers, and by "shifting left" to write documentation earlier.