Git is the distributed version control system under every line of code we ship; GitHub is where that history lives and where collaboration happens — pull requests, code review, issues, and CI/CD via Actions. Content-as-code workflows make this more than developer plumbing: for our git-resident content, publishing is a commit, and every change to a client's site carries a reviewable history.
How We Use It
- Reviewable, revertible history for every code and content change
- Pull-request workflows for human and AI-agent contributions alike
- CI/CD pipelines and deploy-on-push via GitHub integrations
Backend & Runtime
Why this matters: Choosing the right runtime and hosting improves reliability, security, and developer velocity from day one. We choose runtimes and hosting that balance security, developer experience, and performance. Our defaults favor fast iteration locally and reliability in production, with growing adoption of secure-by-default platforms. Preferred defaults: Bun for local dev, Node.js for production, Vercel for hosting and edge.