Why constrained components work

Each component solves a recognizable communication problem and owns its responsive behavior.

  • Reviewable

    The complete page contract remains ordinary, readable YAML.

  • Deterministic

    A valid plan compiles without another round of visual inference.

  • Responsive

    Components choose sensible stacking and wrapping behavior.

  • Theme-aware

    Semantic tokens preserve each theme's personality.

- type: feature-grid
  heading: Why constrained components work
  intro: Each component solves a recognizable communication problem.
  items:
    - { title: Reviewable, text: The page contract remains ordinary YAML. }
    - { title: Deterministic, text: Valid plans compile without visual inference. }
    - { title: Responsive, text: Components own their stacking behavior. }
    - { title: Theme-aware, text: Semantic tokens preserve theme personality. }

Deliberate limits

Features or facts
2-6
Enough range for a useful group without an endless wall.
Actions
1-2
A primary step and, when needed, one alternative.
Column controls
0
Responsive layout remains component-owned.
- type: key-facts
  heading: Deliberate limits
  items:
    - { value: "2-6", label: Features or facts }
    - { value: "1-2", label: Actions }
    - { value: "0", label: Column controls }
DNS query output displayed in a terminal
Verify the system from the command line.
A smiling person wearing a retired cap
Make the content feel human.
A tabby cat resting on a rug
Informational sites can still have personality.

The foundational gallery component remains useful when a page needs a straightforward collection of captioned images.