Skip to content
Cat Thanh

Static-first notes on systems, frontend craft, and patient shipping.

Post

Field Guide to Component Boundaries

A practical way to split templates, styling, and tiny enhancements before the codebase turns mushy.

Mar 10, 2026 · 1 min read
frontend web-components maintainability

Good component boundaries are less about theory and more about whether someone else can safely edit one part of the page without surprising another.

For this site, the boundary rule is:

  1. content lives in Markdown
  2. structure lives in 11ty layouts and includes
  3. style lives in Tailwind utilities
  4. behavior stays in a single lightweight module unless a component truly needs more

That keeps the maintenance surface smaller and the mental model calmer.