A theme is a surface. It gives you colors, fonts, and a layout. You install it, adjust a few settings, and move on. It works until it does not. When your needs change, the theme becomes a constraint.

A system is a structure. It gives you rules, relationships, and a way of thinking about your product. It grows with you. It does not need to be replaced — it needs to be understood.

The problem with themes

Themes optimize for first impressions. They are built to look good in a preview. They are designed to convert browsers into buyers.

But the people who use them — the ones who build real products — quickly discover the gap between what was promised and what is possible.

• Customization hits a wall
• Components do not compose well together
• Updates break things
• The original design intent gets lost

This is not a failure of any individual theme. It is a failure of the model.

What a system provides

A system does not try to look good in a screenshot. It tries to work well over time.

It provides:

• Consistent spacing that scales across screen sizes
• Typography rules that maintain hierarchy without manual adjustment
• Component patterns that compose predictably
• Constraints that prevent drift

The value is not in what it gives you. The value is in what it prevents.

Building with restraint

The hardest part of building a system is saying no. Every feature request feels reasonable in isolation. But systems degrade one reasonable addition at a time.

Good systems are opinionated. They make decisions so you do not have to. They trade flexibility for coherence.

This is the approach we take here. Not because constraints are fashionable, but because they work.

This is not a design failure. It is a design choice. These products are optimized for engagement, and engagement requires interruption.

But there is another way to build software.

Attention as a resource

Your attention is finite. Every notification, every animation, every unexpected change in the interface costs something. Most software treats this cost as zero. It is not.

Calm software acknowledges this. It does its job and gets out of the way. It does not celebrate itself. It does not demand that you notice it.

What calm software looks like

• It loads fast and stays stable
• It does not move things around after the page renders
• It uses typography and whitespace instead of color and motion
• It provides information without demanding a response
• It respects the back button

These are not features. They are qualities. You cannot put them in a changelog, but you feel their absence immediately.

Why this matters

The tools we use shape how we think. Frantic tools produce frantic work. Calm tools create space for focus.

We build products with this in mind. Not every product needs to be calm. But the ones that do — the ones used for writing, thinking, and building — should be.

This blog is one of them.

But for complex ideas — the kind that require nuance, context, and careful reasoning — the best interface is still a paragraph.

The limits of visual design

Visual design excels at orientation. It tells you where you are, what you can do, and what matters most. It is essential for applications, dashboards, and tools.

But it struggles with depth. A card component can hold a title and a summary. It cannot hold an argument. A grid layout can organize information. It cannot develop a thought.

For that, you need prose.

Why Markdown works

Markdown is not a design tool. It is a writing tool. It gives you:

• Headings for structure
• Paragraphs for ideas
• Lists for enumeration
• Code blocks for precision
• Links for references

Nothing else. And that is exactly right.

The constraint of Markdown forces clarity. You cannot hide weak thinking behind a beautiful layout. The words have to do the work.

Building for writers

When we built this blog, we started with the reading experience. Not the homepage, not the navigation, not the visual identity. The paragraph.

Every decision flows from there:

• Font choice: optimized for long-form reading
• Line length: constrained to prevent eye fatigue
• Spacing: generous, to let ideas breathe
• Color: neutral, to keep focus on the text

The result is not impressive. It is not meant to be. It is meant to be readable.

That is enough.