Skip to content

Patterns in practice

These are real screens from Space Works Events, built on Space Works UX and run with demo data. Each pattern links back to its number in the Space Works UX spec. Select any image to open it at full size.

A Citron sidebar with the workspace switcher on top, a text-only nav with one filled active item, then “View public page ↗” and the account chip at the bottom. On a phone it folds into a top bar and sheet.

The dashboard answers “what needs me?” first: the callout links straight to the approvals and the draft.

Page header, callout and stats (P2, P4, P5)

Section titled “Page header, callout and stats (P2, P4, P5)”

One identity block per page: name, meta and at most one filled primary action. A contextual callout carries the next step, and stat cards show real numbers.

Detail header with a date tile, status chips, underline tabs and a readiness checklist where every gap links to its fix.

Lists with filter chips and bulk actions (P6, P8, P10)

Section titled “Lists with filter chips and bulk actions (P6, P8, P10)”

Filter chips carry their counts. Selecting rows turns on the bulk bar. Every status is a word in a pill, never colour alone.

Member IDs: All 10 · Waiting 2 · Approved 6 · Rejected 1 · Revoked 1, with a reason shown under a rejection.
Guests: the next step is inline in the row; rare actions sit in the row menu.

Dense data keeps the card chrome: a bordered card, sentence-case column labels and a hairline between rows.

Team members with roles, and the invite card on top.

Settings rows, live preview and sticky save (P15, P16)

Section titled “Settings rows, live preview and sticky save (P15, P16)”

Settings are labelled rows with helper text beside each field. Changes collect in a sticky Discard / Save bar, and the danger zone sits at the very end.

The public-page preview updates as you type. Nothing is saved until you choose Save changes.

Create forms stay short, mark optional fields inline, and check the web address as you type.

An empty workspace never just says “nothing here”. It names the next step, and the first-run checklist shows only one call to action at a time.

High-frequency work gets its own focused surface: the scanner, search, live progress and an offline callout. Reversible actions offer Undo in place instead of asking “Are you sure?”.

Auth split screen and centred task card (P22, P23)

Section titled “Auth split screen and centred task card (P22, P23)”

Sign-in is a split screen: the form on one side, one bold brand moment on the other. Single tasks, like resetting a password, get one centred card.

One header card with the person and their verification chips, then tabs, each a column of cards.

Public pages use the organisation’s identity and a sticky card with the one action that matters.

Things people show at a door are built for a phone first: large type, high contrast and a clear state.

A valid card shows only what is needed to confirm it.
Errors are calm and specific, and say what to try next.