Research add new Cards menu #207
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#207
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 want to be able to add new cards through a menu where all available views are visible. It would be useful to research how to structure this menu, models and screenshots specifically. Feel free to experiment!
Something along these lines:
No need to add any actual functionality.
Model 1
Cards are grouped and are in a closed state to begin with. Click on a group to see cards under that group.
Model 1
Cards are grouped and are in a closed state to begin with. If you click on a group the cards under that group will appear and you can choose the card you want.
Model 2
Cards are graphical and use icons to represent each option, making it easier for users to quickly recognize and select a card
Model 3
Combination of Model 1 and Model 2. Groups are shown vertical and can be expanded.
Model 3
Combination of Model 1 and Model 2. Groups are shown horizontal and can be expanded.
All the models look lovely and well-modeled!
In my personal and uneducated opinion, I am leaning more toward Model 2, which has icons that represent the cards more easily.
I also find Model 3, with horizontal grouping, fitting well in our case. However, it needs to be consistent with the icons. So also adding icons to the expandable cards would make more sense and grab the user's attention easier.
On another note, Model 2 feels cohesive with the StudentPortal for our school, making it feel familiar.