2026-06-11 · 5 min read · Rahul Chitturi
- markdown
- documentation
Not every team needs Confluence. Markdown in git gives you version history, review workflows, and portability. The friction is preview and sharing with non-technical stakeholders.
Recommended structure
- docs/ folder in the main repo
- One topic per file with clear filenames
- Index README linking to runbooks
- Templates for incident postmortems and RFCs
Preview and export
Edit with live preview before commit. Export PDF for compliance or exec reviews without giving everyone git access.