Subscribe
Sign in
Home
📐 Planning Docs
⚡ Scaling Docs
🤖 AI & Tools
About
Latest
Top
Discussions
How we onboard new hires with codelabs
One-to-one onboarding doesn't scale. Codelabs do.
Jul 2
•
David Garcia
2
June 2026
Anatomy of a good codelab
The parts that separate a codelab from a tutorial nobody finishes.
Jun 24
•
David Garcia
1
Codelabs are the internal docs your engineers are missing
Every team documents its own product. Nobody documents how they connect.
Jun 19
•
David Garcia
1
How we scope large docs migrations
Plan less, learn from one product, then scale.
Jun 9
•
David Garcia
May 2026
Nobody plans for redirects
Until users can't find anything, partners complain, and Google traffic disappears.
May 11
•
David Garcia
2
1
2
Why we still use Doxygen (just not the way you think)
Doxygen isn't dead. Here's how we turn it into docs users actually read.
May 5
•
David Garcia
April 2026
15 tips for better AI answers from your docs
What we tell companies after they add an AI chatbot, MCP server, or internal AI assistant to their documentation.
Apr 22
•
David Garcia
2
How to make your docs discoverable to AI agents
The basics that cover 90% of the work, plus what to do if you want to push further.
Apr 16
•
David Garcia
4
March 2026
We tried following a client's getting started guide
Half the code examples didn't compile.
Mar 25
•
David Garcia
2
Docs are fuel for AI. Not every company sees it that way.
While some companies eliminate their entire docs team, others are doubling down.
Mar 19
•
David Garcia
6
1
We added an AI assistant to a docs site. Support tickets went up.
Here’s why that’s actually a good thing.
Mar 11
•
David Garcia
4
February 2026
Slow builds were killing our docs
How we cut a Sphinx build from 30 minutes to under 3 by splitting PDFs into chapters and parallelizing outputs.
Feb 26
•
David Garcia
This site requires JavaScript to run correctly. Please
turn on JavaScript
or unblock scripts