Skip to main content

Build note

Why public copy lives in the CMS

A build note on keeping marketing strings out of React and making launch gates enforceable.

June 5, 2026 · 1 min readAbout the author

Shipping marketing copy inside React components is fast early and expensive later.

Every headline tweak becomes a deploy. Every empty-state sentence hides in a PR diff. Every "we'll fix copy in admin later" note becomes a launch blocker.

Why CMS-first won

Lebear treats public UI as a read-only consumer of stored content:

  1. Site settings own hero, section titles, and about/contact copy.
  2. Tools and notes own their own cards and detail pages.
  3. Scripts like content:check enforce honest published inventory.

That constraint sounds strict. It is — and it keeps the brand credible while the tool catalog grows.

What this enables next

With copy out of components, enrichment work (detail pages, RSS, JSON-LD) composes on stable loaders instead of another sweep for hardcoded strings.

The site becomes a workshop door that can stay open while tools inside mature.

Related tools

← All notes