Site architecture
The technology behind this site
A compact public website can still show how I think about software: deliberately, with clear ownership, and with enough process to make future changes boring.
This website is small, but I treat it as serious software.
It is a public business-card site, a content platform, and a practical reference implementation for how I make technical decisions when the scope is intentionally modest.
The process comes first: clear specs, agent-assisted implementation, human review, automated checks, controlled deployment, and ongoing operation all matter more than any single framework choice.
Agent-driven development
The interesting part is not "AI writes code". The useful part is a disciplined software development workflow where an agent helps execute decisions that still need product sense, technical judgment, and review.
I use structured specs, implementation plans, focused tests, and tight verification loops so the work stays legible from idea to shipped change.
Current stack
The core stack is Next.js, React, TypeScript, Tailwind CSS, and Sanity CMS, with a workflow built around small, reviewable changes.
- Application
- Next.js 16 with the App Router and React 19.
- Interface
- TypeScript components styled with Tailwind CSS v4 and shared theme tokens.
- Content
- Structured content modeled through typed GROQ queries and generated content types.
- Workflow
- Codex/agent workflows with Git/GitHub history, review, and previews.
- Quality
- Linting, formatting, type checking, Vitest coverage, and release signals.
- Operation
- Preview deployments, production releases, and monitoring kept understandable.
Quality and operation
Lightweight discipline is easier to keep when it is part of the normal path, not a special occasion.
- Version control, checked locally before changes move forward.
- Automated linting, formatting, type checking, and tests.
- Changes are reviewed and deployed through a controlled workflow.
- Preview deployments, monitoring, and operational checks make production changes easier to trust.
A small working lab
I use this site to try new development tools, content workflows, AI-agent practices, deployment patterns, monitoring ideas, and operational discipline in a real environment. That makes it a useful place to talk about technology choices, development process, and the practical details behind delivery.