This talk was presented at API The Docs Virtual 2020 event series on 4 November. We are honored to share the video recording, slide deck, and talk summary below. Enjoy!
Visit the API The Docs 2020 recaps overview to explore all presentations this year.
In 2017 first conversation about moving to docs-as-code/DocOps. Issues were that for almost every solution they had to use plugins, the fronted tech was unfriendly, the possible tools didn’t eradicate collaboration barriers, and most of them used unconventional documentation formats.
Now, at Adyen, the documentation team is managing 2000+ pages of documentation, having 1000 reused items for different audiences in a collaborative, central, crowd-sourced docs-as-code environment based on Markdown and Github. They are working closely with the CMS developers to have a convenient and useful IDE (integrated development environment) and they write their own extensions and tools to test and publish their docs.
DocOps involves facilitating a content flow that is collaborative, agile, continuous, enables reuse; it helped create a culture that serves documentation in a way that understands how techwriters work.
Their DocOps tools are about to keep the docs flowing.
Technical writers are frustrated by having to update:
Watch the video recording for a live demo.