Quest Board · the redesign · lane 4 of 8

At the table

Theme

Table mode is where Quest Board earns its keep: the GM’s shelf of cards during play, what the players see when something is shown to them, a screen the whole table can read, the recording, and the sweep at the end that decides what was worth keeping. 163 features across five surfaces — and TABLE-1 alone is 111 of them, the largest surface in the catalogue. The first draw drew the decided parts and left 76 out; the backfill (#696) draws the rest: every card’s own controls and shapes, Find and the preview beside the table, the canvas’s other states, and the recording panel’s.

Desktop-first for the GM, deliberately (D34). The desk is where a GM is meant to be. A phone gets a real reduced surface for when the laptop has died or is needed for something else — not a squashed board.

Same campaign. Session 14 is in progress: Dana is running it, four of five are here, and the bot has been recording for an hour and forty-two minutes.

Look

Found, settled, and open

Nothing open

D37 settles the one question this lane raised. The shelf is freeform, not look.html’s reflowing grid, and the board is a canvas that may be wider than the screen, with sideways scrolling an officially supported way to get more room. The default stays 1:1, so every card stays readable at a glance; “see the whole board” is an optional overview rather than a shrunken default.

Worth recording how it was reached: the question was what happens if a GM preps on a 4K monitor and plays on a 1080p one. The variable turned out to be CSS width, not resolution — a 4K monitor at 200% scaling is exactly as wide as a 1080p one, while a laptop at 125% is narrower than either — and positions were already screen-independent. What was missing was that the scrolling happened by accident, the whole page scrolled rather than the board, and nothing told the GM a card was off to the right.

Settled for the backfill

Decided while drawing

Answered on review, 2026-09-25

The build's own survey raised twelve questions (L1–L12); the owner accepted every recommendation, recorded as D111 to D122.

Answered on review, 2026-09-26

The coverage check

207 placements, none missing. 139 drawn (IS-439, Add a card's menu, joined them on review, 2026-09-25), 12 replaced by a decision, 15 behaviour with nothing to see, 26 belonging to other surfaces, and 15 deferred (six of them added on review, 2026-09-25: recording from anything but Discord, the shared screen, credits, safety and the Foundry map mark all wait on other work). Before the backfill: 76 missing and 18 half-drawn of 200.

What rendering caught in the backfill

  1. Start recording stayed clickable while another session was recording — the first draw’s own fault, found by the audit.
  2. The Table bar wrapped every button onto two lines once it gained Players’ view and the keys.
  3. Card controls squeezed titles to three lines, and the taller NPC card overlapped the card below it.
  4. Whole Table frames in half-width stills pushed the shelf’s own states below the fold and ran the bar off the edge. Those states are drawn as the shelf now.
  5. “Scrolled to the middle” counted two cards off the right while both were on screen.
  6. A panel that had lost the connection said the recording “carries on”, which it cannot know.
  7. An NPC from the wiki had the glance face, which only generated NPC cards get (TB-026).
  8. The shelf’s menu repeated “See the whole board”, already a button beside it.
  9. A sweep row said a card had no text, on a card whose text was right above it.

Settled before drawing

What rendering caught the first time

Six, plus one I caught while writing it.

  1. The phone bar said “recording” with a red icon and no word. The desktop bar says Recording; I dropped the word on the phone to save room. That is the exact fault the render check first caught in lane 2 — recording told from not-recording by colour alone, in the place it matters most — reintroduced two lanes later.
  2. The shared screen sized its type to the page, not to itself. Its font sizes used vw, so a TV drawn at a third of the page was still sized for all of it: the title wrapped, one screen grew taller than 16:9, and the lost-contact bar covered the last word. Now in container units, which is also what a real TV of any size needs.
  3. A lone shared-screen still stood 850 pixels tall, because a single item fills a whole grid row. The three states now sit side by side, which is the comparison anyone reviewing them wants anyway.
  4. A card footer broke mid-phrase — “Handout · On / the table”, with “· carried” stranded on a line of its own.
  5. “Keep in the wiki” wrapped onto two lines in the phone sweep.
  6. One speaker’s time read “41m of speech” and the other three just “28m”.

And one caught before it rendered: the phone surface said “the board, scenes and card layout are on the desktop”. That is precisely what D20 forbids — a pointer elsewhere on a surface people open constantly, and D20 names Table mode outright.

And two more, drawing D37. In the light theme the sweep and the new canvas still took the page’s accent rather than Table mode’s, so “review it” and the on-the-table labels were dark blue on navy — a fault that shipped in this lane’s first version and only showed once a new still used the same wrapper. And this section’s headings sat on top of each other, in lane 3 as well.

What this lane leaves for later

The scene model itself (#689) is a design record, not a build: a migration, a scenes table, and the Foundry pairing, which depends on #5 and #6 connecting to Foundry at all. Building a scene in prep belongs to PREP-1, which is lane 5.