Digital products
A personal website is not an online résumé
A personal website becomes useful when it stops archiving credentials and starts organizing ideas, projects and decisions as a living system.
Most personal websites start aging the moment they are published. The portrait is ready, the professional summary has been polished, the most presentable projects are in place and every social link works. Then almost nothing changes.
The problem is not a lack of polish. It is the underlying model. An online résumé treats the website as a photograph: it records a professional version of someone at a particular moment. An editorial system treats the website as a practice: it organizes ideas, projects and decisions over time.
That difference changes what should be built. The question is no longer “which sections do I need?” but “which publishing cycle can I sustain?”
Credentials inform; arguments differentiate
Roles, experience and tools help readers understand the writer's context. On their own, however, they do little to distinguish one person from another. Many people can hold similar positions, use similar technologies and list comparable responsibilities.
Judgment is much harder to duplicate.
How does this person interpret a problem? Which distinctions matter to them? Where do they disagree with the prevailing view? What did building something teach them? Which criteria do they use to choose between two reasonable options?
A good personal website makes that judgment visible. It does not need to turn every opinion into a manifesto. It only needs to publish enough reasoning for readers to understand how its conclusions were reached.
That is why an essay with a clear thesis often reveals more than a long inventory of skills. The inventory asserts capability. The argument makes it possible to examine it.
The editorial loop is the primary unit
It is natural to start a website by designing the home page. But the home page is only the surface of a system that must keep working after launch.
The central component is a simple loop:
- a question or observation appears;
- it is captured before it disappears;
- the note is developed until a thesis emerges;
- the thesis becomes an essay, a note or a project;
- the new material is connected to what already exists;
- older ideas are revised when the author's understanding changes.
Without that loop, the website depends on occasional bursts of effort. Every publication begins with a blank page, competes with everyday work and seems to demand a definitive conclusion. The predictable result is a carefully executed launch followed by silence.
An editorial system makes each next step smaller. Not every observation needs to become an article. Not every experiment needs to be presented as a finished product. What matters is giving each piece a format that matches its stage of development.
Different formats carry different commitments
Putting every piece of content into one chronological list creates a false equivalence. An exploratory note, an argumentative essay and a working project do not make the same promise to the reader.
A simple editorial architecture can distinguish between:
- notes for questions, lessons and hypotheses that remain open;
- essays for arguments developed enough to support a conclusion;
- projects for artifacts, tools and experiments that have been built;
- references for books, links and other material that informs the work.
This separation is not bureaucracy. It is a form of editorial honesty. It makes room for an unfinished idea without disguising it as certainty, and for an early project without overstating its maturity.
It also creates paths for development. A note can gather context and become an essay. An essay can expose a problem worth turning into a project. A project can produce lessons that revise the original argument. The website begins to record relationships rather than isolated items.
Projects and writing should explain each other
A conventional portfolio shows outcomes. A conventional blog shows ideas. A more useful editorial system brings the two together.
A project without context can become little more than an image, a name and a technology list. Readers can see what was made, but not why its decisions mattered.
Writing with no contact with construction can have the opposite weakness: it offers a coherent view without showing how that view responds to constraints, tradeoffs and consequences.
When projects and essays coexist, each provides evidence for the other. The project exposes concrete decisions. The writing explains the criteria behind them. This connection is more informative than adding more cards or documenting every tool involved.
The home page should orient, not persuade
Many personal home pages imitate commercial landing pages. They open with a broad promise, repeat benefits, accumulate calls to action and try to turn every visit into a conversion.
An editorial system has a different job. Its home page should help readers answer a few questions quickly:
- who maintains this space;
- which subjects belong here;
- which thesis or project best represents the work;
- what has been published recently;
- where to find projects and additional context.
This favors a restrained interface. Hierarchy, typography and rhythm matter more than the number of components. Design does not have to disappear, but it should reduce the effort required to find and read an idea.
In this setting, minimalism is not just an aesthetic preference. It is a product decision: fewer competing elements leave more attention available for the content.
An owned channel does not have to be the only channel
Publishing on a personal website does not require abandoning social networks, newsletters or other platforms. Those channels remain useful for distribution and conversation. The difference is refusing to make them the only archive of the work.
Platforms organize material around their own objectives. A personal website can organize it around the author's logic: by subject, relationship, maturity or sequence of learning.
The value is not merely controlling a domain. It is preserving continuity. A new essay can point to an older note. A project can collect the writing that explains its origin. A revision can show that a conclusion has changed. Over time, those links form a structure that a publishing timeline rarely provides.
Maintenance is part of the product
Thinking of the website as an editorial system also changes the definition of done. Launch is no longer the end of the project. It is the beginning of a routine.
That routine does not need to be intense. It needs to be clear. Capture ideas, select a few to develop, publish them in the right format, connect the new material and revise what is no longer precise. That is enough.
The most useful test is not whether the website looks complete today. It is whether its structure makes the next publication easier tomorrow.
An online résumé tries to compress a trajectory into one stable page. An editorial system accepts that work, interests and understanding will keep changing. Instead of hiding that movement, it turns it into the most valuable part of the website.