Technical writing with Continuous Integration and docs-as-code
The post reflects a creative “book tasting party” at a school library, inspiring thoughts of a similar event for documentation sites. It highlights different static site generators—Sphinx, Astro, Hugo, Jekyll, MkDocs, and Docusaurus—each compared to a beverage, emphasizing their unique features, strengths, and suitability for documentation projects.
When using docs-as-code techniques, writers might hesitate to work with others on content deliverables, and developers might feel they have little to contribute to the documentation. I assert is that no one can know everything, so distribute the workload by writing together just like you collaborate together on code. What about reviews? How do you maintain quality while working […]
I like to point people to GitHub Pages when they want to learn Git. How about three options for learning Git and GitHub with doc projects?