Settings: one structure for the settings page before more sections land #696
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
optional
question
S
security
technical improvement
UX Improvement
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
local-it/mitgliederverwaltung#696
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?
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:
Acceptance criteria
Dependencies