Task: Refactor homepage hero banner using DaisyUI hero component #149
Labels
No labels
accessibility
api
auth.js
backend
copy
database
defect
dependencies
design
discussion
documentation
duplicate
enhancement
epic
feature
front-end
good first issue
help wanted
invalid
next.js
noscript
on hold
operations
optimization
postgresql
prisma
prototype
question
react
spike
stale
story
tailwind
vulnerability
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
SSE/WebsiteTheSSEquel#149
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?
Description
For maintainability and aesthetic purposes, let's see if we can use DaisyUI's hero component for our homepage hero section
Pre-changes
Post-refactoring using DaisyUI Hero Component
In short, the biggest change is in the horizontal margin/padding which imo looks less cluttered.
The DaisyUI template includes a solid background color, which highlights the component and makes it distinct. Currently, our page doesn’t use many solid colors to separate sections, which might make it harder for users to distinguish between different components. How could we adjust the visual structure to improve the clarity and flow between sections?
Modern pages often use either a background image or a solid background color to clearly distinguish the hero component. Incorporating a similar approach could help users instantly recognize the hero section and provide a stronger visual hierarchy for the page.
I'll bring this up to the UX Design team. Other than that, this issue can be closed. I'm opening a PR.
Closing this as it appears to have been merged into main