Components, variables and CMS collections solve different kinds of repetition. The trick is choosing the right layer for each design decision.
Sample content for CMS, layout and interaction testing. This is not approved editorial copy.
Components, variables and CMS collections solve different kinds of repetition. The trick is choosing the right layer for each design decision.
Use components for repeated interface patterns
Navigation, cards, calls to action and shared content structures are good component candidates. Their value comes from a consistent structure with a controlled set of meaningful variations.
Use variables for shared design decisions
Colour, spacing, type and radius variables help teams change a system coherently. Name them by purpose so future editors understand where a token belongs rather than copying a visual value.
Use CMS content when editors own the variation
If the content changes independently and needs its own publishing lifecycle, it usually belongs in the CMS. Avoid turning ordinary component properties into a substitute content database.
A practical starting point
- Agree the outcome before choosing the tool or tactic.
- Keep the first version small enough to test with real users.
- Document what the team should measure and who owns the next decision.
Good website systems make useful work easier to repeat.
The strongest approach is rarely the most complicated one. Start with a clear structure, test it against real content, and improve it when evidence shows where the friction is.
