Our software documentation is part of how we talk to each other – our users, our colleagues, our community. It’s a way we demonstrate how we value each other – including how we value you.
We’ve understood the importance of this for some time, but actually finding a way to express those values in our practice is less easy.
One thing that has made it difficult at Canonical is the complexity of our engineering, product and services portfolio. Our software spans a range from single-purpose command-line tools to vertical ecosystems composed of dozens of discrete component products, created by dozens of independent engineering and product teams.
We’ve been able to create unified and coherent software product lines, but we’ve been less successful doing the same for documentation. We want to do better for our documentation users – this is how we’re going to do it.
A documentation transformation project
We know that merely valuing documentation is not enough to take us…
