Docs-As-Code, my first approach
I was watching some videos about Technical Writing trends when I got speechless. At that moment, I realized that the tools and techniques I used for my daily work as a Tech Writer were kind of outdated. I think that was the first time I heard about “Docs-As-Code”.
I was so curious and excited about learning how to treat my documentation like code that I wanted to learn about adopting automation pipelines, dev tools, and a DevOps mindset for documentation purposes.
At Wizeline, I had the opportunity to join the DocOps Taskforce that we put together within the Technical Writing team; that is how we learned, experimented, and propagated this documentation approach.
Then, my friend and colleague Silvia Alvarado and I wrote an article about our experience implementing Docs Like Code and the solution we ideated. In the article, we explain the challenges we faced using our previous process, the steps we took to build a better solution, and the benefits of the new approach.
We wrote it on behalf of the DocOps Taskforce (Armando Salazar, Arunabh Nag, Isaí Cortés, Roberto Antelo, and José Luis Zapata) and the rest of the Technical Writing Team.
The article “Implementing a Docs Like Code Solution at Wizeline” was published on The Pulse, which is the official Wizeline’s blog.
To read the complete article, visit the following link: https://www.wizeline.com/implementing-a-docs-like-code-solution-at-wizeline/?fbclid=IwAR0aQqu1GuGAjE5pbz5M_lYmZZe_7UGc14HpWT--j_3iuiJ7hUQFKU7IeU8
