The catwalk — mechanics

The fork in this look

There is no fork screen. The keynote walks; the fork is the floor's rule: walk ↓ (the standard route), ask (the mind) and tickets →; / or a printable key lands on ask.

The first question is one camera move: after the strobe frame, startViewTransition() carries it from the rule into the heading of section 01, under the runway; only the question moves (0.7 s, the walk-in ease), the root cross-fade off.

Walk is the page: the whole programme, static and indexable. Ask is one word beside it, free until focused (Turnstile waits for that), and only re-orders the page; the remembered door (decision 6) shrinks to the strobe and keys switches.

The standard route

No nav bar (tell 20): the walk verb, the rail, the lockup and tickets → navigate. Static pages share the letterbox: /lineup/<slug> is a one-walker runway (pull → carries the flash frame there by cross-document transition), /agenda/<session> that walk on the runway, and /agenda#day-2 deep links. The agenda is the numerals band over four day columns (a band per day on the phone); the roster takes day columns too. Tickets are the door, registration staying on Eventbrite. Without JavaScript everything reads and ask submits GET /ask?q= to a server-side matcher, no model.

Asking the mind

Every turn uses the site surface, its page note naming the walk on the runway and the ids on screen, so "what's this one about?" means whoever is walking.

Thinking is light before a walker: one 70 ms strobe frame (at most one a second), the cycle holds, and the new section's 300 px band comes on empty. say streams into the hairline under the question; each component walks in from the band's far end as its JSON closes. At 8 s without words the state line says so; at 25 s the band goes dark. Older answers recede by the line's 0.8 step.

• Text: say in the hairline; faq adds its site-authored question at 32 px.
• Speakers: speaker_grid is the line re-ordered, up to twelve flash frames receding in walking order (the model picks the set, the programme the order); the 18 without a photo get a black frame holding the name, never initials (tell 26). speaker_card is a one-walker runway.
• Sessions: session_card puts the walk on the runway; several print as sheet rows.
• Agenda day: a running-order column; a track filter dims rows, never removes them.
• Venue: AUSTIN in the band, "venue announced soon", the hotel line.
• Tickets: the door for the phase on sale, $849 and $299 base, fee-inclusive $907.78 and $320.89 in mono; phases flip by date, never by the model.
• Partners: names by tier, never a logo wall (tell 25).
• Choices: not chips (tell 34) but an "ask next ·" mono line of up to four questions; links print as floor verbs.
• Sources: the closing mono footnote, with a renderer-owned sample-data clause.
• Fallbacks: not_in_snapshot shows the nearest real band, off_topic one line; errors keep mind.html's codes without // (tell 5); unavailable or a spent budget hands over to the matcher, labelled "matched by name, not by the mind".

The assistant in the chrome

• The composer as a rule: ask, a block caret and a hairline input on the floor rule, no box or button, riding above the phone keyboard (--kb).
• The edge-parked card: the hero's "next up", made persistent. An answer landing away from the reader parks at the bottom strip's right end as an opaque ticket (first walker's frame, "02 · 5 walkers", walk to it ↑); phones use the state line.
• The state line: the 56 px under the rule, a polite status region ("02 · asking · stop", "02 · 5 walkers, Tue–Wed"). Below the runway, standard.html's merge rules act in place: grids re-order the line, days reveal their column, sessions take the runway, venue and tickets walk to the door.

Data, performance and accessibility

The fixture holds what renders: 77 speakers, 50 sessions (Monday's 8 speaker-led ones are the rail), ticket phases, 39 partners, eight FAQ, placeholder throughout. Whova and WordPress must add runway lines and a lead walker per session (titles reach 121 characters), a flash frame with rights and consent per person (graded on upload by walkers/flash.py, reviewed: 2 of 17 needed tweaks), real tracks (all seven are invented), rooms, descriptions (3 of 50), retime-proof ids and a live Whova clock for May 3–6.

Motion is one transform at a time; reduced motion stops cycle, strobe, walk-ins and transitions. Single-key typing gets an off switch (WCAG 2.1.4); the rail is one tab stop; the h1 becomes the event, not the rotating title; the cycle pauses on focus (2.2.2). Red 12 px type on white is 3.8:1, so "now walking" grows to 32 px; dim grey goes from #5A5A5A (3.0:1) to #757575.

Build plan

Carries over: server.py whole; the fixture; mind.html's reader, reconcile(), summarize(), error codes and offline script (the matcher's seed); standard.html's merge-and-clear; the concept's fit(), paint(), strobe and clock. Changes: seven components become the brief's reconciled nine plus sources and coverage; WALKS derives from the fixture; the page note carries visible ids. New: a four-day runway engine, renderers, the ticket, transitions, the matcher, standard pages, the flash job. Effort: a four-day demo; four weeks of front end for one developer plus a week for the flash job, beside the shared backend.

Risks

• The look stands on portraits: 17 graded, 18 speakers without a photo, consent for every face.
• The rail keys walks by time, but Tuesday 13:30 holds two breakouts: key by id and share the band.
• "asked here" implies logged questions, and none are: use staff lines ordered by text-free topic counts, labelled "often asked", unless Zpryme approves moderated retention.
• Twelve walkers recede to a 26 px frame; past eight the queue is texture.