Settings: one structure for the settings page before more sections land #696

Open
opened 2026-11-19 13:43:13 +01:00 by simon · 0 comments
Owner

Description

The settings page (MvWeb.GlobalSettingsLive) has grown one section per feature: club, join form, emails to applicants, authentication, SMTP, Vereinfacht, version (lib/mv_web/live/global_settings_live/*_section.ex). Fee settings, data fields and roles live on their own pages. The sections behave differently: some save with a form and a Save button, the emails to applicants use instant switches plus a Save per paragraph (#668). The page has no navigation inside it; links from the What's new list jump to a section by anchor (#683).

The next issues add more settings: the hint for minors and paper applications (#670), retention of join request data (#671), the exit rule (#673), the membership type choice (#675), and a club contact address (separate draft). Without a structure, each issue picks its own place and its own save behaviour.

Proposal

Decide with mockups (light/dark, desktop/390 px) and the positions of Apple HIG, Material 3 and GOV.UK:

  • Grouping: which groups the page has (e.g. club, membership and fees, join and admission, emails, sign-in and security, integrations, system) and which existing pages belong into them or stay separate (fee settings, data fields, roles).
  • Navigation: one long page with an in-page navigation (sticky list or jump links), tabs, or sub-pages per group; how anchor links from What's new keep working.
  • Save behaviour: a rule for when a setting applies at once (switch) and when it needs Save (texts, values that belong together), written into DESIGN_GUIDELINES.
  • Placement rule for new settings, so #670, #671, #673 and later issues know where they go.
  • Build the structure with the existing sections moved into it; no new settings in this issue.

Acceptance criteria

  • The decision (grouping, navigation, save rule) is recorded in DESIGN_GUIDELINES with a placement rule for new settings.
  • Every existing section sits in its group; anchors used by What's new entries still land on the right section.
  • Every section follows the save rule; a section that does not has a recorded exception.
  • Keyboard and screen reader users can reach each group directly (in-page navigation or equivalent); works at 320 px without horizontal scrolling.
  • No setting changes its value or default through the move (test).

Dependencies

## Description The settings page (`MvWeb.GlobalSettingsLive`) has grown one section per feature: club, join form, emails to applicants, authentication, SMTP, Vereinfacht, version (`lib/mv_web/live/global_settings_live/*_section.ex`). Fee settings, data fields and roles live on their own pages. The sections behave differently: some save with a form and a Save button, the emails to applicants use instant switches plus a Save per paragraph (#668). The page has no navigation inside it; links from the What's new list jump to a section by anchor (#683). The next issues add more settings: the hint for minors and paper applications (#670), retention of join request data (#671), the exit rule (#673), the membership type choice (#675), and a club contact address (separate draft). Without a structure, each issue picks its own place and its own save behaviour. ## Proposal Decide with mockups (light/dark, desktop/390 px) and the positions of Apple HIG, Material 3 and GOV.UK: - **Grouping:** which groups the page has (e.g. club, membership and fees, join and admission, emails, sign-in and security, integrations, system) and which existing pages belong into them or stay separate (fee settings, data fields, roles). - **Navigation:** one long page with an in-page navigation (sticky list or jump links), tabs, or sub-pages per group; how anchor links from What's new keep working. - **Save behaviour:** a rule for when a setting applies at once (switch) and when it needs Save (texts, values that belong together), written into DESIGN_GUIDELINES. - **Placement rule for new settings**, so #670, #671, #673 and later issues know where they go. - Build the structure with the existing sections moved into it; no new settings in this issue. ## Acceptance criteria - [ ] The decision (grouping, navigation, save rule) is recorded in DESIGN_GUIDELINES with a placement rule for new settings. - [ ] Every existing section sits in its group; anchors used by What's new entries still land on the right section. - [ ] Every section follows the save rule; a section that does not has a recorded exception. - [ ] Keyboard and screen reader users can reach each group directly (in-page navigation or equivalent); works at 320 px without horizontal scrolling. - [ ] No setting changes its value or default through the move (test). ## Dependencies - After #668 and #683. Before #670, #671 and #673, which add settings.
Sign in to join this conversation.
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
local-it/mitgliederverwaltung#696
No description provided.