Documentation Index
Fetch the complete documentation index at: https://docs.rffl.dev/llms.txt
Use this file to discover all available pages before exploring further.
Knowledge Base Maintenance
The Mintlify layer is a curated publishing surface. It should make RFFL data easier to browse and search without replacing canonical source files.
Local Commands
| Command | Purpose |
|---|
npm install | Install the Mintlify CLI package locally |
npm run dev | Preview the knowledge base locally |
npm run validate | Validate the Mintlify build |
npm run links | Check internal links |
npm run verify | Run the full local verification gate before calling work complete |
Content Workflow
- Update canonical source files first.
- Regenerate derived source pages when needed.
- Update the matching
.mdx knowledge base page.
- Run
npm run verify.
- Fix any failed checks before reporting the change as complete.
- Commit the source and knowledge base changes together.
Runbooks
| Page | Use it for |
|---|
| Source Conversion | converting raw source files into public MDX |
| Publication Checklist | pre-publish content checks |
| Verification Checklist | required local tests and browser checks |
| Add Season Or Source | adding new season/source coverage without weakening authority |
Publication Rules
| Rule | Reason |
|---|
| Do not publish raw CSVs by default | They are source evidence, not member-facing explanations |
| Do not publish scripts by default | They are implementation, not knowledge base content |
| Do not invent missing data | Preserves the “We Do Not Guess” policy |
| Keep source paths visible | Makes answers traceable |
| Mark provisional pages clearly | Prevents uncertain data from becoming accepted by search |
Season Coverage Rules
| Coverage | Maintenance rule |
|---|
| 2002-2010 | Represent as founding-era historical coverage until validated per-season source packages exist |
| 2011-present | Publish structured season pages only from source-backed season folders |
| 2026 | Keep marked partial until the season record is complete and validated |
Static Site Notes
The knowledge base should stay useful as a static documentation site. Search, navigation, source paths, and validation matter more than a separate chat surface for this project.