style(frontend): the organizer's participant page reads like the member's - #289
Merged
Conversation
…er's `participants/[participantId]` was set to be read in 648e77e; this page was left in the shape that one had before it — every sentence 12px mono at the width of the window, two type sizes for the whole page, and each answer running its question into its value on one line, so a question and its answer read as a single sentence with no column to scan. The same treatment, deliberately identical rather than merely similar: capped column, a card per section, `text-section` headings, sentences in `.prose`, and the answers in a two-column grid with the question quieter beside the value. The two pages show one person and differ only in what they may say and do about them, so an organizer moving between them should be reading one page in two states rather than learning a second layout. Nothing an organizer acts on is changed: the email line, the Shared chips, Approve, Make owner, Remove owner, the two-step removal and its reset when the page swaps to another person, and the note explaining why an owner has no Remove button. Answers still render through `AnswerText`, and the value keeps `min-w-0 break-words` so a pasted address wraps rather than widening the column.
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.
Organizers get the same readable profile everyone else got
Who it's for: the organizer opening a participant to decide whether to approve them.
Before: the participant-facing profile was made readable last week, but the organizer's version of the same page was left behind. It was still a wall of tiny grey text at one size, running the full width of the monitor, with each registration question crammed onto the same line as its answer — so deciding about someone meant squinting at exactly the moment you needed to read carefully.
Now: it looks like the page it's a sibling of. Answers are the biggest thing on the screen, each question sits in its own column beside its answer, and the sections are boxed so the page reads as parts instead of one long block.
Nothing about what organizers can do has changed — Approve, Make owner, Remove owner and the two-step removal all work exactly as before, and the confirmation still resets when you move to the next person.