Brand Pack · v2

Brand Packs

The machine-readable categorised dataset of brand data points and assets that every Wavecast rendering engine reads to produce on-brand output.

Components: Logos · Colours · Type · Artwork · Icons · Illustrations · Elements · TemplatesChannels: Web · Video · GraphicsScope: Account · Workspace · Event
01

What is a Brand Pack?

The model

It reads top-down — the Brand Pack feeds the Templates, and the Templates feed every output.

Brand PackThe machine-readable dataset and assets — the brand’s building blocks and the rules that govern them.
TemplatesBrand-locked compositions.
WebPages and emails.
VideoWatermarks, slates and overlays.
GraphicsSocial assets, slides and document visuals.
02

Brand Pack contents

8 components

Eight components make up a pack — seven brand primitives plus the assembled Templates layer. Each is its own categorised slice of the dataset.

On the components
  • Logos, Colours and Typography are live references; Artwork, Illustrations and Templates are forming.
  • Icons and Elements are surfaced from the Library — referenced here, not duplicated.
  • The model is the dataset, not a fixed list of files — new components can be added as the brand surface grows.
03

Who has a Brand Pack

Brand Packs can be stored at the Account, Workspace or Event level. They are available and portable — each level inherits the one above and overrides only what it needs.

AccountA client’s Brand Pack. The master for everything produced for that client.
WorkspaceA workspace within an account. A brand, division or programme — inherits the Account, overrides what it needs.
EventAn individual event’s Brand Pack. A conference, festival or campaign — inherits its Workspace where it needs its own identity.
Available & portableA Brand Pack is a dataset, not a fixed install — it can be exported, handed over, duplicated and applied across contexts. Re-skinning is a change to values, not a re-draw, so a pack travels cleanly between levels and between tools.
04

Examples

Placeholders

Real Wavecast packs — to be built out and dropped in here.

Client Brand Pack

Moody’s

Account-level pack.

Awaiting brand data
Client Brand Pack

ION Analytics

Account-level pack.

Awaiting brand data
Event Brand Pack

FIPP Congress

Event-level pack.

Awaiting brand data
05

What it is — and isn’t

Draft

A working articulation, to refine.

A Brand Pack is
  • A live dataset — structured, categorised and queryable by any engine.
  • The single source of truth for a brand’s assets and rules.
  • Versioned and re-skinnable — change a value, every output follows.
  • Portable and scoped — stored at Account, Workspace or Event level, and movable between them.
  • Rules included — clearspace, misuse, pairings, tone — not only files.
A Brand Pack is not
  • A static PDF or slide deck of guidelines.
  • A DAM — a folder of files someone has to hunt through.
  • A manual lookup or copy-paste exercise, asset by asset.
  • Locked to one design tool or one output format.
  • A creative brief — it governs the brand, not campaign messaging.
The data model
  • Data first: the Brand Pack is a dataset. The Notion registries (Colour, Typography…) are its canonical, queryable form; this site mirrors them.
  • Captured, not only sourced: designed templates are saved back into the pack, so it holds both the primitives and the compositions assembled from them.
  • One lever: re-skinning a client or event is a change to values, not a re-draw — every engine’s output follows automatically.
Wavecast Brand Pack
The machine-readable brand — a categorised dataset of assets, templates, conventions and rules that replaces static PDF guidelines and the DAM. Constituent values mirror the Notion registries; not edited here.