Sans CMS.
What could managing a website look like without a traditional CMS?
A site to build
the idea around.
Sans CMS explores a different way to manage a website: keeping the content alongside the code, and working on both through conversation.
I’m using this personal site to try it out. Projects, writing, and the occasional change of direction give the experiment something real to work with.
The question behind it
Less managing.
More making?
A personal website should have room to change as your interests do. I’m curious about what happens when changing the words, the design, and the way the site works can all be part of the same conversation.
That’s the idea I’m exploring here. It’s still an experiment, with plenty left to figure out.
Learning by
building it.
The process is part of the project.
So far, that has meant shaping the homepage, trying a more expressive About page, and finding different ways to tell each project’s story. Some ideas work better once I can see them on the page.
Content lives in Git alongside the site, built with Next.js, TypeScript, and Tailwind. Vercel previews let me try changes before deciding what to publish.
The questions are still open: what feels easier this way, what needs more structure, and how much of the process can become useful beyond this one site?
See the About exploration