Docs in the same editor as your blog
Guides, references, and tutorials use the same block editor and content model as your posts — one tool to learn, one place to search, one system to keep current.
Product · Docs
Versioned product docs in the same system as your blog and changelog — written once, connected everywhere, and kept current as you ship.
Why docs belong here
Every team knows the pattern: the product ships on Tuesday, the docs catch up in three weeks — if anyone remembers. Meanwhile customers follow outdated instructions, file support tickets, and quietly lose trust.
The root cause isn't laziness — it's that docs live in a separate tool from everything else you publish. Kascade Docs puts them in the same connected system as your blog and changelog, so a product change flows through every surface it touches, in one pass.
What you get
Structured, versioned, and connected — the way documentation should have always worked.
Guides, references, and tutorials use the same block editor and content model as your posts — one tool to learn, one place to search, one system to keep current.
Cut a docs version when you cut a release. Readers on v1 see v1; readers on v2 see v2. No more "the docs say one thing, the product does another."
Link a changelog entry to the doc it changes and the blog post that announces it. Kascade keeps the references intact, so nothing drifts apart.
When your product changes, Kascade flags the docs that mention what changed and drafts the update. You review, approve, publish — minutes, not sprints.
What product and developer-experience teams ask before switching.
Docs is rolling out to early-access teams alongside Blog. Join the list and we'll reach out as spots open.
Or see pricing first.