[Meta] UI guidelines #20
Labels
No labels
Security
TeX
board
done
board
ready
board
todo
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS#20
Loading…
Add table
Add a link
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?
We should document how we design the UI of AlekSIS, as a set of guidelines and probably checklists we can check when reviewing front-end changes and designing UIs in the first place.
@ZugBahnHof Please get this started by documenting the principles you use when reviewing frontend changes.
Notes (WIP, tba):
CSS:
Important: Never convey information solely by color, as this is not accessible. Places where this currently happens (list is not complete):
New Decision by Devmeeting: Page title goes into navbar
Todo: decide which button style to use in which case
Devmeeting decided:
save-button,cancel-button, etc.)When to use which item for selects
(e.g. Switches, Checkboxes, radios, Autocompletes, etc.)
Always provide a way back to the previous page (most PWAs don't have browser navgation)
Primary buttons (save-button etc) should have primary color instead of green
Pick new default secondary color
Spacing guidelines (@hansegucker )
mentioned in merge request !386
mentioned in commit
b984816f62