Add human design touches. Refactor: Replace custom HTML structures wi…#738
Merged
oliviasculley merged 1 commit intoJun 11, 2026
Merged
Conversation
…th reusable Blade components for heroes, CTAs, buttons, and dropdowns across views.
Author
|
I have another design PR ready with more design changes, but I felt taking baby steps with design and smaller iterations is a less demanding path. |
oliviasculley
approved these changes
Jun 11, 2026
oliviasculley
left a comment
Member
There was a problem hiding this comment.
This seems like such a massive improvement I want to just merge it in now, but I think we should get bogdan's thoughts on using x-whatever as the prefix, not sure if that's convention for laravel or not
but this PR is super awesome and we should fast track this!!
Edit: Yep seems like Laravel convention lol, we already had x-nav-link so I think we're good to merge this
allella
reviewed
Jun 11, 2026
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.
TL;DR: This PR modernizes the site's look using the brand we already have (--color-primary, --color-success, Geist, the existing logo, and photography). Nearly all of it is Blade templates and Tailwind classes. It looks like a big change because the design touches many files — but most of the diff is repeated markup collapsing into ~8 small Blade components, with pages rewritten as short component calls. Also, the copy and text are the same as the current live site.
I tried to keep the ethos of this PR simple: make the design feel more polished and less broken than what we have today. At this stage, I wouldn’t overthink the design direction or spend time debating design decisions. The goal is simply to clean things up, fix inconsistencies, and tune the UI so it feels more cohesive and intentional.
Why now: the current design is already inconsistent in ways users can see:
Overall, the design improves:
Suggested review path: read resources/views/components/ first (8 files, all short) — that's the whole design system. Everything after that is called sites. pint passes, php artisan test passes, yarn build is clean, and every page was verified at desktop and mobile widths.
OLD
NEW