Define your brand once: how gallery software should reuse your look everywhere

Most galleries do not lack taste. They lack a system that carries taste forward.

You pick a serif for exhibition titles. You settle on an accent for inquiry buttons. You upload the mark that appears on fair invitations. Then someone opens Mailchimp and picks a slightly different blue. Someone else exports a catalogue PDF with last year's footer. Checkout on your site uses Stripe's default chrome because nobody remembered to match the button color. The work is not bad. The fragmentation is.

Professional gallery operations need brand primitives: a small set of identity decisions defined once and inherited by every public surface. Not a theme you tweak per page. Not HTML you paste into five tools. One workspace record that says how you look—and software that respects it.

What counts as a brand primitive

Think in layers, not layouts.

• Colors. Accent (buttons, links, highlights), primary text, and muted secondary text. Enough to read clearly on white paper and on screen without a designer in the loop every send.
• Typography. A display or header face for titles and a body face for captions, invoices, and long-form copy. Loaded once; applied wherever branded text renders.
• Logo. The primary mark for headers, checkout, and letterhead—not re-uploaded per campaign with a different crop.
• Print page templates. Overlay layouts for catalogues, certificates of authenticity, checklists, and invoices: where the logo sits, where margins begin, how content flows on A4 or Letter.
• Email footer. Workspace contact, social handles, and legal lines appended to campaigns and previews automatically—not duplicated inside every template.

These are primitives because they combine into many outputs. Change the accent color once; inquiry buttons on the public site, Stripe Checkout, and transactional email buttons should all shift together.

Where primitives should flow (and usually do not)

Galleries touch collectors in more places than a homepage. A coherent brand system propagates to:

• Public website — header, navigation tone, typographic hierarchy, footer studio name
• Private viewing rooms and collector portals — the same trust signals as the main site, without a separate "room brand"
• Marketing and transactional email — campaign blocks plus the shared footer; logo URLs that render reliably in clients
• Checkout — Stripe sessions that inherit your button color and logo instead of generic payment chrome
• PDF exports — fair catalogues, consignor-facing documents, COAs, labels: header and footer from branding, body from structured inventory data
• Receipts and post-sale surfaces — the collector's last impression should match the first

When each channel maintains its own mini-brand, staff become accidental designers. The registrar fixes a typo in inventory; marketing fixes a different typo on the site; finance prints a statement with an old logo. Nobody is careless. The architecture asked them to repeat themselves.

Primitives are not a website theme

Website builders sold galleries on "pick a template and customize." That conflates two jobs: identity (how you look) and composition (what you show on which page). Identity should be global. Composition should pull from what you already know—works, exhibitions, artists, events—and let you curate visibility without rebuilding metadata.

On a platform built this way, Website Studio reads fonts from Branding when you have not overridden them locally. Campaign previews append the brand email footer you configured once. Export modals offer toggles for header and footer because those slots already exist—they are not blank HTML fields you must fill from memory.

That separation is the point. You are not managing "site settings" and "email settings" and "PDF settings." You are managing your practice, and the software projects it.

Inventory and brand share one graph

Brand primitives answer how you present. Your catalogue answers what you present. The strongest gallery systems treat both as outputs of the same workspace.

When a work sells, the public grid should update—not because someone unpublishes a CMS entry, but because sold state lives on the object record. When you send an exhibition campaign, artwork blocks should pull titles, images, and captions from the same fields the registrar maintains. When you export a booth checklist, dimensions should match the viewing room PDF from Tuesday.

We wrote separately about websites that stay current when inventory changes. Brand primitives are the other half of that story: consistent presentation of records that are already trustworthy.

What to configure before your first public send

You do not need a brand agency to benefit from primitives. A practical first pass:

1. Set accent, text, and muted colors to values you already use on printed invitations or fair cards.
2. Choose header and body fonts—or upload faces you license—once in Branding.
3. Upload the logo you would put on a letterhead PDF.
4. Save a default page template for exports if you print catalogues or COAs regularly.
5. Complete workspace contact and social links so the email footer renders on the next campaign preview.

Then publish one page on Website Studio, preview one campaign, and export one catalogue PDF. If all three match without manual color picking, your primitives are doing their job.

The bottom line

Galleries should not re-decide identity every time they email a list, open a viewing room, or invoice a sale. Define brand primitives once—colors, type, logo, print shell, email footer—and expect every customer-facing surface to inherit them.

That is not a cosmetic convenience. It is how small teams look like institutions: one catalogue, one voice, one graph. Art.industries keeps Branding at the center of the public site, campaigns, checkout, exports, and portals so you spend time on curation and relationships—not on chasing hex codes across tools.