Raklet engineering docs¶
Welcome — this is the internal engineering knowledge base for rakletv3.
Looking for something?
Hit s or / to focus the search box, or use the left nav — pages are grouped by feature area (Engineering, CI, Testing, Payments, Membership, Coupons, Events, Jobs, Portal, Settings).
Product design — the memory of the product
Every design doc, CEO plan, decision record, and presentation deck behind what we ship is catalogued under Product design. Start there to understand why a feature looks the way it does and what was deliberately cut.
Most-read pages¶
- Testing
- Browse-tests overview + environments — visual status + how local / ci-vm-1 /
.raklet.netvalidate a change - Migration prompt (Selenium → browse-tests) — copy-paste system prompt for Codex / Cursor / Claude
- Payment-sandbox fixtures contract — env-var contract and how to wire a sandbox
- Migration checklist — per-row source of truth
- Migration batches — the 16-batch plan
- Browse-tests overview + environments — visual status + how local / ci-vm-1 /
- Engineering
- Fast-build PR notes — view precompilation + fast build script
- Local IIS setup —
*.raklet.orgon Windows - IIS worktree branch previews — preview a branch without disturbing main
- Operations
- Dedicated CI runner plan — ci-vm-1 setup
- Hot tables registry — tables to be careful with at prod scale
How this site is built¶
Static site generator: mkdocs-material. Source: the docs/ folder in this repo. Every push to master triggers a workflow that rebuilds and deploys to GitHub Pages.
Want to edit a page? Click the pencil icon in the top right of any page — it opens the source on GitHub. Pull-request the change like any code edit.
Adding a new doc¶
- Drop a Markdown file under
docs/in the appropriate subfolder (see the left nav for the taxonomy). - Add a line for your new page to the
nav:block inmkdocs.ymlso it shows up in the sidebar with the title you want — auto-derived titles look ugly (Custommembership Status One-Time Task). - Open a PR. The mkdocs build runs on the PR; deploys on merge to
master.
For HTML files (status pages, dashboards), drop them in docs/ exactly like the Markdown ones — they're served raw and linked from index.md.
If you move or rename a page, add a redirect in mkdocs.yml under plugins → redirects → redirect_maps so existing bookmarks keep working.