Own your docs in Git and publish them with dubstack
dubstack keeps documentation source in Git while providing hosted docs sites, dashboard editing, previews, and publishing workflows.
Key points
Connect documentation repositories instead of copying content into a locked content store.
Use pull requests and branch previews for documentation review.
Let AI and workflow automation draft changes without bypassing Git review.
Publish hosted docs from source-controlled MDX and configuration.
Why Git-native matters
Documentation is part of the product. Keeping it in Git preserves ownership, review history, and collaboration with engineering teams.
- -Docs changes can follow normal engineering review processes.
- -Content can be backed up, mirrored, and migrated more easily.
- -Agents can create draft changes without direct production writes.
Hosted publishing without losing source control
dubstack provides the hosted docs experience while Git remains the source of truth for content and configuration.
- -MDX files define documentation pages.
- -dubstack.json defines site metadata, navigation, theme, and behavior.
- -Sync and preview flows keep published docs aligned with repository state.
Questions
Do docs have to live in Git?
Git-backed documentation is the recommended path because it preserves ownership and review. Hosted starter flows can help teams begin quickly before deeper repository setup.
Can AI workflows still respect Git review?
Yes. The intended workflow is to draft changes and open reviewable updates, not silently mutate production documentation.