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.
Great news! Now you can try one URL for a GPT all about “Docs Like Code,” and you can ask a chat agent questions based on the books Anne Gentle has authored, like Docs Like Code: Collaborate and Automate to Improve Technical Documentation and Conversation and Community: The Social Web for Documentation. I used Retrieval […]
In open source, all sorts of interesting connections happen. In open source documentation, an even more narrowly defined group of folks connect the dots for others. Recently I was interviewed by Mirantis, an OpenStack services startup, about my involvement with OpenStack documentation. They’re doing a series of interviews with the technical leads in OpenStack. We […]