feat(frontend): participants shared answers - #287
Merged
Conversation
sabinem
changed the title
Every sentence on the page was 12px mono at the full width of the window — about 120 characters to a line, nearly twice the 68 the theme's own `.prose` caps at, in the face reserved for scanning rather than reading. The page used `text-xs` thirteen times and `.prose` not once, while overview, timeline, manage and the registration answers page all use it. That left two sizes for the whole page: a 21px name, then an undifferentiated grey field with no rung between them. The disclaimer above the answers was physically larger than the answers it qualified, on a page whose reason to exist is those answers. And each answer ran its question and its value together on one line at one size, so "Which university are you with? University of Basel" read as a single sentence with no column to scan down. Sentences move to `.prose`, headings to `text-section`, answers to `text-body`, and the answers themselves into a two-column grid with the question quieter beside the value. The visibility note drops below them as the footnote it always was. The two sections become cards, and the column is capped — this page is one person and several sentences, not a roster that wants the width. The question labels deliberately do not use `.meta`, which uppercases: these labels are whole questions, and a question shouted in 11px capitals is harder to read, not easier.
sabinem
force-pushed
the
feat/participants-shared-answers
branch
from
September 1, 2026 19:43
24ae872 to
648e77e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reading someone's profile no longer feels like reading a receipt
Who it's for: anyone clicking a name in the participant list to find out who they're about to team up with.
Before: the page was a big name at the top and then a flat wall of tiny grey text, all one size, stretching the full width of your monitor. Lines ran about twice as long as is comfortable to read. The small print explaining who can see the answers was actually bigger on the page than the answers themselves. And each question ran straight into its answer on the same line, so "Which university are you with? University of Basel" looked like one sentence — you had to hunt for where the answer started.
Now: sentences are set in a readable size and width, headings look like headings, the answers are the most prominent thing on the page, and each question sits in its own column beside its answer so your eye can run down the list. The two sections are boxed so the page reads as three parts instead of one long dribble.
Left out on purpose: no new information is shown. There's still no photo, bio, affiliation or skills, because the system doesn't store any of those yet — this is the same content, just set so it can be read.