This site is built with Mintlify and lives in a separate repository from the main Swarms Python package. If you want to fix typos, add guides, update API pages, or improve navigation, you contribute here.Documentation Index
Fetch the complete documentation index at: https://docs.swarms.world/llms.txt
Use this file to discover all available pages before exploring further.
Documentation repository
The-Swarm-Corporation/swarms-framework-docs on GitHub
What belongs in this repo
Use swarms-framework-docs for:- MDX pages (guides, concepts, examples, community, API reference content)
docs.json(site name, theme, navigation, tabs)- Images and static assets referenced from the docs
docs/, follow Contributing to Swarms and the main framework repository linked from GitHub.
Quick start: edit on GitHub
- Open the repository and browse to the file (for example under
concepts/,agents/, orcommunity/). - Click the pencil icon Edit this file.
- Commit to a new branch and open a pull request.
Local preview
For larger edits, preview the site before you open a PR.-
Fork and clone the docs repo:
Add the upstream remote if you plan to sync often:
-
Install the Mintlify CLI (requires Node.js):
-
Run the dev server from the repository root (where
docs.jsonlives): - Open http://localhost:3000 and verify your changes.
mint update and try again.
Project layout
| Path | Role |
|---|---|
docs.json | Site config: theme, colors, navbar, navigation (which MDX files appear in each tab) |
*.mdx at repo root | Top-level pages (for example introduction, quickstart) |
Folders (agents/, concepts/, api/, …) | Grouped MDX pages; paths match entries in docs.json without the .mdx extension |
AGENTS.md | Notes for humans and AI assistants working in this repo |
navigation.tabs[].groups[].pages entry in docs.json, otherwise it will not appear in the sidebar.
Writing conventions
These align with the repo’s CONTRIBUTING.md and AGENTS.md:- Use active voice and address the reader as you.
- Keep sentences short; one idea per sentence.
- Start procedural sections with the outcome the reader wants.
- Use sentence case for headings unless a product name requires otherwise.
- Bold UI labels when describing clicks: Settings, Submit.
- Use code formatting for commands, file paths, and identifiers.
Card, Note, Warning, AccordionGroup) when they improve scanning; match patterns used on neighboring pages.
Before you open a pull request
-
Confirm new or moved pages are wired in
docs.json. -
Run link checks from the repo root:
- Keep the change focused (one topic or fix per PR when possible) so review stays fast.
Conduct and help
- Follow the Code of Conduct.
- Questions about Swarms usage are a better fit for Discord or FAQ; use GitHub issues on the docs repo for site bugs or clear documentation gaps.
Thank you
Improvements to this documentation help every Swarms user. We appreciate your contributions.