Yes, I meant in regards to publishing. Thanks for sharing!
What are the expectations for product documentation? For example, does the doc set strive for an MVP-level to release at same time as the new version, and then the rest of the documentation is more reactive to what customers ask? Or, do you try to document as much as possible to circumvent support calls once there's a release? I would imagine in a CI/CD environment, you're hearing from the user more often to see what to work on next.
I'm also interested in how you use the CI server... Do you continuously push your content to a server to validate it, and then it's ready to go live? Who sets that up for you-- the documentation team or another department?
Our company is in the process of switching to a CI/CD environment, so everyone is learning at the same time, which makes it difficult to find the resources to create a system that focuses on the docs. Do you plug in with the source code of the product, or is documentation created and tested separately?