What is the difference between "docs as code" and "docs as product?" Alex discusses the approach of "docs as product"; what is it, is it relevant to you, and pitfalls to avoid when starting with "docs as product." He also does a deep dive into how to actually implement this type of product strategy for your documentation. What is traditional technical documentation, and how does it differ from "docs as product"? Where should I start to implement "docs as product"? Is your documentation pre or post-sales? What type of product do you have? How does this change the way I relate to my technical documentation?
Music by: BeatsbyAlf - Fat Cat Beats Comments, questions, or to submit "a word to retire": Email: fiedler.alex@gmail.com