Write-ups, not articles
Each note is the long version of the "why this way" section from a case study. The case gives three paragraphs; the note gives the full account, with code and configuration.
The first note is not out yet
The section opens with the first text. Below is the queue — each one grows out of its own case study.
In the queue
- 01Workflows in YAML: when configuration beats codeFrom the case study: Freight accounting system
- 02One frontend, two portals: configuration from the backend instead of a forkFrom the case study: Client area
- 03Schema instead of code: JSON Schema as a way to keep configuration from falling apartFrom the case study: Low-code platform
- 04A React widget inside WordPress: why a separate repositoryFrom the case study: TRT ecosystem
- 0534 ACF blocks: handing page assembly to a content managerFrom the case study: TRT ecosystem
- 06Secrets in git without an external store: SOPS, age, helm-secretsFrom the case study: Self-hosted infrastructure