Back to blog

Blocks vs Components: What Survives a Rebrand

May 28, 2026ShipAny TeamShipAny Team

The core architectural split in ShipAny TanStack — disposable blocks read English message strings and wire content, durable components render anything you feed them.

Every template promises "easy customization," then makes you grep through twelve files to change a headline. ShipAny TanStack avoids that with one rule:

A file that reads message strings is a block. A file that takes all content via props is a component.

Blocks are disposable

Blocks live in src/blocks/ and are zero-config page sections — <Hero />, <Pricing />, <Footer />. Each one reads English messages, builds a content config, and passes it to a component. They're the demo material: when you start a real project, you delete them and write your own.

// src/blocks/header.tsx — a block: reads messages, wires a component
import { m } from '@/paraglide/messages.js';

export function Header() {
  const navLinks = [{ href: '/#features', label: m['landing.nav.features']() }];
  return <SiteHeader navLinks={navLinks} />;
}

Components are durable

Components live in src/components/ and never read message strings. SiteHeader, PricingTable, AppSidebar — all content arrives via props. They don't know your app's name, your copy, or your message keys. That's exactly why they survive every rebrand.

Why the split matters

When you rebrand or start a new project from the template:

  1. Keep src/components/* — the chassis.
  2. Rewrite src/blocks/* — the content wiring.
  3. Rewrite the English message JSON file that feeds the blocks.

The page files themselves stay tiny — page.tsx is pure composition, a stack of blocks. Changing your entire landing page touches blocks and JSON, never the primitives. The split is not cosmetic; it's what makes customization a rewrite of intent instead of a fight with someone else's design decisions.