Documentation lives in three places: a Confluence nobody updates, a GitHub wiki that's two major versions behind, and the heads of the senior engineers who wrote the system. None of these is where developers actually work.
VibeControls Docs brings documentation to the Vibe — the same place where sessions, environment variables, and actions live. Write your docs in Markdown (or HTML), store them in the project repository, and point the docs builder at the folder. VibeControls compiles them asynchronously in the background.
The resulting documentation site is embedded in the Vibe detail view. Anyone who opens the Vibe sees the current, compiled docs immediately — no separate URL to remember, no confluence login, no wiki drift.
The async builder means you don't block on a compilation step. Make a change to a Markdown file, trigger a rebuild, and the embedded docs update without leaving the Vibe dashboard. Multiple documentation sites per Vibe are supported, making it practical to embed user-facing docs, API reference, and internal ops runbooks in the same place.
Do it yourself
Build a documentation site from Markdown and embed it directly inside your project Vibe, updating it whenever you edit your docs.
Open your project Vibe and click the "Docs" tab at the top of the detail view.
You should see: The Docs panel for your Vibe opens, ready for you to set up a documentation site.
Ready to make this your story?
