← Back to posts
processmeta

Starting the Studio Blog

This is the first post on the Studio Blog — a space I’m building alongside my design practice to think out loud, share what I’m learning, and keep a public reference for the work and systems I’m developing.

Why a blog?

Three reasons, roughly in order of importance:

1. A reference to share. I work across advertising campaigns, CPG packaging, websites, motion, and AI-native design workflows. A lot of that work lives in private repos, Figma files, or client deliverables. This blog gives me one link to drop into conversations — a way to say “here’s how I think” without forwarding a deck.

2. A skills lab. I built this site using Astro, React islands, BoldKit components, and shadcn/ui design tokens — deployed to Cloudflare Pages. Every post is an opportunity to test a new pattern, refine a system, or learn a tool that I could later use for client work.

3. Authority that compounds. A portfolio shows what you’ve made. A blog shows how you think. Over time, posts accumulate into something more valuable than any single project — a body of ideas that keeps working after you hit publish.

What to expect

I design and build across a wide range, so the content will reflect that:

  • AI-first design workflows — how I use tools like OpenAI image generation, Remotion, MagicPath, and HyperFrames as part of a real design process
  • Systems thinking — StudioOS, component libraries, design tokens, and how I organize creative work
  • Campaign and brand work — process notes, rationale, and what I learn from specific projects
  • Tooling and automation — Hermes profiles, cron jobs, Kanban workflows, and the infrastructure behind a modern design practice

Not every post will be deep. Some will be quick observations. Some will be full case studies. The goal is to keep writing.

Built with

This blog runs on:

  • Astro — content framework, static-first, Markdown/MDX
  • BoldKit — neubrutalism UI components on top of shadcn/ui
  • Tailwind CSS v4 — styling
  • Cloudflare Pages — deployment

The full source is managed from within StudioOS, my central design operations system.

Thanks for reading. First of many.