Thanks for helping improve docs.resq.software. This guide gets you set up.
- Navigate to the page you want to edit.
- Click the pencil icon ("Edit this file").
- Make your changes and open a pull request.
- Fork and clone the repository.
- Install the Mintlify CLI:
npm i -g mint. - Create a branch from
mainusing thedocs/<topic>convention. - Make changes; run
mint devto preview athttp://localhost:3000. - Run
mint broken-linksbefore pushing. - Commit and open a pull request against
main.
See README.md for the full local workflow.
- Active voice. "Run the command" — not "The command should be run".
- Second person. Address the reader as "you", not "the user".
- One idea per sentence. Keep them short.
- Lead with the goal. Start instructions with what the reader wants to accomplish.
- Consistent terminology. Don't alternate between synonyms for the same concept.
- Show, don't just tell. Include examples.
Brand tokens, typography, and component conventions are codified in custom.css and AGENTS.md. Use the existing tokens — don't introduce new accent colors, decorative gradients, or non-brand fonts.
This is the public-facing docs site. Keep content focused on the platform:
- Yes: API integration, concepts, architecture, authentication, examples for ResQ Tactical OS.
- No: Mintlify component reference, tutorials about MDX, AI-tooling setup for the docs repo. That belongs in this file or
README.md, not as a published page.