Model for frontend dashboard #146
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
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#146
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?
Model for the frontend dashboard is needed before the actual implementation. The model should be presented to the team for feedback and agreement.
Multiple people can take this issue as different ideas would be nice to discuss.
Parent issue: #145
assign me
I also feel that I need to explain this a bit more.
The model's goal is to show how different HTML elements are constrained by or to each other. So there is no need to draw something complicated or something pretty. It only needs to show which div exist within which div.
draw.io is a good tool for this
An idea of how the dashboard could be built.
An idea for what could be included/how it could look
Dashboard design example
I'll upload my version as well then
As talked about on the meeting this afternoon, every model in this issue is structurally the same and no one in the meeting had any objections to this model we have decided to use this model (can also be found on the wiki) as of now to build an actual implementation.
Someone will be assigned to the related issue for the implementation #187