← Back to the screen

Design system portfolio

Design record: Rota

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

Brief #4, fluent-2. A ward team inside Teams. The night team hands Ward 7 to the day team at 07:00, and this is the screen both of them stand at while it happens.

The four direction lines

What the critique round changed

The inversion was asserted and not composed. h1 and .metric-value were both fontSizeHero700, so four 28px figures stood against one 28px heading while the primary column's own h2 sat at 16px: the tiles were the headline. The figure came down to fontSizeBase600, the thread's heading went up to fontSizeBase500, and below 640px, where the title itself drops to 24px, the figure drops again to 20px so the heading is the largest thing on the screen at every width. On a phone the four tiles had also stacked into 474px of numbers between the title and the first word anybody wrote; they are two columns there now and the thread starts on the first screen.

Five behaviours were wrong rather than missing. Sign off as read, the only control drawn as primary and the act the screen exists for, did nothing. A posted entry took its time from the reader's clock, so it landed at 02:21 under an entry timed 07:02 in a column whose whole meaning is the order. 14 entries since 19:00 never moved: not when the filter hid twelve of them, not when somebody posted a fifteenth. Posting under Escalations only left the new routine entry on screen with the filter still pressed. And the ward and category menus carry role="menu", which is a promise about the arrow keys that only Escape was keeping.

The second state

The entry that did not send. A day charge nurse types the one thing with a clock on it, a repeat sample the theatre slot depends on, and the post fails. It sits in the thread where she wrote it, marked as reaching nobody, with two ways out: send it again, or move it back to the box she wrote it in. Both are live on the page. The composer's empty-submit validation is live too.

Generator

fluent_theme.py --mode both

tokens.css is that output, unedited. The audit acted on:

fluent_theme.py --contrast --mode dark

which passes every required pair and reports colorNeutralStroke1 at 2.53:1 as a decorative divider. The page draws no hairline at all: the composer separates from the thread by receding one neutral layer instead. Every control boundary reads colorNeutralStrokeAccessible.

Measured contrast

Read out of the rendered page with getComputedStyle, and confirmed with contrast.py:

The lever spent against the neighbouring index

direction_check.py --compare put Rota and Carbon's Grid North at 0.83 against a 0.75 ceiling. The lever is elevation, which is the one structural language Carbon has no word for: it rules its regions and forbids shadows, while Fluent layers colorNeutralBackground1 through 6 and lifts what floats. So the thread surface lifts off the canvas on shadow2 and borderRadiusLarge, the four tiles stay flat on the canvas, and the composer recedes to colorNeutralBackground2 inside the lifted surface, which is what let the last decorative hairline go. The elevation now carries the bold thing: the primary column is the only region on the page that lifts. The pair reports 0.67, distinct, and Rota's highest similarity against any of the other eighteen pages is 0.59.

Deviations

The uplift round (2026-10-29)

What changed, in the order a visitor meets it:

Not done on purpose: no Mica or acrylic. Fluent puts Mica on a native window's base layer and acrylic on transient surfaces over content; a web page has no window base layer, and the menus are opaque. Generator command unchanged.

Round two: the first screen has one moment

The four equal tiles were the fold and nothing led. What a ward team opens Rota to learn is the one thing owed by a clock that is about to be missed, so that is now the screen's moment: 08:15 at fontSizeHero1000, "Repeat group and save, bed 17" at fontSizeHero800, on the status-danger layer, with a runway drawn to scale from 07:02 through the 08:15 lab cut-off to the 09:30 slot (73 of 148 minutes filled). Fluent spends emphasis through its type ramp and its status layer, not a shadow, so the thread stays the only region that lifts. Brand blue sits on one control, the send that fixes it, so Sign off as read is outline until the screen is signed. The moment reads the same state as the thread, the Escalations tile, the line down the morning and the rail: send the 07:02 entry and the surface turns to the success layer, escalations go from 3 to 4, and the figures still agree (1 h 13 min everywhere). The tiles keep every figure and sparkline at 20px, a level below. The title and h1 no longer compete: the heading is not the largest thing on the screen by design.

Round four

Round eight

Round nine: below the fold, driven states, the real phone

Found by driving every state, by a real-phone context (isMobile, hasTouch, scale 3, at 390 and 360), by a 200% pass at 720px and by a width sweep from 320 to 1920 in 10px steps. No horizontal overflow at any width. Heuristic total 29 before, 30 after (consistency 2 to 3); the moments behind every score under 3: no shortcuts on a screen used twelve-hourly (flexibility, 2), no help beyond the hint under the box (help, 2), and a sign-off that cannot be taken back (control, 3).

Round ten: the heuristics that sat below 3

Scored again from scratch before anything was touched, driving the ward handover at 1440, 390 and 360 (a real-phone context: isMobile, hasTouch, scale 3) in both schemes. Round nine's 30 and this round's opening 25 are two readings of the same page; this one is stricter on the moments, and the cut is where the screen asks a nurse to act with no way back.

Before, with the moment behind each score under 3:

What changed, and why:

Dialogs are the native element, so Tab, Escape and focus return are the browser's. On a phone they rise from the bottom edge like the box's own sheet. Every new surface has a reduced-motion path that shortens, exits stay under 250ms, and print hides all of it.

After: every heuristic is 3. Nothing is a 4. What keeps flexibility at 3 is that the thread filters on one thing, escalations, and cannot be narrowed by bed or by bay.

Not done on purpose: the toast is not a live region, because the page's one status line already announces each act and a second announcement would say it twice. Generator command unchanged.

Round eleven (2026-11-10)

Two defects from an independent score, both reproduced before any edit.

Inventions, each minimal: the words "Not in this view" and the status line above; a toast with no Undo leaves after six seconds instead of ten (the ten are the window to take a post or sign-off back, and the grace after the pointer leaves was already six). No patients, counts or ward facts were added.

Round thirteen (2026-11-10)

One defect from the round-twelve score, reproduced at 1440 light, 1920 dark, 390 dark and 360 light before any edit: the moment card out-ranked the thread the brief says leads. The direction line says "the words a nurse writes at 06:52 outrank every count on the screen"; the card set its time at Hero 1000 (68px) and its title at Hero 800 (32px) against a thread heading at Base 500 (20px) and a 28px page title, so the clock was the largest thing on the screen at every width (40px against a 24px title on the phones), and the card plus the tiles put the thread at y 729 at 1440 and y 1197 at 390.

Round two made the clock the screen's moment. This round keeps the clock as the card's lead and ends its claim on the whole screen. The ramp is now four distinct Fluent steps, each at semibold: page title Hero 800 (32), thread heading Hero 700 (28), card time Base 600 (24), card title Base 500 (20). On phones: title Base 600 (24), thread heading Base 600 (24), time Base 500 (20), card title Base 400 (16). Urgency is carried by what was always carrying it, not by size: the danger layer, the filled alert icon, "in 1 h 13 min" in the danger foreground, the runway and the one brand-blue send. Nothing moved in the DOM, so the focus order is unchanged; on a phone the runway label row is 40px, not 56px, which takes 16px off the card. Measured by computed size and position, and with hierarchy_probe.py driven headless: the largest type on the first screen is the page title, then the thread heading (visible from y 657 at 1440 and 1920, where it was y 729), then the time, and focal-competition is quiet at 1440 and 1920. The thread still starts below the tiles on a phone (y 1119 at 390), because four tiles with sparklines stand between; reordering them would break tab order, so they stay.

Invention: none. No words, figures or states were added; the sent state (card turns to the success layer, "no longer at risk") was driven at all four widths and still works.