Make Chromiq yours

Typography and colors

Oxanium 600/700 is the display default; standard Barlow 400/500/600 is the body/UI default. Both are bundled under SIL OFL 1.1. Enable the explicit Shopify-font override in Theme settings > Typography to choose another pair. Default cold white #F4F5FA, ink #16131D, silver #C6CAD4, pink #FF79C9 and blue #2545D8. The primary CTA uses white on blue; pink sections use dark text. Set contrasting text/background pairs together.

Campaign cover

Choose a portrait or rectangular photograph; the oval frame is CSS and no cutout is required. Adjust image alt text and focal point in the picker. A selected collection takes precedence over the fallback link. Use one concise CTA. Chrome heading is optional, with solid fallback and forced-colors support. It applies only to campaign type, never names or prices. Show original cover decorations controls the orbit, star and editable sticker, with at most three visible decorations. Clear the sticker to reduce them.

Capsules and product grid

Select up to three collections and optional image overrides, titles and captions. The capsules provide real collection links, not scarcity or timed-drop promises. Theme settings > Layout supports 2-4 desktop columns, 1-2 mobile columns and portrait/square card ratios. Preset photography is 3:4. Collection section settings retain products per page; product data controls actual sale/sold-out badges.

Product page

Main and Featured product support merchant blocks. Add Collapsible rows for material, care and sizing, using rich text or a Shopify page. Empty rows are hidden; there is no automated fit advice. Product names, prices, stock and variants are solid text. On mobile the contained gallery precedes the information card, options and buying controls. Decorative effects never replace purchasing content.

Other templates

Collection/search/cart, contact, content pages, blog/articles, password and 404 retain native foundation behavior with the Chromiq visual system. Compatible app blocks remain available. Store-specific integrations need verification with your own content.