Source code rules - UI exploration
Goal
The goal of this issue is to investigate the structure or pattern of UI layout and the required components. This is dependant on the discussion in How "rules" should be organized but makes the assumption that we would want to standardize these layouts.
Display a "list" of "controls"
All of the controls have multiple "rules" or instances of that control so we will likely need a method for displaying those "rules".
Considerations
- Dependent on what fields we include
- Scanability is important
- Flexibility is needed to be able to account for the variance in data displayed
- Options
Additive UI
- Only show rules users have added
- Robust add rule feature that walks users through what they could do
Detail display
Depending on the Display a "list" of "controls", this may not be needed, but it is likely not all information will be possible to display and a view to see additional information will be needed.
Considerations
- Preferably in context with the "list" or in a way that allows users quick access
- Flexibility is needed to be able to account for the variance in data displayed
- Options
- Expanding the "list" item
- Modal
- Sidebar
- New page
List filtering, sorting, grouping
If "controls" are combined the need for filtering, sorting and grouping will be key for the user to be able to quickly find the "rule" they are looking for as the number of them grows, but also could be a key way to mitigate resistance to change migrating from established features. These could be replicated as filters.
Dynamic grouping could be an interesting solution
- Ability to choose how data is grouped
- List updates and optimizes for scalability
Edit flow
Considerations
- Preferably in context with the "list" or in a way that allows users quick access
- Flexibility is needed to be able to account for the variance in data displayed
- Options
- In line
- Modal
- Sidebar
- New page