Technical writing

Notes on systems, shipping, and the decisions underneath them.

A technical blog should publish as quickly as a database record changes. This layout is designed for fast scanning, strong metadata, and markdown-driven posts from PocketBase.

Runtime-fetched from PocketBaseMarkdown-first publishingNo frontend redeploy for new posts

Featured article

Designing1 PocketBase content for a fast personal site

The site should behave like product software, not like a static brochure. That means content changes need to travel through a durable backend model while the frontend stays lean and cache-friendly.

April 20, 20267 min read
PocketBaseTanStack StartMarkdownPerformance
Read article

Archive

Built for ongoing publishing, not one-off updates.

System design / content pipelineFeatured

Designing1 PocketBase content for a fast personal site

A practical content model for publishing markdown posts from PocketBase without turning a portfolio into a heavyweight CMS build.

April 20, 20267 min read
PocketBaseTanStack StartMarkdownPerformance
Editorial design / frontend

Making technical writing feel native to a portfolio

A blog should look like part of the site’s product language, not a bolted-on template that ignores the rest of the brand.

April 8, 20265 min read
DesignWritingFrontend