#251 Made a 404 page #265
No reviewers
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked-waiting-for-further-changes
bug
bug-only-on-server-for-mobile-not-webpage
Bug-Report-After-Merge
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
further-changes-needed
future-problem-not-fixint-this-period
help wanted
invalid
last-week-issue-to-fix
library
low-priority
needs input
needs review
not-implemented.
project documentation
question
research
reviewed
Script
security
SQL
style
Team 1
Team 2
team leaders
test-creation
testing
topLevel
unassigned
Under-review
wontfix
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K!265
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "#251-Create-404-page"
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?
The 404 page catches all unknown paths and routes to the 404 page. The 404 page has a button which links to the home page. However since nginx only starts after App is started, we can't catch anything before app starts. For example: localhost/ap will lead to nginx own 404 page which has no way to link to our home page.
Please read the wiki page before reviewing
https://git.webug.se/Andras/BoundlessFlowCampus2K/wiki/Webpage-Design
reviewed based on the Webpage Design guidelines.
What I reviewed:
The layout and structure of the 404 page
Use of colors and adherence to the University colour palette
UI elements and overall usability
Whether the design follows the project’s graphical guidelines
Observations:
The page has a clear and simple layout with a centered card, which makes it easy for users to understand that the page was not found.
The header includes the application name and an icon, which helps maintain branding visibility.
The (Return to Home page) button is a good usability feature and provides a clear navigation path for the user.
Design and guidelines:
The main content area is light/white, which aligns with the guideline for the main body.
However, the illustration uses colors such as yellow, bright blue, pink, and purple, which do not match the defined University colour palettes (Rubine, Safir, Smaragd, Topas, Grafit).
The colors appear to be generic/emoji-style rather than using the specified palette hues.
It is also unclear whether the required fonts (AGENDA/TRUMP MEDIAEVAL or their fallbacks) are being used.
Functionality:
The 404 page works as expected for unknown routes handled by the application.
The limitation with nginx (not catching routes before the app starts) is clearly explained and acceptable.
Conclusion:
The implementation works well functionally and provides a clear user experience. However, the design could be improved by aligning more closely with the University’s colour palette and font guidelines to ensure consistency with the project standards.
The review has been conducted in a proper way. Regarding the design aligning more to the university this will be done with buttons having the pruple color etc.