Refactor: UI colors for consistency and accessibility - #7
Merged
Conversation
Replaced gradient text and borders with solid teal-cyan-aqua-600 across headings, buttons, and FAQ items for improved consistency and accessibility. Updated FAQ link and button ring colors for better contrast. Fixed a minor typo in ContactForm.razor.
WalkthroughThe changes update landing-page text and panel styling, FAQ colors and open-state borders, the header navigation ring color, and the contact badge text. ChangesVisual updates
Estimated code review effort: 2 (Simple) | ~5 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@Features/Landing/Components/HeroWarmTealWash.razor`:
- Line 22: Localize every listed user-facing string using the established
localized accessor and add matching resource keys:
Features/Landing/Components/HeroWarmTealWash.razor lines 22-22 (“Less
busywork.”), Features/Landing/Components/Mission.razor lines 22-23 (“Smart
Technology”) and 43-45 (“empower businesses”),
Features/Landing/Components/Services.razor lines 22-22 (“You Focus on Growing
and Making Money.”), Layout/Header.razor line 29 (“Let's Talk”), and
Features/Contact/Components/ContactForm.razor line 9 (“Get In Touch”).
In `@Features/Legal/Components/Faq.razor.css`:
- Around line 159-160: Update the hover styling for the .faq-inline-link
selector to use a darker, higher-contrast color such as `#0e7490` instead of
`#06b6d4`, while preserving the new dark base color and other link styles.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 993a486f-5d80-4bfb-b082-85cb32e24962
📒 Files selected for processing (6)
Features/Contact/Components/ContactForm.razorFeatures/Landing/Components/HeroWarmTealWash.razorFeatures/Landing/Components/Mission.razorFeatures/Landing/Components/Services.razorFeatures/Legal/Components/Faq.razor.cssLayout/Header.razor
| <h1 class="text-5xl sm:text-6xl lg:text-5xl xl:text-6xl leading-[1.05] mb-6 tracking-tight"> | ||
| <span class="entrance entrance-2 block font-bold text-gray-900">Smart systems.</span> | ||
| <span class="entrance entrance-3 block font-bold bg-gradient-to-r from-teal-cyan-aqua-600 to-cloudzen-teal bg-clip-text text-transparent">Less busywork.</span> | ||
| <span class="entrance entrance-3 block font-bold text-teal-cyan-aqua-600">Less busywork.</span> |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Localize the touched user-facing strings.
These Razor segments bypass localization. Use @L["Key"] or the project’s established localized accessor and add the corresponding resource keys.
Features/Landing/Components/HeroWarmTealWash.razor#L22-L22: localizeLess busywork.Features/Landing/Components/Mission.razor#L22-L23: localizeSmart Technology.Features/Landing/Components/Mission.razor#L43-L45: localizeempower businesses.Features/Landing/Components/Services.razor#L22-L22: localizeYou Focus on Growing and Making Money.Layout/Header.razor#L29-L29: localizeLet's Talk.Features/Contact/Components/ContactForm.razor#L9-L9: localizeGet In Touch.
📍 Affects 5 files
Features/Landing/Components/HeroWarmTealWash.razor#L22-L22(this comment)Features/Landing/Components/Mission.razor#L22-L23Features/Landing/Components/Mission.razor#L43-L45Features/Landing/Components/Services.razor#L22-L22Layout/Header.razor#L29-L29Features/Contact/Components/ContactForm.razor#L9-L9
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@Features/Landing/Components/HeroWarmTealWash.razor` at line 22, Localize
every listed user-facing string using the established localized accessor and add
matching resource keys: Features/Landing/Components/HeroWarmTealWash.razor lines
22-22 (“Less busywork.”), Features/Landing/Components/Mission.razor lines 22-23
(“Smart Technology”) and 43-45 (“empower businesses”),
Features/Landing/Components/Services.razor lines 22-22 (“You Focus on Growing
and Making Money.”), Layout/Header.razor line 29 (“Let's Talk”), and
Features/Contact/Components/ContactForm.razor line 9 (“Get In Touch”).
Source: Coding guidelines
Comment on lines
159
to
+160
| .faq-inline-link { | ||
| color: #0891b2; | ||
| color: #40676B; |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Keep the FAQ link readable on hover.
The new dark base color is appropriate, but the existing #06b6d4 hover color is low-contrast for normal text on a white background. Use a darker hover color such as #0e7490.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@Features/Legal/Components/Faq.razor.css` around lines 159 - 160, Update the
hover styling for the .faq-inline-link selector to use a darker, higher-contrast
color such as `#0e7490` instead of `#06b6d4`, while preserving the new dark base
color and other link styles.
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
1 participant
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.
Refactor: UI colors for consistency and accessibility
Replaced gradient text and borders with solid teal-cyan-aqua-600 across headings, buttons, and FAQ items for improved consistency and accessibility. Updated FAQ link and button ring colors for better contrast. Fixed a minor typo in ContactForm.razor.
Summary by CodeRabbit
Bug Fixes
Style