Domain

Build & Delivery

Continuous integration, release pipelines, and the path from a commit to a running deployment.

Convention Build & Delivery

Actions

Local composite actions under .gitea/actions/ capture reusable orchestration steps, while the logic they orchestrate stays in the build system.

.gitea/actions/ 3

Architecture Build & Delivery

Automation & CI/CD

.gitea/ is the repository’s automation control folder: event-driven workflows and local actions that orchestrate the repository’s own commands.

.gitea/ 2

Contract Build & Delivery

Fingerprinted Cache Tiers

Content-hashed CSS and JS are cached for a year as immutable; everything else is revalidated on every request and kept fresh by invalidation.

public/ 2

Lifecycle Build & Delivery

Release Pipeline

Every change moves through the same Build → Test → Publish pipeline locally, on the pull request, and on merge, ending in a deployment only where there is one.

docs/RELEASING.md 2

Orchestration Build & Delivery

Static Site Delivery

make deploy is the whole deployment model: build the site, initialise and apply its Terraform root, upload public/, and invalidate the CDN.

scripts/deploy.sh 5

Orchestration Build & Delivery

Workflows

Workflow YAML decides when automation runs and in what order, and hands the work itself to stable repository commands and reusable actions.

.gitea/workflows/ 4