I configure docs-as-code documentation platforms — Docusaurus, Mintlify, or MkDocs — so your documentation lives in Git, deploys automatically on push, and integrates with your existing developer workflow.
Setup scope: platform installation and configuration; repository structure and file organisation conventions; sidebar navigation and category organisation; theme customisation; CI/CD deployment pipeline (GitHub Actions or GitLab CI deploying to GitHub Pages, Netlify, Vercel, or a custom host); OpenAPI/Swagger integration for auto-generated API reference; search configuration; versioning for multi-version docs; and a contribution guide for team members.
Platform selection guidance: Mintlify is the best default for developer-facing API documentation — polished, LLM-ready (auto-generates llms.txt and MCP server), and fast to set up. Docusaurus is the most flexible for large, multi-audience doc sites with versioning. MkDocs with Material theme is the top choice for engineering wikis and internal team documentation.
Deliverables: configured, deployed docs site; CI/CD pipeline that auto-deploys on push to main; contribution guide; and optionally, your existing Markdown or Confluence content migrated into the new structure.