Zenith Build

Lead Architect & Author

The role

I led the architecture and authored Zenith, from the language and compiler through the runtime, CLI and docs.

What I owned

I owned the contracts between these parts: what an author writes, what the build accepts, and what the browser receives. Those boundaries need to be understandable in the docs as well as in the implementation.

Key work

I built the portfolio with Zenith to exercise the whole path. It brings together real routes, imported content, static output and a browser that still has to handle theme and navigation.

Result

The portfolio is a working artifact of that work. The Zenith case study links the authored route to the HTML it produces.

Visual evidence

The architecture has a front door.

The public-facing portfolio gives readers a way to try the work without reading a compiler first.

An excerpt from the compiled Zenith case study shows the output file, page title and work-zenith main element.

01 / Demo capture

A concrete build artifact

An authored route becomes the HTML served at that address. The code, the docs and this portfolio all have to agree on that contract.

View full size See the Zenith case study

Hope Media Group