Why it exists
I wanted an internet home that behaves like a workshop rather than a portfolio template. It needs to hold finished projects, rough logs, articles, and pages that change over time without turning every update into a development task.
How it works
The source is deliberately ordinary:
- projects, articles, logs, and pages are Markdown files;
- a small Node build script validates the content and generates static HTML;
- a generated index keeps the content portable for future search or integrations;
- the finished site can be hosted anywhere that serves static files.
There is no database, client framework, or dependency chain between the writing and the published page.
Editing model
Each kind of content has its own folder:
content/projects/publishes to/projects/;content/posts/publishes to/blog/;content/logs/publishes to/log/;content/pages/creates optional standalone pages.
The Obsidian vault is the private editorial layer. Only notes explicitly marked for publication should cross into the repository.
Design decisions
The interface uses rows, borders, and clear type instead of floating panels. The implementation is original, framework-free, and shaped around the writing rather than dropped in as a demo.
The result is meant to feel more like a well-kept technical notebook than a startup landing page.