Skip to content

Landing page update#358

Merged
IAmKio merged 7 commits intostagingfrom
chore/landing-page-copy-update
Jul 2, 2025
Merged

Landing page update#358
IAmKio merged 7 commits intostagingfrom
chore/landing-page-copy-update

Conversation

@ashutoshamazix
Copy link
Collaborator

@ashutoshamazix ashutoshamazix commented Jul 2, 2025

Description

  • Added a new page for Privacy Policy
  • Copy update on landing pages

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

    • Introduced a dedicated Privacy Policy page accessible to all users via the site navigation and footer.
    • Expanded the footer with distinct sections for privacy policy access and social media links (X and Telegram).
  • Enhancements

    • Updated campaign messaging across the landing and waitlist pages to announce a $10,000 prize pool for the soft launch campaign.
    • Improved footer layout and styling for better navigation and clarity.
    • Refined styles for privacy policy and campaign-related content for enhanced readability.
  • Documentation

    • Added detailed privacy policy content outlining data practices, analytics, cookie usage, and user rights.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 2, 2025

Walkthrough

The changes introduce a new Privacy Policy page, update navigation and routing to include this page for all users, and revamp the footer to add privacy and social media links. Campaign messaging on the landing and waitlist pages is updated to reflect a new $10,000 prize pool and revised legal disclaimers. Footer and privacy-specific styles are also enhanced.

Changes

File(s) Change Summary
src/pages/Privacy.jsx Added new Privacy Policy page as a React component with detailed policy content and export.
src/containers/Main.tsx
src/navigation/index.tsx
Added /privacy-policy route and integrated Privacy page into navigation for all users.
src/components/LandingPage/Footer/index.jsx Footer restructured: added Privacy Policy link, expanded social links (X and Telegram), updated layout.
src/components/LandingPage/GlobalStyles/index.jsx Updated footer and hero styles, added privacy page styles, tweaked typography and layout for consistency.
src/pages/Landing.jsx
src/pages/WaitList.jsx
Updated campaign messaging to announce $10,000 prize pool and revised legal/terms content.

Sequence Diagram(s)

sequenceDiagram
  participant User
  participant Router
  participant PrivacyPage
  participant Footer

  User->>Footer: Clicks "Privacy Policy" link
  Footer->>Router: Navigates to /privacy-policy
  Router->>PrivacyPage: Renders Privacy component
  PrivacyPage-->>User: Displays privacy policy content
Loading

Suggested reviewers

  • RanaBug

Poem

A privacy page now stands so tall,
With links for X and Telegram for all.
The footer’s neat, the prize pool’s grown,
Ten thousand reasons to make it known!
With styles refreshed and routes anew,
This bunny hops to thank the crew! 🐇✨

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-02T09_15_37_754Z-debug-0.log


📜 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 32269a6 and 489618f.

📒 Files selected for processing (1)
  • src/components/LandingPage/GlobalStyles/index.jsx (7 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/components/LandingPage/GlobalStyles/index.jsx
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: unit-tests
  • GitHub Check: lint
  • GitHub Check: build
✨ Finishing Touches
  • 📝 Generate Docstrings

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.

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: 1

🧹 Nitpick comments (1)
src/components/LandingPage/Footer/index.jsx (1)

14-28: Consider improving alt text for better accessibility.

The social media links are properly configured with security attributes, but the alt text could be more descriptive.

Consider updating the alt text to be more descriptive:

-                <img src="https://cdn.pillarx.app/home-x.svg" alt="x-image" />
+                <img src="https://cdn.pillarx.app/home-x.svg" alt="Follow us on X (Twitter)" />
-                  alt="home-image"
+                  alt="Join our Telegram group"
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between cf421b8 and 32269a6.

📒 Files selected for processing (7)
  • src/components/LandingPage/Footer/index.jsx (1 hunks)
  • src/components/LandingPage/GlobalStyles/index.jsx (7 hunks)
  • src/containers/Main.tsx (4 hunks)
  • src/navigation/index.tsx (3 hunks)
  • src/pages/Landing.jsx (1 hunks)
  • src/pages/Privacy.jsx (1 hunks)
  • src/pages/WaitList.jsx (2 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (3)
src/navigation/index.tsx (1)
src/pages/Privacy.jsx (1)
  • Privacy (8-148)
src/pages/Privacy.jsx (3)
src/components/LandingPage/GlobalStyles/index.jsx (1)
  • GlobalStyles (11-2598)
src/components/LandingPage/Header/index.jsx (1)
  • Header (7-105)
src/components/LandingPage/Footer/index.jsx (1)
  • Footer (4-34)
src/containers/Main.tsx (1)
src/pages/Privacy.jsx (1)
  • Privacy (8-148)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: lint
  • GitHub Check: unit-tests
🔇 Additional comments (29)
src/pages/Landing.jsx (1)

31-32: LGTM! Campaign message update looks good.

The updated campaign messaging with the increased prize pool and "Special Soft Launch Campaign" branding aligns well with the PR objectives for landing page updates.

src/navigation/index.tsx (4)

19-19: LGTM! Privacy component import added correctly.

The import follows the existing pattern and is properly placed with other page imports.


26-26: LGTM! Privacy route added to navigation routes.

The /privacy-policy path is descriptive and follows good URL naming conventions.


50-53: LGTM! Privacy route properly added to authorized navigation.

The route configuration follows the existing pattern and is correctly placed with other routes.


74-74: LGTM! Privacy route added to unauthorized navigation.

The route is correctly added to the Routes component, making the Privacy Policy accessible to all users regardless of authentication status.

src/containers/Main.tsx (4)

44-44: LGTM! Privacy component import added correctly.

The import is properly placed with other page imports and follows the existing pattern.


226-229: LGTM! Privacy route added to authorized routes.

The route configuration is consistent with other routes and properly nested within the authorized route structure.


279-280: LGTM! Root page check updated to include privacy policy.

Adding /privacy-policy to the root page check ensures proper navigation behavior for unauthenticated users accessing the privacy policy directly.


309-312: LGTM! Privacy route added to unauthorized routes.

The route is correctly configured for unauthorized users, making the Privacy Policy accessible to all visitors.

src/components/LandingPage/Footer/index.jsx (2)

2-2: LGTM! Link import added for internal navigation.

The import is necessary for the Privacy Policy internal link and follows React Router best practices.


11-13: LGTM! Privacy Policy link added correctly.

The internal navigation link uses React Router's Link component appropriately and follows the established routing pattern.

src/pages/Privacy.jsx (7)

1-7: LGTM! Component imports and setup are correct.

The imports follow the established pattern and the ESLint disable comment is appropriate for the jsx-props-no-spreading rule.


8-17: LGTM! Component structure follows established patterns.

The Privacy component uses the same structure as other pages with GlobalStyles, Header, and consistent JSX patterns.


18-51: LGTM! Privacy policy introduction is comprehensive.

The opening section properly identifies the website, explains data collection practices, and sets clear expectations for users.


52-64: LGTM! Analytics section demonstrates privacy-focused approach.

The use of Plausible Analytics is a good choice for privacy-conscious data collection, and the explanation is clear and transparent.


65-111: LGTM! Data handling sections are comprehensive.

The sections on cookies, backup management, user contact, social media interaction, data sharing, and individual rights provide clear information about data practices.


112-148: LGTM! Contact information and component structure are appropriate.

The contact information appears legitimate for a Swiss-based company, and the component properly closes with the Footer component.


150-150: LGTM! Component export follows standard conventions.

The default export is appropriate for a page component.

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

521-524: LGTM: Footer layout improvement

The change from justify-content: flex-end to justify-content: space-between with align-items: center and gap: 2rem provides better distribution of footer elements and improved spacing.


532-541: LGTM: Clean footer link styling

The new footer link styles provide consistent typography, smooth transitions, and a clear visual hierarchy with the bottom border.


612-612: LGTM: Hero content positioning adjustment

The increased vertical translation values (-130% for desktop and -300% for mobile) appear to be intentional repositioning to accommodate layout changes.

Also applies to: 620-620


977-977: LGTM: Improved text wrapping

Increasing the max-width from 20ch to 22ch provides better text wrapping for longer content.


1014-1017: LGTM: Consistent link styling

The link styling is consistent with the footer links, maintaining visual coherence across the page.


1145-1145: LGTM: Content width optimization

The increase from 110ch to 115ch provides more comfortable reading width for legal text.


1304-1305: LGTM: Mobile footer layout improvement

The column layout with gap provides better vertical spacing on mobile devices.


2521-2597: LGTM: Comprehensive privacy page styling

The privacy page styles are well-structured with proper responsive design, typography hierarchy, and consistent spacing. The commented-out blurred background effect is preserved for future use.

src/pages/WaitList.jsx (3)

66-66: LGTM: Clear campaign messaging

The updated heading clearly communicates the new $10,000 prize pool and soft launch campaign branding.


129-142: Link Verified: Campaign Terms URL Is Accessible
The campaign terms link returns an HTTP 200 response, confirming it’s reachable. The legal disclaimer and eligibility details are correctly presented.


69-81: LGTM: Improved user engagement copy and verified external link

The external campaign blog link returns HTTP 200 and clearly describes the “PillarX Soft Launch: Join & Unlock Exclusive Rewards” campaign. No further changes required.

@cloudflare-workers-and-pages
Copy link

Deploying x with  Cloudflare Pages  Cloudflare Pages

Latest commit: 489618f
Status: ✅  Deploy successful!
Preview URL: https://0197ac65.x-e62.pages.dev
Branch Preview URL: https://chore-landing-page-copy-upda.x-e62.pages.dev

View logs

@ashutoshamazix ashutoshamazix requested review from IAmKio and RanaBug July 2, 2025 09:20
@IAmKio IAmKio merged commit d960773 into staging Jul 2, 2025
6 checks passed
@ashutoshamazix ashutoshamazix deleted the chore/landing-page-copy-update branch July 2, 2025 11:38
@coderabbitai coderabbitai bot mentioned this pull request Oct 2, 2025
3 tasks
@coderabbitai coderabbitai bot mentioned this pull request Oct 23, 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