Skip to content

Comments

Chore/landing-page-update#366

Merged
ashutoshamazix merged 3 commits intostagingfrom
chore/landing-page-update
Jul 9, 2025
Merged

Chore/landing-page-update#366
ashutoshamazix merged 3 commits intostagingfrom
chore/landing-page-update

Conversation

@ashutoshamazix
Copy link
Collaborator

@ashutoshamazix ashutoshamazix commented Jul 9, 2025

Description

  • Landing page copy update

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

  • Style

    • Improved layout and text wrapping on the landing page for better visual alignment across devices.
    • Adjusted sizing of key containers for enhanced readability.
  • New Features

    • Updated landing and waitlist page messaging to highlight PX Points collection and exclusivity for waitlist and Pillar users, replacing previous prize pool campaign details.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 9, 2025

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)
  • src/containers/__snapshots__/Main.test.tsx.snap is excluded by !**/*.snap

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The changes update the landing and waitlist page content to shift messaging from a prize pool campaign to an emphasis on collecting PX Points during the PillarX soft launch. Associated style adjustments modify the layout and text wrapping of key elements on the landing page, but no functional or exported entity changes are introduced.

Changes

File(s) Change Summary
src/components/LandingPage/GlobalStyles/index.jsx Adjusted CSS for hero content and signup containers: changed transform values, max-widths, and heading width.
src/pages/Landing.jsx Updated landing page paragraph text to promote PX Points collection instead of a prize pool campaign.
src/pages/WaitList.jsx Revised waitlist heading and paragraph to focus on PX Points, removing prize pool references and links.

Suggested reviewers

  • RanaBug

Poem

A shift in the wind, a tweak in the style,
PX Points await—join in for a while!
The prize pool has sailed, but the fun’s just begun,
With layouts that shimmer and headlines that stun.
Hop on the list, let your inbox sing—
PillarX soft launch is just the thing!
🥕✨


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

@ashutoshamazix ashutoshamazix requested a review from IAmKio July 9, 2025 11:13
Copy link
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: 0

🧹 Nitpick comments (1)
src/pages/WaitList.jsx (1)

65-70: Double-check heading hierarchy & tone

Good to see the H1 updated. Verify that no other <h1> exists on this page (SEO) and consider mirroring the lower-case “for” nitpick from Landing.jsx for consistency.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between eb56588 and c64933f.

📒 Files selected for processing (3)
  • src/components/LandingPage/GlobalStyles/index.jsx (3 hunks)
  • src/pages/Landing.jsx (1 hunks)
  • src/pages/WaitList.jsx (1 hunks)
⏰ 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). (2)
  • GitHub Check: lint
  • GitHub Check: unit-tests
🔇 Additional comments (4)
src/pages/Landing.jsx (1)

31-32: Lower-case “for” for smoother copy

“Exclusively For Waitlist…” reads as a proper-noun; marketing copy usually keeps the preposition lower-case (“for”).
[ suggest_nitpick ]

-  Join PillarX Soft Launch and Collect PX Points! Exclusively For
-  Waitlist Participants & Pillar Users.
+  Join PillarX Soft Launch and Collect PX Points! Exclusively for
+  waitlist participants & Pillar users.
src/components/LandingPage/GlobalStyles/index.jsx (3)

612-621: Confirm new translateY offsets on all breakpoints

Changing from −130 %/−300 % → −112 %/−240 % alters vertical alignment of the hero logo. Please sanity-check on common screen sizes—small discrepencies here can push the image out of view.


667-668: 78 rem may overflow smaller laptops

.home_hero__signup now allows 78 rem; the top-level container caps at 140 rem, but on 1440 px width a side-margin of 4 rem leaves ~136 rem of space—still safe, yet worth testing at 1280 px.


975-978: Reduced max-width to 18 ch looks good

Tighter line-length will improve readability of massive headings—nice tweak.

Copy link
Collaborator

@IAmKio IAmKio left a comment

Choose a reason for hiding this comment

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

LGTM

@cloudflare-workers-and-pages
Copy link

Deploying x with  Cloudflare Pages  Cloudflare Pages

Latest commit: 11062c1
Status: ✅  Deploy successful!
Preview URL: https://5d7d5eb7.x-e62.pages.dev
Branch Preview URL: https://chore-landing-page-update.x-e62.pages.dev

View logs

@ashutoshamazix ashutoshamazix merged commit d4fc3ad into staging Jul 9, 2025
5 checks passed
@ashutoshamazix ashutoshamazix deleted the chore/landing-page-update branch July 9, 2025 11:36
@coderabbitai coderabbitai bot mentioned this pull request Oct 2, 2025
3 tasks
@coderabbitai coderabbitai bot mentioned this pull request Dec 22, 2025
3 tasks
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.

2 participants