doering.ai

doering.ai is this portfolio site — an Astro 7 static build with Tailwind v4, the Irix design system, a pixel-flora simulation, and adversarial merge-request review. It is the artifact you are reading right now.

The problem

A portfolio has to ship its own evidence. Most portfolio sites hand-write their project claims and then rely on styling to make them convincing; the claims and the proof live in different systems, and they drift. A static site that generates its project data, runs its flora simulation at build time, and gates every merge request through adversarial review is overbuilt for a portfolio — and that overbuilding is the point.

The approach

The site is an Astro 7 build with Tailwind v4 and the Irix color system providing the design tokens. A pixel-flora simulation — a virtual-pixel engine that runs in both the browser and at Node build time — generates the botanical visuals purely from buffer operations with no CSS filters, shadows, or overlays. An offline botanical research pipeline (flora-refs) and a unified pixel system keep the simulation grounded in real plant morphology. Project data is generated, not hand-typed; a content-freshness checker, `astro check`, 35 tests, and an html-validate pass gate every build. Adversarial MR review catches regressions before they merge.

What it demonstrates

A stage-8 published site with 35 tests, 22 docs pages, CI, pre-commit hooks, full type coverage, and adversarial review on every merge applies production-grade rigor to what most teams treat as a weekend project — the portfolio as a running demonstration of the practices it advertises.