Skip to content

feat(frontend): settings grouped switches - #372

Merged
sabinem merged 2 commits into
mainfrom
feat/settings-grouped-switches
Oct 22, 2026
Merged

sabinem merged 2 commits into
mainfrom
feat/settings-grouped-switches

Conversation

@sabinem

@sabinem sabinem commented Oct 22, 2026

Copy link
Copy Markdown
Collaborator

Settings becomes a step-by-step guide for running a hackathon

As an organizer, I want the Settings page to tell me what to switch on and when, and to warn me before I lose a change I didn't save.

Before, "What participants can do" was a flat list of seven checkboxes with one-line descriptions. Nothing said what order they come in or what happens between them, for example that people who register must be approved, or that teams are formed on another page. Ticking a box and then clicking away dropped the change without a word.

Now the switches are an eight-step guide in the order a hackathon runs: register, projects, project preferences, team assignments, hacking, voting setup, voting, results. Each switch sits at its step, labelled for the organizer ("Open registration", "Publish results"). The steps that aren't switches link to the page where they happen. A bar at the top shows what's unsaved, with Save and Discard, and leaving the page asks first, as on Manage Teams.

  • Register links to the registration form and to Manage Participants, because everyone who registers waits for approval. A private hackathon also links to its invitation links.
  • Publish results says to turn voting off and make the results final first, linking to Manage Voting. The switch stays locked until then, as before.
  • "Set team preferences" is now "Choose preferred projects". Participants see this label too, on their Timeline and "You can now" card.
  • A switch the backend adds later still shows, under "Other", rather than disappearing.

Left out on purpose

  • The save bar is a copy of Manage Teams' bar, not a shared component. Sharing it would mean changing the 1,500-line Manage Teams page in this PR. That cleanup can come separately.
  • The guide is advice only. Switches can still be turned on in any order, and nothing here changes what a switch allows.
  • Jury voting isn't on the platform. The guide says to leave voting and results off if a jury decides outside it.

…zers

- Eight steps in the order a hackathon runs: register, projects,
  preferences, team assignments, hacking, voting setup, voting, results
- Each switch sits at its step, labelled for the organizer
  ("Open registration", "Publish results")
- Links to the pages in between: registration form, approving
  participants, invitation links (private only), Manage Projects,
  Manage Teams, Manage Voting
- "Set team preferences" is now "Choose preferred projects" on the
  participant pages too
- A switch no step names still shows, under "Other"
- A bar at the top lists what is unsaved, with Save and Discard, and
  sticks below the nav bar while scrolling
- Changed switches are tinted until saved
- Leaving through a link asks first; closing the tab, or pressing a
  phase button, gets the browser's own prompt
- Saving stays on the page; a failed save keeps the ticks
@sabinem
sabinem merged commit 7447c70 into main Oct 22, 2026
3 checks passed
@sabinem
sabinem deleted the feat/settings-grouped-switches branch October 22, 2026 07:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant