Rasepi Blog
Rethinking knowledge in times of AI.
Documentation Platforms Built for Another Era
Confluence and Notion were built for a pre-AI model of documentation. They can evolve, but established platforms carry structural baggage. Newer systems can design for AI from day one.
Readers and Writers Are in Different Mental Modes. Why Does Every Tool Give Them the Same UI?
Documentation platforms force readers, writers, and AI into one interface. But consuming knowledge and creating it are cognitively different tasks. Rasepi separates them.
The State of Docs in 2026: Five Trends That Will Define the Next Era
AI readership is up 500%. Notion shipped 21,000 agents. Confluence got Rovo. GitBook published the State of Docs. Five trends from across the industry that tell us where documentation is heading.
Builders, Not Developers: How Claude Changed Who Your Docs Are For
The person integrating your API no longer reads your docs. They sit in Claude and describe what they want. Developer relations, API documentation, and the whole getting-started funnel need to be rethought for this new reality.
How Rasepi Translations Actually Work, And Why They Sound Like Your Team
Rasepi doesn't just translate your documentation into other languages. It learns your terminology, matches your tone, and lets every language version live its own life. Here's how.
Inside the Translation Engine: Glossaries, Style Rules, and Smart Retranslation
A deep technical walkthrough of how Rasepi's translation pipeline actually works: glossary resolution, DeepL style rules and custom instructions, content hashing, and the integration that ties it all together.
Stop Maintaining Five Copies of the Same Document
Most companies have onboarding_germany, onboarding_japan, onboarding_brazil. In Rasepi, it's just 'Onboarding'. One document. Shared steps translated, local steps per language. No more copies drifting apart.
The Business Case for Block-Level Localisation
Global teams don't just need translations. They need knowledge that works in every market, with each language carrying its own structure. Block-level localisation makes that practical.
Content Freshness, Part 2: Beyond Expiry Dates
Expiry dates solve accountability. But a document can go stale in a hundred ways between reviews. Part 2 explains how continuous freshness monitoring fills the gap.
Content Freshness, Part 1: The Metric Your Team Isn't Tracking
Your documentation might be technically correct today. But in six months, who checks? Freshness is about to become the most important signal in your knowledge base.
Teach Your AI to Ignore Stale Documentation
Your AI assistant treats a document reviewed last week the same as one nobody has touched in two years. Content governance fixes that.
Talking to Documents Feels Better Than Reading Them
Reading is powerful, but effortful. Conversation is older, faster, and more natural. Speaking to information often feels mentally lighter than scanning pages of text.
Inside the Rasepi Architecture: Plugins, Action Guards, and Pipelines
A deep technical walkthrough of how Rasepi's plugin system, action guard pipeline, and block-level translation engine actually work, with real code from the codebase.
Stay in the loop
New posts on documentation freshness, AI-ready knowledge, and building platforms that scale. One email per post.
Thanks! You're on the list.