The links below are the references to the "docs-as-code" approach, writing style guides and the documenting tools:
- "Architecture Advice";
- "Awesome README;
- "CodeX Docs";
- "Commit Style Reference and Docs Auto Testing";
- "Companies Using RFCs or Design Docs and Examples of These";
- "Compas", Atlassian Tool;
- "Cortex Docs";
- "Diátaxis Docs Style Approach";
- "Docs-as-Code Tools";
- "Documenting APIs: A Guide for Technical Writers and Engineers";
- "Explo";
- "Flow Conference: Doc-as-Code Approach";
- "Fly.io Docs";
- "Gifski" converter;
- "Google Developer Documentation Style Guide";
- "History of Docs-as-Code";
- "How Canonical Systematically Improves Developer Documentation";
- "How Google, Twitter, and Spotify Built a Culture of Documentation";
- "How to Champion Investments to Improve Documentation";
- "How to Create Beautiful Docs (References)";
- "Measuring and Maintaining Documentation Quality" (for the tool see here);
- "Microsoft Writing Style Guide";
- "Mistakes of Engineers that Write Dev Docs";
- "PagerDuty: runbook";
- "Product Hunt" (the service of newly launched products);
- "RFC";
- "Take a screenshot on your MAC";
- "Technical Writing: a bibliography, tips, and tricks";
- "Why you Should Consider Using Docs-as-Dode";
- "Write the Docs".