Hallucinated Documentation
Documentation that
should exist
We dive into source code, parse official docs, mine community discussions, and synthesize comprehensive documentation for developer tools. Source code is truth.
Documentation Sites
Tools with hallucinated documentation
How It Works
From source code to published documentation
Source Code
We analyze the actual source code. Tests, comments, type signatures, architecture patterns. The source is truth.
Official Docs
Reference and link to official documentation. Identify gaps. Track opportunities to contribute upstream.
Community
Mine StackOverflow, GitHub issues, mailing lists, and blog posts. Real problems, real solutions.
AI Generation
Synthesize comprehensive drafts from all sources. Cross-reference for accuracy. Generate diagrams.
Human Curation
Review, edit, add opinions. Verify against source. Maintain quality and voice.
Philosophy
What makes this different
"These docs may be hallucinated. The source code definitely isn't."
Not Auto-Generated Garbage
We're not scraping README files and calling it a day. Every page is crafted with intent, verified against source code, and enhanced with practical examples.
Source Code Archeology
We dig into codebases to find features even maintainers forgot existed. Hidden flags, undocumented APIs, clever patterns in tests.
Community Wisdom
Real questions from StackOverflow. Real issues from GitHub. Real discussions from mailing lists. Distilled into practical FAQs.
Contribution-Friendly
Everything is in Markdown/MDX. Fork, edit, PR. No proprietary CMS. No lock-in.
Upstream-Aware
We track opportunities to contribute improvements back to official docs. Better docs for everyone.
Contribute
Help improve the documentation
Quick Start for Contributors
# Clone a doc site repo (e.g. copybara-docs)
git clone https://github.com/albertocavalcante/copybara-docs.git
cd copybara-docs
# Install and start dev server
bun install
bun dev
# Make changes to src/content/docs/
# Submit a PR