Rebuilding atenaxproject.com: a case study in Structured Clarity

Atenax Project is the oldest name in the studio — my strategic consulting practice, founded in 2006. When it came time to rebuild its site this year, I treated it the way I’d treat a client engagement with an unlimited standard and a very limited calendar: full BMAD-Nova, spec before code, and a design concept strong enough to carry the whole build. This is how it went, because the process matters more than the screenshots.

The concept comes first, and it has a name

Before any layout existed, the site had a concept document and the concept had a name: Structured Clarity. Amber #F5C000 against near-black. IBM Plex Mono caps labels opening every section. border-radius: 0 on every button — no exceptions, because the practice sells precision and the interface should behave like it. Poppins for authority in the headlines, Inter doing quiet work in the body.

Naming the concept isn’t branding theater. It’s a decision-compression tool. Once “Structured Clarity” existed, a hundred downstream choices answered themselves: does this element get a rounded corner? No. Does this section open with a mono label? Yes. Every hour spent on the concept saved ten in the build, because the agents executing the build never had to guess what the site was trying to be.

The signature

Every site the studio builds gets one signature element — a single moment the design is remembered by, with everything around it kept deliberately quiet. For Atenax, it’s the System Boot: a load sequence where the dark page initializes like a system coming online before the amber floods the hero. It runs once per visit, respects reduced-motion preferences, and can be replayed with a URL parameter — a detail that exists specifically so the animation can be demonstrated on demand.

One signature. Not five effects fighting for attention. Restraint is the more difficult and more valuable half of the discipline.

The build: sessions, not sprints

The site was built in structured sessions, each with one scope, executed by coding agents against the spec. Every session started the same way: the agent reads the repo’s CLAUDE.md — a context file defining the tokens, the rules, the things it must never do — and the spec section for that session. Foundation first. Then the signature. Then the content sections. Then the blog system. Then integrations. Then a final pass where nothing new is built and everything is verified.

The stack is deliberately boring: Astro, Tailwind, Markdown content collections, self-hosted fonts, deployed from GitHub to Cloudflare Pages. Total client-side JavaScript measured in single-digit kilobytes. The publishing workflow for articles is a Markdown file and a git push. Boring stacks are a feature — every exotic dependency is a future maintenance appointment, and this site needs to still be trivially maintainable in five years.

What it proved

The Atenax build was never just the Atenax build. It was the proof-of-concept for the studio’s entire design language — the token system, the mono-label DNA, the session-based agent workflow, the CLAUDE.md convention. The site you’re reading right now, bbluestudios.com, was built in six sessions on the exact same skeleton, inheriting the discipline wholesale and spending its concept budget on its own signature instead of reinventing the foundation.

That’s the compounding I care about. The first build establishes the standard. Every build after it starts from that standard and raises it. The deliverable isn’t a website — it’s a system that produces websites, and the website is just the first thing it produced.

If you want the strategic version of this conversation applied to your own business, that’s what the practice does: atenaxproject.com.

— Orlando