Skip to content
Brand & UX guide
Patterns

Patterns

How components combine to answer a question: the pulse strip, the action band, the weekly timeline, the handoff, waiting states, and money.

#Pulse strip

A row of three or four metric tiles at the top of a page. Each tile is one number, its change against the prior week, and its last five weeks as a sparkline. It answers “how are we doing?” before anything else. The grid reflows to two columns on phones.

Pulse strip
Revenue
$18,420
↑ 12.4% vs prior
Orders
312
↑ 3.6% vs prior
Sessions
9,840
↓ 1.8% vs prior
Code
<div class="pulse">
  <div class="tile"><div class="label">Revenue</div><div class="tile-value num">$18,420</div><div class="tile-foot"><span class="delta delta-up">↑ 12.4% vs prior</span><svg class="spark" viewBox="0 0 88 28" role="img" aria-label="Revenue, recent weeks"><polygon class="spark-area" points="3,28 3,22 23,18 43,20 63,10 85,5 85,28"/><polyline class="spark-line" points="3,22 23,18 43,20 63,10 85,5"/><circle class="spark-dot" cx="85" cy="5" r="3"/></svg></div></div>
  <div class="tile"><div class="label">Orders</div><div class="tile-value num">312</div><div class="tile-foot"><span class="delta delta-up">↑ 3.6% vs prior</span></div></div>
  <div class="tile"><div class="label">Sessions</div><div class="tile-value num">9,840</div><div class="tile-foot"><span class="delta delta-down">↓ 1.8% vs prior</span></div></div>
</div>
  • Three or four tiles. More than four stops being a summary.
  • Same order on every page: revenue, orders, sessions, then the operational count.
  • If a prior week does not exist, leave the delta out. Do not show 0%.

#Action band placement

The action band sits directly under the pulse strip, before the summary. One per page. If there is no action, omit it on the store page and say No action recommended on the report.

Do

  • One action, one sentence, one reason
  • Amber when it needs attention, teal for good news

Don’t

  • List three actions in one band
  • Move the band below the timeline
  • Invent an action to fill the space

#Weekly timeline

Newest first. A dashed Next pack card on top sets expectations. The latest week gets the violet node and pill. Each card: a plain headline (the first sentence of the summary), then revenue with delta, orders, and sessions. See the component.

#Handoff flow

Whenever the owner leaves Weekwright, for payment or store approval, they move through the same four steps. Each has one job.

The four steps
1 · Settings: the button→ 2 · Handoff modal→ 3 · Their page→ 4 · Return confirmation
Code
<div class="steps" style="gap: var(--space-3)">
  <span class="step-pill">1 · Settings: the button</span><span class="arrow">→</span>
  <span class="step-pill">2 · Handoff modal</span><span class="arrow">→</span>
  <span class="step-pill">3 · Their page</span><span class="arrow">→</span>
  <span class="step-pill">4 · Return confirmation</span>
</div>
StepWhat it doesWords
1 · ButtonStarts the flow. Secondary unless the plan is not yet active.Connect your store, Manage billing, Continue to secure checkout
2 · ModalSays what will happen, reassures three ways, offers Cancel.“You’ll leave Weekwright briefly to…, then come back.”
3 · Their pageOutside our control. Do not name the vendor on our side of the handoff.—
4 · ReturnConfirms the result and points to the next step.“You’re all set.”

See the modal in Feedback and overlays and the return card in Page templates.

#Waiting, empty, failed

StateShowPill
Connected, no pack yetStatus panel: “Queued · first pack Monday”, expected dateWaiting for first report
GeneratingStatus line “Generating · almost ready”generating
ReadyPulse strip, action band, summary, timeline● Connected
FailedA plain sentence on what happened and what to doFailed
Loading“Loading stores…”, nothing more—
Never fake it

Waiting states stay honest: one line of status, no placeholder charts filled with sample numbers.

#Money and currency

  • Store money in minor units and format it for display. Whole amounts have no decimals: $18,420. Others have two: $59.50.
  • Never sum across currencies. Show each separately and say so where totals appear.
  • Money is a mono, tabular figure, always.
  • Prices shown to customers are the founding price and come from one place in the app. Do not retype them.

#Responsive behavior

  • Metric tiles reflow from four to two to one column, by content width.
  • The report’s three panels stack below 960px.
  • The sidebar becomes a top bar with a Menu button below 960px. There is still one navigation landmark.
  • Buttons never shrink below 40px tall. Give touch targets room.
Weekwright brand & UX guide v1.0.0 Components rendered from app @ bd6c1f4 · build d2e1ef8