What is our tech stack

Pattern Automation’s public surface is static-first: hand-maintained HTML, shared CSS, and small JavaScript for navigation, themes, and demos. Neuro OS, agents, and customer integrations may live in other repos—this section describes how we work on the site and repo you are reading.

Web & content

Semantic HTML, shared stylesheets (for example landing.css, section CSS), and vanilla JS where interactivity is needed. We avoid pulling in a heavy client framework for the marketing and handbook shell to keep builds and reviews fast.

Hosting

Static hosting on Vercel (no required build step for the root site; previews align with branches/PRs when configured).

Source control

GitHub is the source of truth—see the Pattern Automation Daniil DeBak repository. Ship via pull requests, review, merge to the default branch.

Automation & tooling

Python 3 for content generators and maintenance scripts under scripts/ (for example regenerating day pages). Run locally or wire into CI when batch updates are needed.

Quality

Prefer small, reviewable diffs; smoke-check navigation, links, and theme toggles before merge. Add automated checks when they earn their keep (link checking, formatting)—we grow rigor as surface area grows.

Product & platform elsewhere

Services that power Neuro OS, billing, or agent runtimes use their own stacks in their own repositories. Document data flows, SLAs, and ownership there; keep customer-facing promises aligned with this handbook.