Modern "this that" design systems blend flexible components with intentional contrast to guide user attention and simplify complex interfaces. These frameworks rely on clear visual hierarchies, responsive spacing, and consistent patterns so products remain usable across devices and brands.
Below you will find a structured overview of core concepts, keyword-driven deep dives, and practical recommendations to apply "this that" styling effectively in real projects.
| Aspect | Definition | Visual Cue | Best Use Case |
|---|---|---|---|
| Primary "This" | The dominant element users focus on first | Strong color, larger size, shadow | Key actions, primary content |
| Secondary "That" | Supporting elements that complement the primary | Muted color, smaller size, outline | Secondary actions, contextual info |
| Interactive States | Changes on hover, focus, active, disabled | Opacity, scale, border shift | Guiding expected user flows |
| Responsive Behavior | How "this that" layout adapts across breakpoints | Stacking, spacing, reflow | Mobile-first and desktop layouts |
Establishing Visual Hierarchy with This That Styling
Effective "this that" styling starts with clear visual hierarchy so users instantly recognize what is primary and what is secondary. Designers use size, weight, color saturation, and spacing to create contrast without adding noise.
By defining which element is "this" and which is "that", teams reduce cognitive load and make interfaces feel intentionally structured rather than arbitrarily decorated.
Component Patterns in This That Systems
Component patterns formalize how "this that" relationships repeat across an interface library. Buttons, cards, navigation items, and data rows each follow a core template that separates primary action from secondary context.
Documenting these patterns in a living system ensures consistency, simplifies onboarding, and allows teams to compose new UI faster while preserving coherent contrast.
Responsive Implementation Strategies
"This that" styling must adapt gracefully across screen sizes so contrast and importance remain clear on small viewports as on large displays. Responsive implementation strategies include breakpoint-specific scaling, touch-friendly sizing, and reordering to preserve hierarchy without sacrificing usability.
Design tokens for spacing, typography, and color opacity can shift between breakpoints to keep the primary element dominant and the secondary element accessible yet subtle.
Brand Expression and Theming
Brand expression thrives on "this that" styling by letting teams elevate signature colors and shapes to the primary tier while keeping supporting elements neutral. Theming allows light, dark, and high-contrast variations so the system remains inclusive without breaking the intended hierarchy.
Consistent theming rules ensure that "this" always feels bold and confident while "that" recedes gracefully, regardless of the brand palette in use.
Recommended Practices for This That Styling
- Define "this" and "that" roles in your design system tokens so teams reuse them consistently.
- Test contrast ratios and visual prominence with real users on different devices.
- Establish responsive rules that reflow "this" and "that" without reversing their importance.
- Use the component pattern catalog to apply the same logic across buttons, cards, and navigation.
- Document theming guidelines so "this" stays bold and "that" stays subdued across brand variations.
FAQ
Reader questions
How do I decide which element should be "this" versus "that" in a dashboard?
Prioritize the action or data most critical to the user's primary goal as "this", such as a call-to-action or key metric, while treating navigation, secondary stats, or helper text as "that". Evaluate by observing where users look first in usability tests and by mapping business objectives to interface prominence.
What are common pitfalls when applying "this that" styling to forms?
A frequent mistake is overemphasizing decorative elements as "this" while essential inputs and error states remain subdued, which harms completion rates. Reserve "this" for the primary submit action and critical feedback, and keep supporting hints, labels, and secondary buttons as "that" to reduce noise.
Can "this that" principles be applied to data-heavy interfaces like tables?
Yes, use "this" to highlight the currently selected row, primary action column, or sort indicator, while treating background rows, muted labels, and auxiliary actions as "that". Maintain readability by ensuring contrast ratios meet accessibility standards and avoid relying solely color to convey importance.
How should "this that" styling evolve when designing for dark mode?
In dark mode, preserve the hierarchy by shifting "this" elements to higher luminance or more saturated brand tones, while "that" elements should desaturate and reduce contrast against the dark background. Test visibility in both themes to confirm that primary actions remain prominent and secondary content does not distract.