RFFL stands for Raging Fantasy Football League. The league began in 2002 at the University of Wisconsin-Stout. This repository is the canonical documentation system for league governance, seasons, team registries, finance, KORM, lore, and operational history.
Operating Principles
| Principle | Meaning |
|---|
| Data Integrity | Do not fabricate league data, scores, financial figures, player names, owners, or historical events. |
| One Source of Truth | Each fact should have one canonical location. Derived pages must point back to it. |
| Validate Everything | Important claims must be supported by Commissioner confirmation, ESPN data, registries, or approved source docs. |
| Machine-Readable First | Data should be structured enough for scripts and future tooling to use reliably. |
| Human-Readable Always | League members must be able to understand the same source material. |
Editorial Voice
RFFL pages should read like a clean league reference for the people who use it. The voice is direct, league-specific, and practical: answer the member’s question, use RFFL terms consistently, and keep exact details exact when the record supports them.
The full editorial and design voice standard is maintained in Design System as RFFL Editorial Voice, version 2026-05-15.
| Quality | Use it this way |
|---|
| League-native | Use RFFL terms, team codes, season labels, KORM, finance, and governance names when they answer the question. |
| Direct | Put the answer before the caveat. Avoid slogans, hype, and filler. |
| Useful | Help a member find a rule, compare a season, confirm a payout, or follow a ruling. |
| Clear about gaps | When a record is incomplete, say so clearly and keep the page useful. |
Knowledge Base Product Shape
| Layer | Role |
|---|
| Raw sources | canonical evidence in Markdown, CSV, Python, YAML, and JSON |
| Curated MDX | member-facing reading layer published by Mintlify |
| Verification scripts | local checks that prevent broken links, missing pages, and copy issues |
| Browser preview | final visual and navigation check before work is called ready |
Repository Domains
| Code | Domain | Folder |
|---|
| GOV | Governance | governance/ |
| FIN | Finance | finance/ |
| KORM | King of Rage Mountain | korm/ |
| REG | Registries | registries/ |
| SZN | Seasons | seasons/ |
| OPS | Operations | operations/ |
| INT | Integrations | integrations/ |
| TPL | Templates | templates/ |
| PROJ | Projects | projects/ |
| LORE | Lore | lore/ |
League Timeline
| Years | Platform and structure | Knowledge base treatment |
|---|
| 2002 | Yahoo Fantasy Sports, 10-team league | Founding-era historical coverage |
| 2003-2006 | Fanball Custom Leagues, 10-team league | Pre-ESPN historical coverage |
| 2007-2010 | Fanball Custom Leagues, 12-team league | Expanded pre-ESPN historical coverage |
| 2011-2020 | ESPN Fantasy Football LM, 13-week regular season | Structured ESPN-era season folders |
| 2021-present | ESPN Fantasy Football LM, 14-week regular season | Current structured season coverage |
Current Mintlify Scope
The Mintlify site publishes curated .mdx pages. Raw Markdown, CSV, Python, YAML, and JSON files remain in the repository as source evidence and are intentionally excluded from publication until they are converted into maintained knowledge base pages. Last modified on May 15, 2026