9/13/2025

plutov/oq: Terminal OpenAPI Spec viewer

Terminal OpenAPI Spec viewer. Contribute to plutov/oq development by creating an account on GitHub.

plutov

7/25/2025

Good Docs Describe, Bad Docs Prescribe - by Adam Ard

Of the four tenets of the Agile Manifesto, one gets the least attention:

Adam Ard

5/27/2025

Distr Launch Week: Our docs are now built with Starlight instead of Docusaurus | Glasskube

Comparing Docusaurus vs Distr incl. Design, SEO, DevEx, Extensibility and how we structured our technical documentation

Philip Miglinci

2/5/2025

General documentation — mgmt documentation

The mgmt tool is a next generation config management prototype. It’s not yet ready for production, but we hope to get there soon. Get involved today!

AsciiDoc

AsciiDoc is a human-readable, text editor-friendly document format evolved from plain text markup conventions and semantically analogous to XML schemas like DocBook.

AsciiDoc Working Group

11/26/2024

Your docs are your infrastructure - Stack Overflow

Fabrizio Ferri-Benedetti, who spent many years as a technical writer for Splunk and New Relic, joins Ben and Ryan for a conversation about the evolving role of documentation in software development. They explore how documentation can (and should) be integrated with code, the importance of quality control, and the hurdles to maintaining up-to-date documentation. Plus: Why technical writers shouldn’t be afraid of LLMs.

Eira May

documentation

11/10/2024

What docs-as-code means | Hacker News

I think this is a really good point in the post:

documentation

10/20/2024

What docs as code really means | passo.uno :: Fabrizio Ferri-Benedetti on Technical Writing

I’ve recently started a new job as a documentation engineer. While my work is largely the same as that of a technical writer, the sound and semantics of my new job title gave me some pause and made me think about what it really means to be doing docs-as-code. To say that it’s about writing documentation using the same tools and methods as software developers is correct, but fails to acknowledge the full consequences of the fact. Most descriptions of docs-as-code are naive because they stop at the implications of being developers’ attachés.

Fabrizio Ferri Benedetti