Landing Page Update

[ashutoshamazix]

Description

• Copy update
• Added 'Login' Button to nav
• Removed 'Testing Campaign' from nav

How Has This Been Tested?

• Locally

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Summary by CodeRabbit

• New Features

  • Added a "Log in" button to the header, allowing users to navigate directly to the login page.
  • Updated the hero section's call-to-action to "Get started," linking to the login page for easier onboarding.

• Style

  • Enhanced styling for the login button with a new design and improved responsiveness.
  • Increased the maximum width of the hero signup section for better layout on larger screens.

[coderabbitai]

Walkthrough

The changes update the landing page's hero and header to replace the waitlist and Twitter links with a login flow. This includes new styles for the login button, updates to the hero section's text and call-to-action, and the removal of the Twitter link in favor of a login link.

Changes

File(s)	Change Summary
src/components/LandingPage/GlobalStyles/index.jsx	Added .header__login CSS class for styling the login button; increased .home_hero__signup max-width.
src/components/LandingPage/Header/index.jsx	Removed "Testing Campaign" nav item; replaced Twitter anchor link with internal /login React Router Link; removed mobile menu toggle handler.
src/pages/Landing.jsx	Updated hero section text and CTA: changed from waitlist to login, updated link destination and label.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

A bunny hops on landing bright,
Swapping waitlists for login light.
The Twitter bird now flies away,
"Get started" is the call today.
With rounded corners, styles anew—
This page invites both old and new!
🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

npm error Exit handler never called!
npm error This is an error with npm itself. Please report this error at:
npm error https://github.com/npm/cli/issues
npm error A complete log of this run can be found in: /.npm/_logs/2025-07-25T13_59_24_577Z-debug-0.log

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d800d36 and 269b75f.

⛔ Files ignored due to path filters (1)

• src/containers/__snapshots__/Main.test.tsx.snap is excluded by !**/*.snap

📒 Files selected for processing (3)

• src/components/LandingPage/GlobalStyles/index.jsx (2 hunks)
• src/components/LandingPage/Header/index.jsx (1 hunks)
• src/pages/Landing.jsx (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• src/components/LandingPage/GlobalStyles/index.jsx

🚧 Files skipped from review as they are similar to previous changes (1)

• src/pages/Landing.jsx

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: lint
• GitHub Check: unit-tests
• GitHub Check: build

🔇 Additional comments (1)

src/components/LandingPage/Header/index.jsx (1)

69-74: LGTM! Clean implementation of the login navigation link.

The login link is properly implemented using React Router's Link component with appropriate CSS classes for styling and analytics tracking. The routing to "/login" and "Log in" text are clear and user-friendly.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/landing-page-changes

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/pages/Landing.jsx (1)

35-39: Consider updating the analytics event name.

The routing change to "/login" and "Get started" CTA are appropriate, but the className still references "Waitlist+Home+Hero" which may no longer accurately reflect the user action for analytics tracking.

Consider updating the analytics event name:

-                className="cta plausible-event-name=Waitlist+Home+Hero"
+                className="cta plausible-event-name=Login+Home+Hero"

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ae9917e and d800d36.

📒 Files selected for processing (3)

• src/components/LandingPage/GlobalStyles/index.jsx (2 hunks)
• src/components/LandingPage/Header/index.jsx (1 hunks)
• src/pages/Landing.jsx (1 hunks)

🔇 Additional comments (5)

src/components/LandingPage/GlobalStyles/index.jsx (3)

450-455: Well-implemented login button styling.

The new .header__login class provides appropriate styling with consistent use of CSS variables and follows the existing design patterns in the codebase.

---

457-461: Good responsive design consideration.

The media query appropriately adjusts the login button spacing for mobile devices, ensuring proper visual hierarchy on smaller screens.

---

680-680: Max-width adjustment supports layout changes.

The increase from 78rem to 80rem for .home_hero__signup properly accommodates the updated hero section content.

src/pages/Landing.jsx (1)

31-33: Content update improves messaging clarity.

The new hero text provides a clearer value proposition about the app's core functionality rather than focusing solely on waitlist participation.

src/components/LandingPage/Header/index.jsx (1)

78-80: Cannot find /login route in routing setup

I searched across .js, .jsx, .ts, and .tsx files but didn’t locate any <Route path="/login"…> (or equivalent useRoutes) entry. Please manually verify that:

• Your router configuration (e.g. src/App.js, src/routes.js, or src/router/index.js) includes a route for /login.
• A Login page/component file exists (e.g. src/pages/Login.jsx or similar) and is correctly imported.

[cloudflare-workers-and-pages]

Deploying x with    Cloudflare Pages

Latest commit:	269b75f
Status:	✅  Deploy successful!
Preview URL:	https://cf91794a.x-e62.pages.dev
Branch Preview URL:	https://chore-landing-page-changes.x-e62.pages.dev

View logs