Why Project Atlas Started with a Constitution Instead of a Homepage
Before designing a homepage for Project Atlas, I wrote a constitution. This note explores why defining principles before pixels has become the foundation for building a website intended to evolve over decades, not just launch successfully.
When I started Project Atlas, I expected the first thing I'd design to be the homepage.
Instead, I spent days writing a constitution.
No layouts. No components. No color palette. Just principles.
At first, it felt like procrastination. I was writing documents while the website itself barely existed. But over time, I realized that I wasn't delaying the work—I was doing the most important part first.
Every website eventually reaches a point where there are multiple "right" answers. Should this page exist? Should this feature be public? Is this animation worth keeping? Does this belong in the navigation? Without a shared set of principles, those decisions become subjective. They get revisited over and over again.
A constitution changes that.
It doesn't prescribe every future decision. It defines the values those decisions should be measured against.
For Atlas, that meant agreeing on ideas before implementation:
- Build for decades, not launch day.
- Document decisions, not just outcomes.
- Prefer clarity over novelty.
- Make it exist first. Perfect it later.
- Treat the website as an institution rather than a product.
None of these principles make the site more visually impressive. But together they make it more coherent.
I've spent most of my career designing interfaces. Atlas has reminded me that interfaces are often the visible result of invisible thinking. Good systems aren't held together by components alone—they're held together by consistent decisions.
The homepage will eventually change. So will the navigation, the typography, and probably the entire visual language.
The constitution shouldn't need to.
That's the foundation everything else is being built on.