Skip to content

feat: redesign homepage with parallax expedition experience - #100

Open
dekanbro wants to merge 8 commits into
mainfrom
feat/venture-beyond-redesign
Open

feat: redesign homepage with parallax expedition experience#100
dekanbro wants to merge 8 commits into
mainfrom
feat/venture-beyond-redesign

Conversation

@dekanbro

@dekanbro dekanbro commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

concept off louchi ideas

Summary by CodeRabbit

  • New Features
    • Introduced a redesigned home experience with responsive navigation, hero artwork, featured work, mission content, contact section, and footer.
    • Added interactive animations, parallax effects, horizontal wheel navigation, and reduced-motion support.
    • Added responsive layouts optimized for mobile and desktop screens.
    • Improved page metadata with a title and description.
    • Updated organization information displayed in structured data.

@vercel

vercel Bot commented Aug 7, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
website Ready Ready Preview Aug 7, 2026 5:11pm

Request Review

@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@dekanbro, you've reached your PR review limit, so we couldn't start this review.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 0c8e78d6-9695-46d7-b5f7-32fbda8f558a

📥 Commits

Reviewing files that changed from the base of the PR and between f48eb23 and 6e5f3ec.

⛔ Files ignored due to path filters (7)
  • bun.lock is excluded by !**/*.lock
  • public/images/neo/field-autonomous-treasury.png is excluded by !**/*.png
  • public/images/neo/field-protocol-garden.png is excluded by !**/*.png
  • public/images/neo/field-signal-commons.png is excluded by !**/*.png
  • public/images/neo/raidguild-panorama.png is excluded by !**/*.png
  • src/app/opengraph-image.jpg is excluded by !**/*.jpg
  • src/app/opengraph-image.png is excluded by !**/*.png
📒 Files selected for processing (4)
  • package.json
  • src/app/page.tsx
  • src/components/HomeExperience.module.css
  • src/components/HomeExperience.tsx
📝 Walkthrough

Walkthrough

The homepage now renders a client-side HomeExperience component. It adds animated interactions, responsive sections, themed styling, reduced-motion support, page metadata, and updated organization structured data.

Changes

Homepage experience

Layer / File(s) Summary
Interactive homepage implementation
src/components/HomeExperience.tsx
Adds the client-side homepage with navigation, hero artwork, guild content, craft disciplines, featured work, creed, contact, and footer sections. It also adds menu, pointer, wheel-pan, parallax, and resize behavior.
Responsive visual styling
src/components/HomeExperience.module.css
Adds the visual theme, animations, layouts, responsive breakpoints, and reduced-motion overrides for the homepage experience.
Page integration and metadata
src/app/page.tsx
Replaces the manually composed homepage with HomeExperience and updates page metadata and organization structured data.

Estimated code review effort: 4 (Complex) | ~45 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the homepage redesign and its parallax expedition experience.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/venture-beyond-redesign

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

📥 Commits

Reviewing files that changed from the base of the PR and between b630790 and f48eb23.

⛔ Files ignored due to path filters (4)
  • public/images/neo/hero-foreground.png is excluded by !**/*.png
  • public/images/neo/raidguild-panorama.png is excluded by !**/*.png
  • public/images/neo/raidguild-swords.png is excluded by !**/*.png
  • public/images/neo/sky-citadel.png is excluded by !**/*.png
📒 Files selected for processing (3)
  • src/app/page.tsx
  • src/components/HomeExperience.module.css
  • src/components/HomeExperience.tsx

--coral: #ee3c78;
--rust: #b84031;
--acid: #d7e34d;
background: var(--paper);

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 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

Comment on lines +162 to +165
.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); }

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant