global-toolbar-controls
Global Toolbar Controls
What Belongs Here
Global controls affect the entire product experience but are not the user's primary task. They are reached occasionally — once per session or less — and should not compete visually with primary navigation or content.
Typical global toolbar controls:
- Currency selector (e-commerce, financial tools)
- Language / locale switcher
- Region or market selector
- Unit system (metric / imperial)
- Theme toggle (light / dark)
- Accessibility preferences (font size, contrast)
These are distinct from user account settings (which live in a profile menu) and from contextual settings (which live adjacent to the feature they affect).
Where to Place Them
Header utility strip
A secondary row above or within the main header, right-aligned. Common on e-commerce and international sites.
[Logo] [EN | EUR | 🌍] [Account] [Cart]
────────────────────────────────────────────────────────────
[Main navigation]
Header right — compact
Inline with the main header, far right, using small typography and minimal visual weight.
[Logo] [Nav items ...] [EUR ▾] [EN ▾] [Account ▾]
Footer
For controls the user sets once and rarely revisits. Language and region selectors frequently appear in footers on large international sites (Airbnb, Apple). Appropriate when the control is truly infrequent.
Dedicated settings area
For more complex preference sets, a Settings page or panel is cleaner than cramming everything into the toolbar. The toolbar should link to it, not contain it.
Typography and Visual Treatment
Global toolbar controls are secondary UI — they should not draw the eye away from primary content.
- Font size: 13–14px — deliberately smaller than body text (14px maximum per the type scale)
- Colour: muted — use a secondary text colour (
--color-text-secondary), not the primary text colour - No bold — regular weight only
- Compact spacing — tighter padding than primary navigation items
- Separator — a
|or thin vertical rule between adjacent controls (language | currency) keeps them grouped without using full button chrome
.toolbar-control {
font-size: var(--text-sm); /* 13–14px */
color: var(--color-text-secondary);
font-weight: 400;
padding: 4px 8px;
}
Interaction Pattern
Global controls typically use a compact dropdown — clicking the label opens a small popover or select with the available options.
- Show the current value as the trigger label:
EUR ▾,EN ▾ - Use a flag icon + language code for locale, or currency symbol + code for currency
- Keep the option list short — if it exceeds ~20 items, add a search input inside the dropdown
- On selection, apply immediately and confirm with a brief status update (toast or inline update) if the change has a visible effect
Review Checklist
- Are global controls placed consistently in one location across all pages?
- Is the typography smaller and more muted than primary navigation?
- Does the control show the current value as its label?
- Is the dropdown or popover compact and keyboard-navigable?
- Are global controls separated from user account settings?
- On mobile, are global controls accessible without being prominent? (Often moved to a menu or footer on small screens)
More from dembrandt/dembrandt-skills
nielsen-usability-heuristics
UI design and review should apply Nielsen's 10 Usability Heuristics — the foundational principles for evaluating and improving usability. Use when auditing an interface, designing interaction flows, writing error messages, or reviewing any UI for usability issues.
45form-design
Forms have three layers of guidance: helper text below the input explains what to enter, placeholder shows the expected format, and validation confirms correctness. Real-time validation for complex inputs. Submit enables only when the form is valid. Use when designing or reviewing any form, input field, or data entry UI.
44color-mode-and-theme
Choose light, dark, or combined color mode deliberately based on brand tone and user context. Offer a theme selector only when user control genuinely matters — enterprise tools, data-heavy UIs, or extended-use applications. Use when defining the base color palette, designing a design system, or deciding whether to build dark mode support.
43user-flows-and-guided-paths
Related features and tasks — such as purchase flows, onboarding, or multi-step configuration — should be designed as natural, guided paths that feel coherent and fit the product hierarchy. Use wizards for complex sequential tasks. Use when designing flows, onboarding, checkout, setup sequences, or any multi-step user journey.
43generate-ui-from-brand
Pipeline skill — turns a URL or DESIGN.md into a concrete UI structure with decisions already made. Extracts live design tokens, normalizes them into a semantic system, applies UX principles, and outputs an actionable UI spec. Use when building UI for an existing brand from scratch, auditing a design system, or refactoring visual inconsistency.
42micro-interactions
Micro-interactions are small, purposeful animations and responses that reward the user and make the interface feel alive — an animated icon, a satisfying toggle, a subtle reveal. Borrowed from the natural world, they add delight without distraction. Use when designing interactive components, success states, toggles, loaders, or any moment worth celebrating.
42