feat: redesign homepage with parallax expedition experience - #100
feat: redesign homepage with parallax expedition experience#100dekanbro wants to merge 8 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 4 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (7)
📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThe homepage now renders a client-side ChangesHomepage experience
Estimated code review effort: 4 (Complex) | ~45 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
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 `@src/components/HomeExperience.module.css`:
- Line 9: Fix the Stylelint violations in HomeExperience.module.css by adding
the required declaration separator before the background declaration and
changing all reported currentColor values to lowercase currentcolor, including
the occurrences at the referenced locations.
- Around line 162-165: Update the closed-state .nav styling so its links cannot
receive keyboard focus while the mobile navigation is hidden, adding visibility:
hidden alongside the existing opacity and pointer-events behavior. Restore
visibility: visible in .navOpen, preserving the current open and closed
transitions.
🪄 Autofix
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: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: bccbb5c6-98e6-4b66-b8c5-0231d734a9b6
⛔ Files ignored due to path filters (4)
public/images/neo/hero-foreground.pngis excluded by!**/*.pngpublic/images/neo/raidguild-panorama.pngis excluded by!**/*.pngpublic/images/neo/raidguild-swords.pngis excluded by!**/*.pngpublic/images/neo/sky-citadel.pngis excluded by!**/*.png
📒 Files selected for processing (3)
src/app/page.tsxsrc/components/HomeExperience.module.csssrc/components/HomeExperience.tsx
| --coral: #ee3c78; | ||
| --rust: #b84031; | ||
| --acid: #d7e34d; | ||
| background: var(--paper); |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Fix the reported Stylelint errors.
Add the required declaration separator before background. Change the reported currentColor values to currentcolor to satisfy the configured Stylelint rule.
Also applies to: 32-33, 37-37, 112-112, 134-134
🧰 Tools
🪛 Stylelint (17.14.0)
[error] 9-9: Expected empty line before declaration (declaration-empty-line-before)
(declaration-empty-line-before)
🤖 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 `@src/components/HomeExperience.module.css` at line 9, Fix the Stylelint
violations in HomeExperience.module.css by adding the required declaration
separator before the background declaration and changing all reported
currentColor values to lowercase currentcolor, including the occurrences at the
referenced locations.
Source: Linters/SAST tools
| .nav { align-items: flex-start; background: var(--deep); flex-direction: column; inset: 0; justify-content: center; opacity: 0; padding: 90px 30px; pointer-events: none; position: fixed; transform: translateY(-15px); transition: opacity .25s, transform .25s; } | ||
| .nav a { font-family: var(--font-display), serif; font-size: 42px; letter-spacing: -.03em; text-transform: none; } | ||
| .navCta { border: 0; padding: 0; } | ||
| .navOpen { opacity: 1; pointer-events: auto; transform: translateY(0); } |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Remove closed navigation links from the tab order.
At mobile widths, .nav remains rendered while closed. pointer-events: none does not prevent keyboard focus on the links in src/components/HomeExperience.tsx lines 131-134. Add visibility: hidden when closed and restore it in .navOpen, or conditionally render an inert navigation state.
Proposed fix
.nav {
+ visibility: hidden;
align-items: flex-start;
background: var(--deep);
flex-direction: column;
@@
.navOpen {
opacity: 1;
pointer-events: auto;
transform: translateY(0);
+ visibility: visible;
}🤖 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 `@src/components/HomeExperience.module.css` around lines 162 - 165, Update the
closed-state .nav styling so its links cannot receive keyboard focus while the
mobile navigation is hidden, adding visibility: hidden alongside the existing
opacity and pointer-events behavior. Restore visibility: visible in .navOpen,
preserving the current open and closed transitions.
concept off louchi ideas
Summary by CodeRabbit