Skip to content

Update navbar to monochrome design with theme-appropriate shadows#133

Closed
ankitkr104 wants to merge 0 commit intoAOSSIE-Org:mainfrom
ankitkr104:feature/monochrome-navbar
Closed

Update navbar to monochrome design with theme-appropriate shadows#133
ankitkr104 wants to merge 0 commit intoAOSSIE-Org:mainfrom
ankitkr104:feature/monochrome-navbar

Conversation

@ankitkr104
Copy link
Copy Markdown

@ankitkr104 ankitkr104 commented Mar 26, 2026

This PR updates the Navbar component to follow a strictly monochrome (black and white) design language in both light and dark modes. The goal was to remove unnecessary color accents from the navigation container to create a more neutral and elegant user experience while maintaining the site's branding.

Recordings:

Social.share.mp4

Checklist

  • My code follows the project's code style and conventions
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings or errors
  • I have joined the Discord server and I will share a link to this PR with the project maintainers there
  • I have read the Contributing Guidelines

⚠️ AI Notice - Important!

We encourage contributors to use AI tools responsibly when creating Pull Requests. While AI can be a valuable aid, it is essential to ensure that your contributions meet the task requirements, build successfully, include relevant tests, and pass all linters. Submissions that do not meet these standards may be closed without warning to maintain the quality and integrity of the project. Please take the time to understand the changes you are proposing and their impact. AI slop is strongly discouraged and may lead to banning and blocking. Do not spam our repos with AI slop.

Summary by CodeRabbit

  • Style
    • Refined navbar appearance with a cleaner solid background, improved border styling, theme-aware drop shadows, and smoother transitions for a more consistent header experience.
    • Adjusted logo text color to follow the app’s foreground theme, ensuring proper visibility in both light and dark modes.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 26, 2026

Warning

Rate limit exceeded

@ankitkr104 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 9 minutes and 7 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 591cae72-fbca-42dc-a5e2-d29adbdd838a

📥 Commits

Reviewing files that changed from the base of the PR and between 60e26d3 and 545a4bd.

📒 Files selected for processing (1)
  • landing-page/src/components/Navbar.tsx

Walkthrough

Navbar styling changed: removed semi-transparent blurred background and white-tinted border; switched to bg-background with border-border, added explicit shadow[...] classes and transition-all. Logo text <span> now includes text-foreground.

Changes

Cohort / File(s) Summary
Navbar Styling
landing-page/src/components/Navbar.tsx
Replaced bg-background/80 + backdrop-blur-md and border-white/10 with bg-background, border-border, added explicit shadow[...] classes and transition-all. Added text-foreground to logo <span>.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

Typescript Lang

Poem

🐰 A crisp new bar upon the page,
No blur or tint to fog the stage,
With shadows neat and text that shines,
I hop with joy at tidy lines 🥕

🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: updating the navbar to a monochrome design with theme-appropriate shadows, which aligns with the removal of color/transparency effects and addition of shadow styling.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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 and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@landing-page/src/components/Navbar.tsx`:
- Line 11: The Navbar component is hardcoding colors (className includes
"bg-white dark:bg-black") which breaks the project's theme token convention;
update the Navbar's className to use the shared theme token (e.g., replace the
explicit bg classes with the token used by other sections such as
"bg-background" and corresponding tokenized border/shadow classes) so it follows
the same theme variables as Hero, Features, EverywhereFeatures, and
CodeShowcase; if the Navbar truly needs a monochrome override, instead add or
use a dedicated theme token (e.g., navbar-background) and reference that in the
Navbar component rather than hardcoding colors.
🪄 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: ASSERTIVE

Plan: Pro

Run ID: 48fb4359-f6cd-408a-b0a6-b8409ee3856c

📥 Commits

Reviewing files that changed from the base of the PR and between 3baea5f and 89fb365.

📒 Files selected for processing (1)
  • landing-page/src/components/Navbar.tsx

@github-actions github-actions bot added size/M and removed size/XS labels Mar 26, 2026
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@landing-page/src/components/Navbar.tsx`:
- Line 11: The dark-mode shadow on the Navbar component introduces a yellow tint
via the class dark:shadow-[0_4px_30px_rgba(255,204,0,0.15)] which breaks the
monochrome requirement; open the Navbar component, find the <nav> element with
the className containing dark:shadow-[0_4px_30px_rgba(255,204,0,0.15)], and
replace that token with a monochrome shadow (for example a neutral/black rgba
like dark:shadow-[0_4px_30px_rgba(0,0,0,0.15)] or remove the dark:shadow class
entirely) so the navbar stays strictly monochrome in dark mode.
🪄 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: ASSERTIVE

Plan: Pro

Run ID: ea714452-87ca-4618-b690-8e27df3acf3d

📥 Commits

Reviewing files that changed from the base of the PR and between 89fb365 and 60e26d3.

📒 Files selected for processing (1)
  • landing-page/src/components/Navbar.tsx

@ankitkr104 ankitkr104 closed this Mar 26, 2026
@ankitkr104 ankitkr104 force-pushed the feature/monochrome-navbar branch from 545a4bd to 3baea5f Compare March 26, 2026 10:03
@ankitkr104 ankitkr104 deleted the feature/monochrome-navbar branch March 26, 2026 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant