Theming
Customize your storefront's colors, spacing, typography, and branding by editing design tokens in a single CSS file. Every design change resolves to Tailwind CSS utility classes at build time, so your components use consistent tokens across the entire application. Theming changes only how the application looks. The Design System page explains how the Figma design system maps to these tokens. The product and variant attributes your mappers read are in Attribute Keys.
How theming works
The Storefront Application V3 uses Tailwind CSS v4 with design tokens defined in src/client/design-tokens.css. This file contains @theme blocks where all customizable values live: colors, spacing, font sizes, border radius, shadows, and more. Tailwind regenerates every utility that depends on a token you change.
Edit colors
Colors are grouped by purpose: brand accents, status indicators, and semantic colors for states such as disabled. To customize your brand colors, open src/client/design-tokens.css and locate the COLORS — Accent comment header. See Tailwind's customizing colors guide for how a --color-* token becomes a utility class.
Update the hex values to your brand colors. The new colors are immediately available in all templates via Tailwind utilities: text-primary, bg-accent, border-secondary, and so on.
The --color-primary color applies to body text and primary UI elements. --color-secondary appears in supporting text and muted UI. --color-accent highlights interactive elements. --color-promotion and --color-campaign are reserved for promotional badges and campaign messaging. Functional colors (--color-status-success, --color-status-alert, --color-product-sale) signal system state and are used for status badges.
Edit spacing and sizing
Spacing tokens scale from --spacing-0_5 (0.125rem) up to --spacing-192 (48rem) in a block-based scale. Tailwind's theme variable reference lists the --spacing-* namespace alongside every other theme namespace. Modal widths are defined separately: --width-modal-sm, --width-modal-md, --width-modal-lg. To adjust spacing or modal sizes, edit the SPACING & SIZING section in design-tokens.css, identified by its own comment header.
Changes apply to padding, margins, gaps, and width utilities throughout the application.
Edit typography
Typography tokens include font family, sizes, weights, and line heights. The font family is set in --font-sans, which defaults to Inter Variable, following Tailwind's font family theme variables. Font sizes range from --text-sm (0.75rem) to --text-3xl (1.75rem), each paired with a matching --line-height value, per Tailwind's font size documentation. Font weights do not live in design-tokens.css. They are Tailwind's own --font-weight-* theme variables, such as --font-weight-normal (400), --font-weight-semibold (600), and --font-weight-bold (700), and the file does not reset them. To change one, set it in an @theme block of that file like any other token.
If you use a different font, update --font-sans to your font name. The application uses local self-hosted Inter by default via an @fontsource-variable/inter import near the top of src/client/index.css. To use a different font, replace that import with your font provider.
Typography in templates uses the Type Hierarchy utilities, which combine tokens into semantic roles: heading-page for the main page title, heading-section-1 for major headings, body-default for body copy. See the @utility blocks in src/client/index.css for the full set and when to use each utility. Storybook shows the Type Hierarchy and all base UI components in action. Run pnpm run storybook to explore. When a design change needs a new utility class rather than a new token value, Tailwind's adding custom styles guide covers the @utility directive.
Replace the logo
SFLogoLink renders your logo in the header and imports it from src/client/assets/icons/logo/signet.svg. To replace it, overwrite this file with your own SVG.
The component renders the icon at size-7, a Tailwind utility, so your SVG's own viewBox controls its internal proportions while the component controls its rendered size. Set fill="currentColor" in your SVG so the logo's color follows the surrounding text color rather than a hardcoded value.
Using a PNG or other image-based logo
vite-svg-loader only handles .svg files. A PNG, JPEG, or WebP file doesn't go through that
loader. Vite imports it as a plain URL string instead.
To use an image-based logo, change SFLogoLink to import the file as a URL and render it in an
<img> tag instead of a component tag:
The aria-label on the link gives it an accessible name, so the image itself stays decorative with an empty alt. The original component also switches the label and sets aria-disabled while the user is on the homepage. Keep that logic from the original file if you want that behavior.
An image-based logo renders exactly as saved and cannot inherit color from currentColor like an SVG with fill="currentColor" can. If your logo needs to change color in different contexts (light and dark headers, for example), an SVG is the more flexible choice.
Customize border radius and shadows
Border radius tokens control rounded corners on buttons, cards, modals, and form inputs. design-tokens.css declares only --radius-full (9999px). The other values, from --radius-sm (0.25rem) up, are Tailwind's default --radius-* scale, and you override one by declaring the same name in the @theme block. Shadows are predefined for specific contexts: --shadow-input for form elements, --shadow-hover for hover states, --shadow-overlay for modals and popovers.
Edit these values to match your design system. Changes apply to all rounded-* and shadow-* utilities throughout the application.
Customize icon SVGs
SVG icons in src/client/assets/icons/ are imported as Vue components via a Vite loader. To replace or add an icon, add or replace the .svg file, then import it with the component name you want:
Icons use currentColor for fill so they inherit color from surrounding text or explicit Tailwind color utilities: class="text-accent" on the icon tag applies the accent color.