← Back to the screen

Design system portfolio

Design record: Northwind Field

The four direction lines behind this page, the generator command that produced its tokens, and the pairs it was measured against.

Brief 11, Salesforce Lightning Design System

The screen. SA-04417, the gearbox oil-change program Northwind Field runs for Ridgeline Wind Cooperative. One record, in SLDS's record shape: highlights panel, path, tabbed detail, related lists in the right rail.

Direction

Archetype. Shell, in the SLDS record-page shape. Under 1024px the rail's three lists become the Related tab, so exactly one of the two is ever on screen.

Data stance. Prose-first. The activity timeline is the record; the fields are what the sentences refer to.

Density. SLDS default (Comfy). 13px body, the 4px spacing scale, 32px controls.

The bold thing. The path is a state machine with four states, not three. Each stage carries its guidance for success and its exit condition. One stage is held by something outside the path (an approval that expires before a board sits) and it carries the warning colour and names the date and the record holding it up. The stage behind it is grey and says which stage it waits on, so the warning colour means one problem rather than two.

Generators

slds_tokens.py --theme hooks
slds_tokens.py --theme primitive --grep duration --format css
slds_tokens.py --contrast

tokens.css is the first command's output and nobody edits it. The hooks set carries no duration, which is why the second command exists: motion-tokens.css holds the six SLDS duration primitives and nothing else.

Pointer states on the path

All six stages answer a pointer, because all six are real targets: clicking one changes the guidance panel, and a completed one moves the record back to it. The refusal lives one level down, on the panel's action button, which carries a real disabled treatment and its reasons. A held stage that read as unhoverable would suppress the affordance on the two stages an account manager most wants to open.

Each state hovers and presses two steps down its own ramp, so a pointer never paints a stage the colour of a state it is not in:

StateRestHoverPress
Completebrand-base-95brand-base-90brand-base-80
Currentbrand-base-50brand-base-40brand-base-30
Blockedwarning-base-90warning-base-80warning-base-70, ink to warning-base-20
Waiting, not startedneutral-base-95neutral-base-90neutral-base-80

Two of these were self-assignments before state-probe.mjs found them: a completed stage's rest colour was the generic hover colour, and the blocked rule repainted the stage its own background to stop the generic hover reaching it. Both are the same defect, a control that looks inert to a pointer, and the completed stage is the one this page made clickable.

The second state

A record you can only partly see. Preview as in the global header switches the page between the agreement's owner and a field technician, and the technician's render is the honest one. The annual value and the margin read Not available to your role. Two of the three contacts stay hidden. A no-access message takes the place of the files list and names who can share it. Edit, Send for signature and Add on the contacts list go disabled together under one sentence naming whose they are, and the path's stage control goes disabled too, giving both its reasons where a stage is refused for two. Field-level security and sharing are the states an SLDS screen has to render, and the platform's own guidance warns against showing an action the running user cannot perform.

Measured

Deviations

Light only. The hooks set carries one set of values, and inside Lightning Experience the theme belongs to the org rather than to a component.

Easing. SLDS tokenizes durations and not easings, so transitions run the ease-in-out keyword over the generated duration tokens.

Type and spacing in rem. Colour, radius, shadow, font family, and duration all come from the token files as var(). Type and spacing follow SLDS's published modular and 4px scales, the values its slds-text-* and slds-p-* utilities carry, since no SLDS stylesheet ships with this page.

A larger record name. font-scale-4 (25.6px) runs larger than a Lightning Experience page header and gives the page one focal size.

<button> rather than <lightning-button>. lwc_lint.py reports 16 native-control warnings and every one of them is right about an LWC template. Off the platform no base-component runtime exists, and a custom element with no definition takes neither focus nor a keypress, so the native control is the accessible answer here.

APCA. Body text at 13px is SLDS's density and clears WCAG 2.2 AA at 17.76:1. APCA asks for 15px at weight 400 and disagrees.

Uplift round (2026-10-29)

Archetype unchanged (shell, SLDS record page). What changed and why:

Round two: the first screen (2026-10-29)

A critic scored the first fold 5.5/10: small type throughout, a path in a thin band, three columns of 12px text competing. The fold now has one figure, one band and one problem.

Round nine: the world-class pass (2026-11-09)

Archetype unchanged. The page was scored against the platform's own record page, walked as the account manager and as the field technician, and driven at 320 to 1920 in 10px steps, on an emulated phone at 360 and 390, at 200% zoom and at 1920. What changed and why:

Left, with reasons: the page stays light only (the hooks set emits one value set, and the theme belongs to the org). The approval is dated Sunday Jul 19, which the arithmetic fixes (Jul 19 plus 90 days is Oct 17, 26 days before Nov 12); it reads as a finance date, not a working day.

Round ten: the harsh second read (2026-11-09)

Archetype unchanged. A cold reader scored the page 31/40 against Salesforce's own record page (path, highlights panel, activity timeline, toasts, modals), not the 34 of round nine. Driven afterwards at 1440, 1920, and on an emulated phone (touch, 3x) at 390 and 360, with the dark scheme checked (the page stays light, so it renders identically). What changed:

Inventions, named: (1) Recall from signature, and what it writes to the timeline. (2) Countersigned cannot be completed before the agreement is sent. (3) The line "Priya already has this as a task", which restates the existing overdue task. (4) A new task's due date is the date typed, with no time.

Left: the phone action bar's Complete stage is disabled without a reason of its own when the current stage is held (the reason is in the card above it, severity 1). The Account name has no record to open, so it is plain text and not a lookup. Edit still covers only two fields.

Round eleven (2026-11-10)

Archetype unchanged. A cold reader scored the page 33/40 and found two defects in the board-date field, both reproduced as reported before editing.

Inventions, named: (1) the title "Countersigned is not held on this date" and the fix "Nothing to extend" for a typed date that clears the hold; both only restate the rule the page already uses (held when the board sits after the approval lapses). (2) The calendar sentence appended to the board field error. (3) Blur validation on date fields; the form-level summary still appears only on Mark complete.

Left: the path stage ("No approval for 26 days") still follows the saved date, not the draft, as in round ten. The phone bar still says Complete stage where the form says Mark Legal review complete.

Round thirteen (2026-11-10)

Archetype unchanged. A cold reader scored the page 34/40 and would ship it, with one change: the phone action bar called one act "Complete stage" where the guide button calls it "Mark Legal review complete". Reproduced as reported at 390 and 360 (touch, 3x): bar "Complete stage", guide button "Mark Legal review complete".

Inventions, named: none beyond the label. When every stage is done the bar button (disabled) names the last stage, "Mark In service complete", as the guide's own disabled buttons name theirs.

Round fifteen (2026-11-10)

Archetype unchanged. A cold reader (r14) would ship it with one note: while a what-if board date is typed, the path still says "Held, No approval for 26 days" and the block says "Countersigned is not held on this date". Reproduced as reported at 1440: type 10/10/2026 in "Cooperative board meets", Tab. The same disagreement held for a later date (11/20/2026: path 26 days, block 34 days).

Inventions, named: (1) the chip text "What-if, not saved" and its sentence; (2) a dashed edge for a not-yet-real state, borrowed from the page's own disabled-button treatment; (3) dismissing the toast on a role switch. SLDS has no preview marker on the path, so the path was left as the saved state and the block carries the label.

Round seventeen (2026-11-10)

Archetype unchanged. A cold reader (r16, 37/40) would ship it with one note: on a phone the first screen is the highlights panel and the path is six unnamed icons, so the held-stage story starts a long scroll down. Reproduced at 390x844 and 360x780 (touch, 3x): the only words about the hold were "Stage 4 of 6, Countersigned is held", at page y 636 (390) and 654 (360), with no day count; the block that explains it began below the action bar's edge.

Inventions, named: (1) the words "Saved date:" and "on the saved date"; (2) the phone held line and its wording, which restate the desktop stage text; (3) hiding the renewal line and the dots on a phone only. Hero size on a phone is one scale step down from round two.

Left: the toast still covers hold-block text while it lasts (sev 1 c); it is bottom centre by round fifteen and has Undo and a close button.

Round nineteen (2026-11-10)

Archetype unchanged. A cold reader (r18, 34/40, ship: no) found that a phone user cannot send the agreement for signature. Reproduced as reported at 390 and 360 (touch, 3x): after Legal review closes, "Mark Countersigned complete" is disabled with "Send the agreement for signature first. The button is at the top of the record.", and #act-sign is 0 x 0 inside .hl__acts, which is display: none under 768px. The bar held Edit and Log a visit only.

Inventions, named: (1) the label "More" and moving Log a visit behind it on a phone only; (2) the two reason sentences.

The toast (sev 1, second pass)

Defect, measured at 1440 and 390: the bottom-centre toast covered the disabled stage button and its reason (desktop) and the stage guidance (phone) for as long as it showed.

One rule: the toast covers none of the text the act just changed. Where it sits: top centre under the global header on 768px and up (SLDS's place; top: 3.75rem, clear of the 57px header at scroll 0), and directly above the action bar on a phone (as in round fifteen). This puts the toast at the top on desktop again; round fifteen had moved it to the bottom for covering "Service agreements" and the path, and the rule below is what makes the top safe. reveal() runs after every act that raises a toast: it takes the elements the act changed, finds the band the toast (and on a phone the bar) leaves free, and scrolls the page only if they are not already inside it (centred in the band, or top-aligned if taller than it). What each act changed: a stage move or move back, the stage's eyebrow and guidance, plus the stage button and its reason on desktop or the path head on a phone; an activity entry (call, visit, task, email, send, recall), that timeline entry, which land() now places with the same function instead of its own 72 and 240 pixel margins; an edit save, the two Details values; an added contact, its new row in whichever list is showing. Focus after a stage move or an edit save no longer scrolls on its own (preventScroll), so reveal() is the only scroll.

Measured after each act (stage Legal review, send, stage Countersigned, move back, edit save, call, task, email, visit, contact) at 1440, 1920, 390 and 360: toast rect against every text rect of the changed elements, and whether those rects lie inside the viewport above the bar. Result: zero covered and zero off-screen in all 40 cases; no page errors, no horizontal overflow. As a negative control the same script with the toast forced to the middle of the screen reports covered text on the stage acts. The toast does still cover other text, such as the highlights panel at the top of the page on desktop; that is text the act did not change.

Inventions, named: (1) top: 3.75rem as the offset under the header; (2) scrolling the page after an act, where before only a new timeline entry was scrolled to.