A controlled language for writing unambiguous technical instructions
The sidebar no longer tries to list all 77+ docs, the homepage and projects index became searchable card grids, and GitHub Sponsors got promoted from a footer link to a sidebar button. Eight previously-undocumented repos were added.
A practical pattern for giving a persistent Letta agent a bounded documentation corpus, validating its citations, and promoting only reviewed findings.
The first consumer of my runner-set library — a CDK construct that runs GitHub Actions jobs on Lambda MicroVMs — was another of my own repos, and the migration was done by an AI agent. The Claude session that moved its nine CI jobs onto the runners filed a field report, and reading it back, every failure it hit traced to something the documentation didn't say, not something it said wrong. The docs never said whether a job can run Docker. The agent probed, hit a sudo failure (no_new_privs is se
A sitemap, favicon, and layout-owned metadata replaced per-page duplication that was advertising the homepage's description to every crawler, alongside 17 new or updated documentation pages.
Added or corrected AGENTS.md agent guidance in 49 repositories and fixed AT Protocol trademark/naming wording in 10, after a full source audit.
Memory repository for a Letta Code writing and document agent.
Centralized changelog and development log for croft.click.
My now-playing kiosk has a long install document, and it's a long document. Three hundred and ninety-three lines, eight sequential phases, six environment variables that each gate a different optional install path, and a fifty-line section on a particular display whose touch input lives on a separate USB cable from its video. In addition to this, I wrote a Claude Code skills bundle that walks the same install conversationally. The two ship together in the repo right now. The long doc is the fa
Updating Malachite documentation for new service support and optimizing client bundles.
Adding AGENTS.md and llms.txt files across repositories to improve AI discoverability and documentation.
Documentation for Humans
Travis Arnold demonstrates OmniDoc's type-checked documentation system and discusses performance optimization in his React-based UI libraries.
D’après 50 Lies told to new people about BDSM, par TylerRose (2018)
Source : Chronologie de l’histoire Leather : introduction par Tony DeBlase et autres
AWS is archiving its docs-on-GitHub experiment. Why open documentation still works at scale, drawing on lessons from launching docs.microsoft.com.
Why "just" and "works for me" are harmful phrases in tech docs and support, illustrated with a Linux-on-the-desktop experiment that went sideways.
How the MSAL team approaches developer-facing documentation - making engineers core contributors, not delegating writing to a separate content org.
A satirical tour of the worst API documentation patterns - manual HTML, no version control, no examples - and why each one wrecks developer experience.
[x089] SM 101 – A Realistic Introduction, par Jay Wiseman (1996, 1998) ISBN 9780963976383
Find the best samples for an Android topic
Build a personal evergreen knowledge base in Markdown using Hugo, the Docsy theme, and a Docker container for portable rendering.
Every software will eventually become a nightmare to maintain, unless we actively do something about it.
Generating Python API documentation from PyPI packages with a single CLI command via adg, an alternative to setting up Sphinx configuration.
Building adg, a Python CLI that wraps DocFX, sphinx-docfx-yaml, and type2docfx so a one-liner can generate API docs across Python, .NET, and TypeScript.
Generate Java API reference documentation using a custom DocFX doclet that consumes Javadoc output and produces HTML via DocFX templates.
Build and publish DocFX-generated documentation using a GitHub Actions workflow, with a containerized step that handles output deployment to the cloud.
Why YAML-based structured content beats freeform Markdown for API documentation at scale, drawn from work on docs.microsoft.com and DocFX.
Use doctainers, a set of Dockerized DocFX pipelines, to generate API documentation for Node.js, TypeScript, and Python libraries.
Generate and host technical documentation in the cloud using DocFX, Docker, and a static-site pipeline you can run on any provider.
A short video walkthrough of DocFX, the open-source documentation generator that powers docs.microsoft.com, covering setup and a first build.
Five takeaways from a year of generating API documentation at scale, covering author variability, tooling, samples, validation, and review loops.
Generate API reference documentation for .NET libraries with DocFX on macOS, including the ECMA2YAML pipeline used by docs.microsoft.com.
Building a cross-platform VS Code extension that performs docs.microsoft.com API documentation lookups, scaffolded with Yeoman and TypeScript.
Wire up a VSTS build pipeline to generate API docs from a NuGet package and publish the output to GitHub Pages on every commit.
Guest appearance on MSDevShow with Jason Young and Carl Schweitzer covering self-driving cars, documentation work, and developer community.
Build SpecBot, a GitHub webhook-driven Node.js bot that auto-creates issues for inline review comments on Markdown specification documents.
How the docs.microsoft.com team generates .NET API reference from compiled assemblies, handling versioning, multi-framework, and reliability at scale.
Reflections after a year working on docs.microsoft.com on why documentation systems matter and how publishing infrastructure shapes product adoption.