Building in Public

There is something clarifying about working where anyone can watch. Not because the audience matters — most of the time nobody is watching — but because it changes how you think about the work.

Why open?

When you know the code is visible, you slow down just enough to name things properly and delete the shortcuts you would normally leave for later. The commit history becomes a kind of journal.

What I'm using

This site is built with Next.js, TypeScript, and Tailwind CSS. Content lives in MDX files checked into the repo. There is no CMS, no database, no admin panel. Just files.

That constraint is deliberate. I want the simplest possible system that still lets me:

• Write blog posts in Markdown
• Show photographs with metadata
• Run small experiments at their own routes
• Sell a few prints eventually

What comes next

The immediate plan is to finish the core pages, add a handful of real posts, and start publishing photographs. After that I'll look at RSS, tag filtering, and the print shop.

One step at a time.