Create Glossary for components #197
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#197
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 need a glossary for often used components, both front and back end, to reduce confusion. Needs a wiki page!
Would probably be good to have images for front-end components.
Navigation Bar (Navbar)
The navigation bar is located at the top (header) of the webpage. The navigation bar should include elements such as settings, login/logout, user information and perhaps a logo. The navigation bar is illustrated in the wiki -- link to the wiki page with the model -- (“<>”).
Dashboard
The dashboard represents the main body of the webpage, positioned below the header. IT contains the primary content of the site, and is in our specific case displayed in the form of cards. The content shown in the dashboard may vary depending on which user is logged in, as a user can personalize their cards.
Footer
The footer is located at the bottom of the webpage. Although it is not shown in the wiki, it is a common component in modern web design. The footer typically contains information such as contact details, news and links to social media platforms. In this project, it could also include a link to his.se and additional information about the project.
Not sure where to put the text in the wiki so I commented instead. Should I create one and if so, where?
The three components are clearly described, and the navbar aligns well with the frontend model in the wiki based on what it should contain.
The dashboard component description also reflects the intended purpose of displaying content as cards and footer is explained well for now based on how it will be implemented later on.
This review has been properly done, i will close this issue.