Publishing · Components
Components
The WDS component library, organised on the Object Framework. A name is a path through the catalogue — Family → Bucket → Group → Variant — and the component's id derives from that path.
Family→
Bucket→
Group→
Variant
the content type·the role it plays·variants on the bucket's one axis·the built component
Events→
Cards→
Foreseeable (4C)→
Essentials + Media + Speakers
id derives →event-card-4c-essentials-media-speakers
01
Families
Benefits
To design
Channels
To design
Events
The components that present an event — Cards, Listings, Heros, Banners, Backchannel.
In use · building outEvent Series
To design
Photos
Stub
Speakers
Stub
Sponsors
Stub
Statistics
To design
Themes
To design
Video Players
Default Player · Live Player · Session Replayer, framed as Side Panel · Compact · Theatre · External Embed · Reader.
3 concepts · 5 variants
How the library grows
- Each family page is the contract the dev team builds from — and the map of what still needs creating in Sketch.
- Modelled on the Object Framework — the Section / Block / Component / Element tiers and the naming convention above.
- New families slot in here as they're defined; new objects are added within a family's buckets.
Component Library
The home of the WDS component families. Each family is a concept × variant matrix; building them out defines the design work and keeps the catalogue and the build in step.
The home of the WDS component families. Each family is a concept × variant matrix; building them out defines the design work and keeps the catalogue and the build in step.