Contact

Get in touch
This site

The site is engineered like the work it presents.

Seven steps take a sourced professional record to a verified public page. This page documents them so the next engineer can run the same process — and so this one can be held to it.

The process

From record to website, the way a process runs.

A site about process engineering should be built like one: defined inputs, a controlled conversion, and verification before release.

  1. Source the record

    Everything starts from a sourced research package: verified institutions, dates, publications and recognition, each tagged with an evidence tier. Nothing publishes without a source.

  2. Model the content

    Research themes, publications, experience entries and news are structured content types, not hard-coded copy — so the site can filter, count and stay current.

  3. Design tokens first

    Palette, type scale, spacing and motion become semantic custom properties before any page exists. Components read tokens, never raw values.

  4. Build static

    Vite and Tailwind v4 compile to plain HTML, CSS and a little vanilla JS. Fonts are self-hosted; no third-party request ever leaves the visitor's browser.

  5. Make it findable

    Schema.org Person metadata, honest page titles, DOIs on every publication, and a sitemap — findability as engineering, not luck.

  6. Verify

    Every page is a build input, so the build itself proves each page parses and every asset resolves. Accessibility floors and honesty rules are checked by hand.

  7. Iterate

    News, CV updates and the verification queue feed the smallest correct change. The record improves the way a process does: continuously, and on evidence.

Principles

Four rules the build cannot break.

Evidence over decoration

Every factual line traces to a source. What is unverified stays draft-stated on the page instead of quietly hardening into fact.

Content outlives design

Structured content first, presentation second — a future redesign re-uses the record without rewriting it.

Accessibility is a floor

Contrast, targets, focus and reduced-motion are entry conditions, not enhancements to schedule later.

Honesty is a design constraint

Forms that admit they are not wired, disclaimers that state employer boundaries, no vanity metrics — the constraints shape the interfaces.