Tech Garden — This Site
ActiveMay 2026 — Present
My personal platform: portfolio, digital garden, changelog, and learning journal — one content pipeline, everything editable from an admin panel.
This site is itself a project. The premise: a personal site should be a living system, not a page you rebuild every two years. All content — notes, posts, experiments, learning progress, monthly changelogs — lives in Postgres and is edited through a private admin panel, so publishing a note costs less than writing a commit message.
Architecturally it bets on server-first rendering: public pages are React Server Components cached with ISR and revalidated by tag the moment any admin mutation lands. Search is Postgres full-text search behind a command palette; there is no external search service and no client-side data fetching on the public site at all.
Lessons learned
The polymorphic tags table was the right call for a single-author CMS — one tagging system instead of eight join tables. The cost (no database-enforced FK on the taggable side) is contained with delete triggers and by routing every mutation through typed Server Actions.