[UX] Full mockups with sample data — 3-5 directions for comparison #363
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found in the August 2026 session lifecycle review (#319). Follows the wireframe exploration.
What
From the preferred wireframe concepts, produce 3-5 full mockups at high fidelity, populated with realistic sample data — a campaign mid-arc, several sessions in various states, a real-length transcript and summary, a populated wiki with relationships, pending lore proposals, a live recording in progress.
Sample data is not decoration here. Most of the review's findings only become visible with real content: a dropdown of sessions all reading "Untitled session", a wiki article squeezed to ~39 px of prose beside a fixed sidebar, a proposals queue that renders differently depending on whether it is empty. A mockup with three tidy placeholder rows hides exactly the problems this exercise exists to solve.
The intent is explicitly comparison and mix-and-match — these are alternatives to choose between and recombine, not sequential drafts. Each should be complete enough to judge on its own.
Acceptance criteria
Round two of the design evaluation is built and live (2026-09-10). Recording it here since this issue had no trail yet.
Why round two. Round one's eight wireframe concepts (C0 to C7) mostly went unanswered: players found them overwhelming and too abstract to react to. Three sheets came back (one player, and the GM's player and GM sheets). The owner asked for two, or three if genuinely needed, full-scale mockups with extensive sample data, hosted under questboard-dev with no login, so players and a few outside people could evaluate something concrete.
Owner decisions, which change this issue's acceptance criteria:
What was built. Both mockups share one design system and one data file, so they can only differ in structure, never in polish. Five screens each in phone and desktop frames: home, the session that matters (this week / Plan), the table during a session (GM desktop, player phone), after the session with the event log from #568, and GM prep. Hosted on the feedback site as audience
round2(#590) with a deliberately short form; the landing page ishttps://questboard-dev.rhoving.com/feedback/mockups(the invitation link carries the key that lets answers save).Bug on first real use, fixed. The design links were root-relative, so behind the
/feedback/prefix they led to the Quest Board login page, and a trailing slash did the same through Starlette's slash redirect. Fixed and deployed, with a test that no page carries a root-relative link: see the PR opened alongside this comment.Against the acceptance criteria:
Next: collect the round-two responses, bring them back, and settle the final design (#364). Leaving this open until then.
Round two now includes the wiki (2026-09-11). Before sending round two out, the owner wanted the wiki designed and in front of players too. The design was worked out with them and recorded in #593, and both mockups now carry it (PR #594, live on dev).
Same link as before. Nothing has changed for anyone who already has it, and nobody had answered round two yet. Still open until the round-two responses are read.