Subscribe
Sign in
Home
📐 Planning Docs
⚡ Scaling Docs
🤖 AI & Tools
About
Latest
Top
Discussions
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
Developers aren't reading your docs
At least, not in the way they used to. They're asking AI from their IDE instead. Here's how to make that work for you.
Feb 22
•
David Garcia
1
"But it was working fine!"
Why your docs site breaks after four years of 'working fine
Feb 10
•
David Garcia
1
The friction problem: Why we skip steps (even important ones)
How a simple link fixed our broken docs review process.
Feb 2
•
David Garcia
2
January 2026
Your docs are talking. Are you listening?
How AI assistants turn user questions into product insights
Jan 21
•
David Garcia
3
1
How to get useful documentation feedback (not comma debates)
Vague requests get surface feedback. Here's how to ask questions that actually help.
Jan 14
•
David Garcia
3
1
New product, no docs yet? Start with documentation strategy
Why writing first creates chaos and how to plan your docs for success
Jan 6
•
David Garcia
3
1
December 2025
Reflecting on 2025: Growth and learning
A look back at a year of progress, collaboration, and results at TechDocs Studio
Dec 31, 2025
•
David Garcia
Our best tutorial was actually broken (we just couldn't see it)
12 user complaints revealed what our analytics couldn't
Dec 23, 2025
•
David Garcia
A tagging system for documentation review comments
Use a tagging system to stop debating what blocks merge.
Dec 16, 2025
•
David Garcia
2
Three tools, five steps, no consistency
Why screenshot workflows break (and what I'm building to fix it)
Dec 9, 2025
•
David Garcia
2
Reference documentation that never gets outdated
Define once. Generate everything else.
Dec 2, 2025
•
David Garcia
This site requires JavaScript to run correctly. Please
turn on JavaScript
or unblock scripts
