Interaction model and microcopy
1.31 Interaction model summary
Section titled “1.31 Interaction model summary”| Concern | Space Works rule |
|---|---|
| Primary action | One per page header, one per sticky card, one per callout. Never points at the current screen. |
| Secondary | Outline pill beside the primary; everything else is a text link or a row menu. |
| Where counts live | Stat cards (overview numbers), tab labels (queue sizes), row right slots (“5 / 120”), header meta, the kiosk header. Never in the sidebar on the reference boards (SpaceWorks keeps its unread count there, see §2). |
| Progressive disclosure | Sub-nav only under the active parent; accordions for reference; the camera off until “Start scanning”; the live preview beside the create form; optional fields labelled rather than hidden. |
| Inline vs menu | The next step is inline (pill or link in the row); rare or destructive actions go in “⋯” / “—” menus; destructive-irreversible actions go in the danger zone. |
| Navigation | Back link on detail pages; breadcrumb only on public sub-pages; tabs are URLs. |
| Feedback | Inline status (“✓ Available”, “Unused”, “Verified”), progress bars, an Undo in place; the result card in kiosk mode. |
| States | Dashed empty cards that point at a visible control; disabled = grey fill; zero shown as “0”. |
1.32 Microcopy style
Section titled “1.32 Microcopy style”Content contract (1A-X01): apply Voice and content for validation, failure/recovery, pending/offline states, localisation and audited actions. The examples below remain reference copy. CR-CONTENT-01 preserves the no-Undo boundary for evidence, handovers and payments.
- Sentence case everywhere, including buttons and tabs (“Page & programme”, “Save changes”). Caps only in 11–12 px eyebrows.
- Headlines may end with a full stop when they are statements (“Welcome back.”, “Free events. Your community’s data stays yours.”). Task titles do not (“Set a new password”).
- Consequence first, in the helper: “Changing it signs you out on every other device.”, “Removes every future date and its registrations.”, “This can’t be undone.” Helpers explain the effect of the field, not its format, except for upload constraints.
- Name the person and the object: “For priya@example.test.”, “Signed in as …”, “Kiran Reddy joined the waitlist · Demo Summit”.
- Numbers in context: “5 / 120 going”, “115 spots left”, “2 of 5 · 40%”, “3 upcoming 6 going 1 draft”, “In 9 days”, “2 min ago”, “Yesterday”.
- Separators: “ · “ for meta, “—” (em dash) inside CTAs (“Register — it’s free”), “→” for internal links, “↗” for anything that opens a new page or site, “…” on buttons that open a confirmation.
- Reassurance at the risk point: “It only holds a private ticket link.”, “Used only to match your registration…”, “Volunteers… can only check people in — no guest lists or exports.”
- Warm but terse: “You’re in, Meera!”, “It’s just you so far.”, “Running late?”, “Not you? Use another account”.
- These match the SpaceWorks brand voice in PLAN §1 (“No parts added yet. Add your first item.”, “Couldn’t save. Try again.”).
Part of Space Works UX spec, published from docs/ux-spec.md. Edit it there.