It Is Almost 2026. Why Still Make a Personal Website?
A personal website is no longer proof that you can code. It is a place where your work can keep its own shape.
AI lowered the cost of building the site. Ownership, long-term structure, and freedom from platform formats are why I still wanted one.
TL;DR
The point is not nostalgia. The point is control.
A few years ago, I probably would not have bothered building a personal website. Not because I did not want one, but because the coding barrier was high enough to make it feel like a side quest.
AI changed that. With Gemini 3 Pro and GPT-5.1, vibe coding turned the site from a vague idea into something real: www.zillionvisionary.com.
But the reason to build it is not only that building became easier. I wanted a place where my notes, resources, project retrospectives, and future experiments could belong to me, grow over time, and avoid being squeezed into whatever format a platform happens to support.
The Cost Changed
AI made the website possible, but it did not decide why the website should exist.
The technical barrier used to be the biggest reason not to build a personal site. Now that barrier is lower, the real question becomes what kind of space is worth owning.
If this were a few years ago, I would probably have left the idea alone. A personal website sounded useful, but making it meant dealing with frameworks, deployment, styling, routing, and all the small details that punish beginners.
In the last couple of years, AI made something obvious: even people who do not code full time can now turn an idea into a working product instead of keeping it in their heads. That does not mean the work becomes automatic. It means the distance between intent and a first usable version gets much shorter.
So the question changed from can I build this? to what do I want this place to be?
Own the Archive
Platforms are convenient, but they still feel like rented apartments.
I do not want the primary copy of my notes, resources, and project thinking to exist only inside someone else's app.
Platforms are good at distribution. They are fast, familiar, and easy to publish on. But they are not the place where I want my primary archive to live.
The notes I write, the resources I organize, and the retrospectives I do after projects should be easy to back up, move, export, and reshape. Keeping that archive in my own hands gives me peace of mind.
-
01
Structure
I can design my own directories, indexes, collections, and links instead of forcing everything into one platform model.
-
02
Portability
I can back up, migrate, and export the work without depending on a single app's future decisions.
-
03
Preservation
I can decide how the data is processed, presented, and kept over the long term.
Beyond the Feed
Not everything I make belongs in a timeline.
Feeds are useful as an entry point, but a lot of work gets more valuable when it can be updated, linked, and revisited.
Most platforms are built around time. You post something, it enters a feed, people see it for a while, and then it sinks.
That is fine for updates. It is less useful for resources, portfolios, project retrospectives, or ideas that need to be revised over time. Those pieces are not only moments. They are parts of a larger knowledge base.
I wanted this site to become a long-term work archive: a place where old writing can stay findable, projects can point to each other, and small pieces can slowly become a clearer map of what I care about.
More Than Posts
Sometimes the thing I want to share is not a post. It is the thing itself.
A website gives me room to publish formats that are awkward or unsupported on normal platforms.
Platform formats are usually compressed into a few shapes: notes, videos, image posts, maybe links. That works for a lot of content, but not for everything.
Sometimes I want to share a file, a template, a downloadable resource pack, a small demo, an interactive page, or a project collection. Those are either inconvenient on most platforms or simply not supported.
A website is a canvas. I can design the page around the thing itself instead of bending the thing until it fits a feed.
-
01
Resources
Files, templates, downloads, and reference packs can live next to the explanation that makes them useful.
-
02
Projects
Experiments and tools can have their own pages, demos, notes, and update history.
-
03
Collections
Related writing and work can be grouped by meaning, not only by the date they were published.
Final thought
So this site is my digital garden.
It is a place I can design, update, and reorganize as my work changes. It does not need to replace platforms. It gives everything a home before it gets distributed elsewhere.
If you have had a similar thought, try vibe coding your own small corner of the web. Let different AI tools help with the building, but keep the shape and the reasons in your own hands.