field note
A homepage should be an edition, not a dashboard
Notes from designing a personal commonplace that can hold finished work, active questions, and the things I keep returning to.
Owning a domain for years creates a peculiar kind of guilt. The address feels like it should be doing something important, which makes every possible use seem too small.
A résumé is useful but thin. A blog asks for a cadence I may not want. A portfolio makes projects look finished and self-contained when the interesting part is often the question that led to them. A stream of links has personality but little shape.
The useful reframe was to stop asking which one of those sites this should be.
I want a commonplace: a deliberately edited home for what I build, write, study, read, and listen to. “Deliberately edited” is the important part. The goal is not to mirror every service where activity happens. It is to decide what is worth bringing home.
Why the homepage is manual
Most personal sites default to chronology. The newest post takes the largest space because a timestamp changed. That is simple, but it makes publication order stand in for editorial judgment.
This homepage works as a current edition instead. It selects one project, one piece of writing, and one item from the collections. New material can exist without automatically taking over the front page. Changing the edition is a conscious act.
That gives unlike things equal permission to matter. A durable project page can sit beside a short explainer about water towers. A repository can be present because its design is useful, not because I wrote it. “What represents me right now?” becomes a better editing question than “what happened last?”
The manual choice is intentionally stored in one small file. There is no popularity score, no engagement loop, and no algorithm pretending that recency is relevance.
Shelves need annotations
A list of books or repositories says surprisingly little. The personal part is the sentence beside the link.
Why would I tell a thoughtful friend about this? What idea did it sharpen? What should someone notice? Why is it in an antilibrary rather than a finished-reading list?
Those annotations turn collections from activity receipts into editorial shelves. They also make uncertainty visible. The antilibrary can contain books I want within reach without suggesting I have read them. A listening shelf can describe what I am paying attention to instead of manufacturing a year-end ranking.
The first edition keeps any unconfirmed selections in draft. That is less polished than invented certainty and much more useful for finishing each collection honestly.
Projects deserve endings, including “no”
Portfolio writing has a bias toward successful launches. That leaves out one of the more valuable kinds of work: an investigation that produces enough evidence to cancel itself.
Hive Mind Trader belongs here because its result was not a trading product. Its result was a tested premise and a disciplined decision not to ship the original idea. The project page can preserve the question, safeguards, method, and conclusion without converting research into a growth story.
bobby.menu is different. It is a living utility whose model keeps getting refined through use. Putting the two together makes the site more truthful than a sequence of polished case studies. Sometimes building reveals the next feature. Sometimes it reveals the exit.
A system small enough to keep
The implementation is intentionally modest: Markdown and YAML become static pages. There is no database or content-management system to operate. Images live with the content. Publishing should usually mean adding one file, previewing it, and deploying a new immutable build.
The site still has rules. Drafts do not leak into production. Future-dated work does not publish accidentally. Work-origin writing requires a source and a recorded review. Analytics is cookieless and limited to a small event vocabulary. These constraints are not enterprise ceremony; they are promises the site makes while it is still small enough to understand.
What this place is for
I do not need the domain to summarize an entire person. I need it to hold a useful selection without forcing every item into the same shape.
The success condition is simple: a visitor should be able to arrive for a project, notice an essay or collection they did not expect, and leave with a clearer sense of how I pay attention.
That feels like enough work for a URL.
AI-use note: I used AI assistants to explore the concept, compare visual directions, challenge the architecture, and help edit this field note. The selection of the “editorial commonplace” model and the final judgments are mine; the visible launch content should continue to distinguish assisted drafting from personal experience.