Developers and DevOps are paid to code and do their DevOps stuff, not write and maintain documentation. They hate it, and we hate having to remind everyone to keep doing it.
Scriversi was created to address the needs and frustrations with current global documentation approaches that result in incomplete and outdated documentation. In the operations of development teams, deployments, contracts and technical reviews, there are daily frustrations of reminding DevOps and Developers to update their site documentation.
We often found ourselves having to create separate documents to protect Intellectual Property in a granular way.
As an example , in one deployment, the technical architecture and APIs used and published had to be separated from the commercial calculations and Service level agreements, compelling one to create and maintain multiple documents per client rather than one unified repository of all the related concepts and information.
With these three simple steps, we’ve managed to build a specialised documentation authoring platform that can stay up to date with external changes, keep documentation relevant, and retain security and access rules on a granular level that doesn’t exist anywhere else.
As distributed workforces grow, it is now more relevant than ever before to ensure that all our documentation is automatically updated and remains relevant at all times.