We solved this by introducing a process and a tool that enables us to run documentation as a program. We went a step further and now offer this solution as part of our product to our customers as a fully automated installation process. Instead of usual way of extracting pieces of code to build documentation we maintain documentation only and use it as code. This way we have a single source of truth that is maintained by our technical writers and easily testable at any moment by a click of a button.
In this talk I will bring the concept of runnable documentation closer to you and show how you can best adopt it in your organization. I will use an open-source tool rundoc (https://gitlab.com/nul.one/rundoc) in my examples with documentation written in markdown.