As you'll see, I have a liberal view of what constitutes “technical documentation” at a software company -- probably more in tune with what many call “technical communications”.
This file (and others) does take a very software-centric view of documentation, please do keep in mind the hardware, process, academic and legal documentation that also benefit from DocOps. Even in the open source world there are the Raspberry Pi users who also have to create docs about their products.
(A quick scan of your TOC does indicate that you are aware of and have at least considered that DocOps has a role to play in areas other than software documentation. I encourage you to keep that view in mind.)
This file (and others) does take a very software-centric view of documentation, please do keep in mind the hardware, process, academic and legal documentation that also benefit from DocOps. Even in the open source world there are the Raspberry Pi users who also have to create docs about their products.
(A quick scan of your TOC does indicate that you are aware of and have at least considered that DocOps has a role to play in areas other than software documentation. I encourage you to keep that view in mind.)