disqualifier ed4e558dca tone down advertisey copy

- index.md: 'building and shipping with Rethink Studios' -> 'building and
  shipping on our network' (it's the network, not the company)
- workflow.md + its index card: 'how we actually work day to day' ->
  'get hands on with how we dev'
- deploy.md: drop the 'see the light / ready to host whatever you've built'
  pitch for a plain 'how a project gets onto rethink-net'; trim the now-
  duplicate eligibility tip

Signed-off-by: disqualifier <dev@disqualifier.me>

2026-06-29 21:23:34 -04:00

1.4 KiB

Raw Blame History

rethink development

The reference for building and shipping on our network: the shared libraries, the coding standards, and how to get a project deployed.

This is a public site — it documents generic patterns and conventions. Real infrastructure specifics (hostnames, internal IPs, exact topology, secrets) stay out of it; examples use placeholders like <dev>, <project>, and /srv/....

Sections

:material-package-variant: Libraries

The live list of the rethink-public library suite, pulled straight from Gitea — each entry links to the repo, where the README and tags live.
:material-ruler-square: Standards

House coding standards — file hygiene, docstrings, type hints, linting, and how we handle errors.
:material-sitemap: Workflow

Get hands on with how we dev — our Gitea, git habits, and the plan-in-chat / build-in-Claude-Code flow, plus shell setup.
:material-language-python: Virtual environments

Project-based Python isolation — local .venv, Makefile, or Docker — and local version management with pyenv.
:material-rocket-launch: Deploy

How to get a project running on rethink-net — containers, paths and mounts, permissions, and secrets.

1.4 KiB Raw Blame History

rethink development

Sections

1.4 KiB

Raw Blame History