The Paperkraft blog
Practical guides to API documentation, technical writing and docs automation from the Paperkraft team.
What separates API documentation developers trust from documentation they abandon
The difference is rarely writing quality. It is whether a developer gets one successful request quickly, and whether the samples still run later.
Read the post →
Your support tickets are a list of missing docs
People who open a ticket usually tried your docs first. Read those tickets like an editor and they tell you which pages to write, retitle or fix.
Read →
API Documentation: Good vs. Great
Five specific patterns separate good API documentation from great. Most are structural changes teams can make without a rewrite.
Read →Why documentation matters more in 2026 than it ever has
Self-serve buying, AI assistants and coding agents have turned documentation into the place where evaluation, adoption and renewal get decided.
Read →How to structure documentation so AI assistants quote it correctly
Assistants now answer product questions before anyone reaches your site. What they say depends almost entirely on how your pages are structured.
Read →