dimstack.net is where I ship in public: the blog, the project index, and the scratchpad for everything that does not deserve a long essay yet. Today it is actually live — DNS, SSL, the boring bits — and that matters to me because the site is not a brochure. It is part of the same pipeline I use for real work.
I build with Forge: a Python-first project management and scaffold system that keeps manifests, graphs, and agent context honest. Forge is the jig I measure against before I cut code. This Astro install was planned there first — routes, layouts, content collections — so when I open the repo I am not guessing what belongs where.
What is next is the fun part. I am deep on a workout app, growing the LifeOS ecosystem of small tools that talk to each other, and standing up tools pages (like a Forge dashboard) so visitors can poke at ideas, not just read about them. I want interactive projects people can use, not only star on GitHub.
The irony I like is that this blog runs on the same toolchain as the rest of my stack. Posts are content, the graph stays in sync, and when I add a route or a card component I treat it like any other Forge-managed surface. No separate “marketing repo” fantasy — one habit, many surfaces.
If you are here from a link or a search: welcome. I will write about graphs, tooling, Flutter when it bites, and whatever breaks when I ship. Today is the line in the sand for dimstack going live; everything after this is iteration in the open.
Hitting publish on 23 April 2026 is mostly a ritual — the stack was already real — but rituals matter when you are trying to keep your own bar honest. Consider this the first commit on the public branch.