Repository navigation
Feature/frontend optimization - #7
Merged
Merged
Conversation
style: update ReachUs component to change text color from brass to azure style: update AuthSplitLayout and DashboardShell components to change ticket icon color from brass to azure style: update SiteNav component to change ticket icon color from brass to azure style: update accordion component to change hover text color from brass to azure feat: add BackgroundGrid and BackgroundSpotlight components for layout enhancements style: update button and input components to change focus and hover colors from brass to azure feat: add DestinationCard component for event display with image and stats style: update FAQ, footer, and various pages to change text color from brass to azure fix: add imageUrl field to EventRecord and CreateEventInput types feat: update EventDetailPage to display event image if available refactor: update EventsPage to use EventCard component for event listings feat: integrate QuoteSection into HomePage layout style: update various pages to change hover colors from brass to azure fix: add image URL input field to OrganizerEventFormPage for event creation
There was a problem hiding this comment.
Hi @ezekielelvis! 👋
Your private repo does not have access to Sourcery.
Please upgrade to continue using Sourcery ✨
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces a unified, branded HTML email layout for all outbound emails, ensures consistent and visually appealing event cards with image support, and updates the frontend hero section for a more modern look. It also adds support for event images throughout the backend and frontend, including validation, storage, and display. The most important changes are summarized below:
Email System Overhaul
renderEmailLayoututility, replacing previous plain-text or ad-hoc HTML emails for all notification types. This ensures all emails have a consistent look and feel, with support for CTAs and improved formatting. [1] [2]formatEmailDate) to ensure event dates are consistently presented.Event Image Support
imageUrlfield to the event model, validation schema, and service layer, allowing events to include a featured image. This is reflected in the API, database, and test fixtures. [1] [2] [3] [4] [5] [6]Frontend UI/UX Improvements
index.htmlto include new typefaces used in the hero and throughout the site.These changes collectively enhance the platform's visual identity, user experience, and event discoverability.