Internal reference for the respira-docs → community hub transition.
Documentation.ai (SaaS hosted). Not Docusaurus, MkDocs, VitePress, or Next.js. The docs are built and deployed by Documentation.ai based on:
documentation.json— nav, sidebar, tabs, navbar config.mdxfiles — content (root + folders: builders, guides, tools, security, support, woocommerce, toolkits, troubleshooting, reference)openapi.yaml— API reference source
- No local build step in this repo.
- Documentation.ai pulls from the repo and renders docs at docs.respira.press.
- Push to main triggers automatic deployment (via Documentation.ai integration, not GitHub Actions in this repo).
| Location | Current | After Rename |
|---|---|---|
| GitHub repo name | respira-docs | community |
| GitHub URL | github.com/webmyc/respira-docs | github.com/webmyc/community |
| documentation.json navbar | GitHub: respira/vibe-coding, Support: support.vibe-coding.com | Update to community Discussions URL |
| .github/ISSUE_TEMPLATE/config.yml contact_links | N/A (new file) | github.com/webmyc/community/discussions |
Note: No hardcoded "respira-docs" or "webmyc/respira-docs" strings found in repo (grep). Documentation.ai likely infers repo from GitHub connection.
- Rename impact: If Documentation.ai is configured by repo URL (e.g. github.com/webmyc/respira-docs), it may need to be reconfigured to point at github.com/webmyc/community after rename. Check Documentation.ai dashboard.
- Edit this page: Documentation.ai may provide "Edit on GitHub" links. These will break when repo is renamed unless Documentation.ai auto-follows redirects (GitHub redirects renamed repos for a while).
- External links: Any external site linking to github.com/webmyc/respira-docs will need updates. GitHub provides redirects for renamed repos.
- CI/CD: No GitHub Actions workflows found in repo. Build/deploy is external.