Rethink Development — public libs, standards, and deployment, in one handbook
Go to file
disqualifier 75ad61b06a add 'point your coding agent here' callout on the landing page
A tip admonition under the intro telling devs to point their coding agent
at the handbook for awareness of our libs/standards/deploy rules, with
copy-pasteable agent prompts in two tabs: from the live site, or from a
git clone of the repo.

Verified in-browser: tabs switch, prompts + clone command render, copy
buttons present; mkdocs build --strict clean.

Signed-off-by: disqualifier <dev@disqualifier.me>
2026-06-29 21:30:07 -04:00
docs add 'point your coding agent here' callout on the landing page 2026-06-29 21:30:07 -04:00
.gitignore restructure handbook to flat-page spec 2026-06-29 19:48:52 -04:00
mkdocs.yml add Virtual environments page (project isolation + pyenv) 2026-06-29 20:54:31 -04:00
README.md add README 2026-06-29 20:57:45 -04:00
requirements.txt pin build deps in requirements.txt for native host build 2026-06-29 20:56:50 -04:00

handbook

The Rethink Studios handbook — our public reference for the shared library suite, coding standards, the dev workflow, Python environments, and how to deploy on our network.

Live at docs.rethinkstudios.io.

What this is

A static documentation site built with MkDocs + Material for MkDocs. Markdown lives under docs/, builds to a static site/, and is served by the reverse proxy at the subdomain — no app process, just static HTML/CSS/JS.

The Libraries page is the one dynamic part: it fetches the rethink-public repo list from the Gitea API client-side at view time, so new libraries appear on the next page load with no rebuild. Everything else is static markdown.

Build

python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
mkdocs build            # -> static site/
mkdocs serve            # local preview at http://127.0.0.1:8000

Contributing

  • One topic per page, grouped under docs/, wired into the nav in mkdocs.yml.
  • Public — sanitize: no real hostnames, internal IPs, secrets, or exact topology. Use placeholders (<dev>, <project>, /srv/...).
  • Markdown: trailing newline, no trailing whitespace, LF line endings.
  • Commits signed (git commit -s).