Skip to content

Add Disclaimer#438

Merged
ashutoshamazix merged 3 commits intostagingfrom
chore/lp-disclaimer
Oct 24, 2025
Merged

Add Disclaimer#438
ashutoshamazix merged 3 commits intostagingfrom
chore/lp-disclaimer

Conversation

@ashutoshamazix
Copy link
Collaborator

@ashutoshamazix ashutoshamazix commented Oct 23, 2025

Description

  • Added Disclaimer to the footer of landing pages.

How Has This Been Tested?

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 disclaimer section to the footer and restored the Privacy Policy link.
  • Style

    • Restructured footer to vertical stacking with improved spacing and visual hierarchy.
    • Reorganized social links placement for clearer presentation.
  • Bug Fixes

    • Improved external-link behavior so social links open in a new tab with consistent, safer handling.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 23, 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

Added a disclaimer block to the Footer, restructured link groups into a new links wrapper (preserving the Privacy Policy link), updated social links and anchor rel attributes to include noreferrer, and converted footer layout from horizontal to vertical stacking with new styling blocks.

Changes

Cohort / File(s) Summary
Footer component structure
src/components/LandingPage/Footer/index.jsx
Added footer__disclaimer paragraph; introduced footer__links_wrapper containing footer__links (Privacy Policy restored) and footer__socials; ensured all anchor tags use rel="noreferrer" and target="_blank"
Footer global styles
src/components/LandingPage/GlobalStyles/index.jsx
Changed footer flex layout to column with increased gap; added styles for .footer__disclaimer and .footer__links_wrapper; adjusted disclaimer paragraph styling (font-size, italic, alignment, max-width)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

  • Landing page update #358: Modifies the same Footer component and global footer styles—restructuring footer markup and handling Privacy Policy and social links.

Suggested reviewers

  • RanaBug
  • IAmKio

Poem

🐰 I nibble at markup, tidy each line,
Disclaimer nestled, links now align,
Rel and target set for a hop and a click,
Footer stacked gently, compact and quick. ✨

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)
Check name Status Explanation Resolution
Description Check ⚠️ Warning The pull request description is largely incomplete against the provided template. While the Description section includes a brief statement about adding a disclaimer to the footer, the "How Has This Been Tested?" section contains only a dash with no actual testing information provided, the Screenshots section is empty, and the "Types of changes" checkboxes are all left unchecked. This leaves critical gaps in understanding how the changes were validated and what category of change this represents (feature, bug fix, or breaking change).
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (1 passed)
Check name Status Explanation
Title Check ✅ Passed The title "Add Disclaimer" directly relates to the main change in the pull request, which adds a disclaimer paragraph to the footer of landing pages. The title is concise, clear, and specific enough that a reviewer can understand the primary purpose of the changeset without additional context. It accurately reflects the key modification made to the Footer component and its associated styles.

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
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 (3)
src/components/LandingPage/GlobalStyles/index.jsx (2)

716-726: Consider adding mobile-specific max-width for the disclaimer.

The max-width: 120ch might be too wide for smaller screens. Consider adding a media query to reduce this value on mobile devices for better readability.

Apply this adjustment to improve mobile readability:

 .footer__disclaimer p {
   font-size: 1.2rem;
   font-style: italic;
   text-align: left;
   max-width: 120ch;
 }
+
+@media only screen and (max-width: 767px) {
+  .footer__disclaimer p {
+    max-width: 100%;
+  }
+}

728-733: Consider adding mobile layout adjustments for footer links wrapper.

The space-between justification might not provide optimal UX on smaller screens. Consider adding a media query to stack the links and socials vertically or adjust the layout for mobile devices.

Apply this adjustment for better mobile layout:

 .footer__links_wrapper {
   display: flex;
   justify-content: space-between;
   align-items: center;
   gap: 2rem;
 }
+
+@media only screen and (max-width: 767px) {
+  .footer__links_wrapper {
+    flex-direction: column;
+    align-items: flex-start;
+    gap: 1.5rem;
+  }
+}
src/components/LandingPage/Footer/index.jsx (1)

25-54: Consider adding "noopener" to rel attribute for enhanced security.

While modern browsers implicitly apply noopener behavior to target="_blank" links, it's best practice to explicitly include both noopener and noreferrer for compatibility with older browsers and explicit security posture.

Apply this pattern to all external links:

               <a
                 href="https://x.com/PX_Web3"
                 target="_blank"
-                rel="noreferrer"
+                rel="noopener noreferrer"
               >

Apply the same change to the Telegram and Discord links.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a03b7b7 and cd55e7d.

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

11-19: LGTM! Clear and appropriate disclaimer.

The disclaimer text is well-written, professional, and includes appropriate risk warnings for cryptocurrency-related content.

@github-actions github-actions bot temporarily deployed to Preview (chore/lp-disclaimer) October 23, 2025 13:02 Inactive
@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Oct 23, 2025

Deploying x with  Cloudflare Pages  Cloudflare Pages

Latest commit: 7884e82
Status: ✅  Deploy successful!
Preview URL: https://5dd0c70f.x-e62.pages.dev
Branch Preview URL: https://chore-lp-disclaimer.x-e62.pages.dev

View logs

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 (2)
src/components/LandingPage/Footer/index.jsx (2)

11-19: Consider adding semantic structure to the disclaimer.

The disclaimer content is clear and appropriate. However, for improved accessibility and semantic HTML, consider adding a heading (e.g., <h3> or <h4>) before the paragraph or an aria-label on the wrapper div to help screen readers identify this as a disclaimer section.

Example:

-            <div className="footer__disclaimer">
+            <div className="footer__disclaimer" aria-label="Investment disclaimer">
+              <h4 className="footer__disclaimer-title">Disclaimer</h4>
               <p>
                 The content on this website is for informational purposes only
                 and does not constitute financial or investment advice.
                 Cryptocurrency assets are volatile and carry market risk. Always
                 do your own research and seek professional guidance before
                 making investment decisions.
               </p>
             </div>

30-53: Improve alt text descriptions for better accessibility.

The current alt texts ("x-image", "telegram-image", "discord-image") are generic. More descriptive alternatives would better serve screen reader users.

Apply this diff:

                 <img
                   src="https://cdn.pillarx.app/social-x.svg"
-                  alt="x-image"
+                  alt="Visit our X profile"
                 />
               </a>
               <a
                 href="https://t.me/+WmZpena91_dlNDhk"
                 target="_blank"
                 rel="noreferrer"
               >
                 <img
                   src="https://cdn.pillarx.app/social-telegram.svg"
-                  alt="telegram-image"
+                  alt="Join our Telegram community"
                 />
               </a>
               <a
                 href="https://chat.pillar.fi/"
                 target="_blank"
                 rel="noreferrer"
               >
                 <img
                   src="https://cdn.pillarx.app/social-discord.svg"
-                  alt="discord-image"
+                  alt="Join our Discord server"
                 />
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cd55e7d and 6d1a4f4.

📒 Files selected for processing (1)
  • src/components/LandingPage/Footer/index.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). (3)
  • GitHub Check: build
  • GitHub Check: unit-tests
  • GitHub Check: lint

Comment on lines +25 to +54
<a
href="https://x.com/PX_Web3"
target="_blank"
rel="noreferrer"
>
<img
src="https://cdn.pillarx.app/social-x.svg"
alt="x-image"
/>
</a>
<a
href="https://t.me/+WmZpena91_dlNDhk"
target="_blank"
rel="noreferrer"
>
<img
src="https://cdn.pillarx.app/social-telegram.svg"
alt="telegram-image"
/>
</a>
<a
href="https://chat.pillar.fi/"
target="_blank"
rel="noreferrer"
>
<img
src="https://cdn.pillarx.app/social-discord.svg"
alt="discord-image"
/>
</a>
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Add noopener to rel attribute for security best practice.

While noreferrer implies noopener in modern browsers, explicitly including both attributes ensures maximum compatibility and security when using target="_blank".

Apply this diff:

               <a
                 href="https://x.com/PX_Web3"
                 target="_blank"
-                rel="noreferrer"
+                rel="noopener noreferrer"
               >
                 <img
                   src="https://cdn.pillarx.app/social-x.svg"
                   alt="x-image"
                 />
               </a>
               <a
                 href="https://t.me/+WmZpena91_dlNDhk"
                 target="_blank"
-                rel="noreferrer"
+                rel="noopener noreferrer"
               >
                 <img
                   src="https://cdn.pillarx.app/social-telegram.svg"
                   alt="telegram-image"
                 />
               </a>
               <a
                 href="https://chat.pillar.fi/"
                 target="_blank"
-                rel="noreferrer"
+                rel="noopener noreferrer"
               >
                 <img
                   src="https://cdn.pillarx.app/social-discord.svg"
                   alt="discord-image"
                 />
               </a>
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<a
href="https://x.com/PX_Web3"
target="_blank"
rel="noreferrer"
>
<img
src="https://cdn.pillarx.app/social-x.svg"
alt="x-image"
/>
</a>
<a
href="https://t.me/+WmZpena91_dlNDhk"
target="_blank"
rel="noreferrer"
>
<img
src="https://cdn.pillarx.app/social-telegram.svg"
alt="telegram-image"
/>
</a>
<a
href="https://chat.pillar.fi/"
target="_blank"
rel="noreferrer"
>
<img
src="https://cdn.pillarx.app/social-discord.svg"
alt="discord-image"
/>
</a>
<a
href="https://x.com/PX_Web3"
target="_blank"
rel="noopener noreferrer"
>
<img
src="https://cdn.pillarx.app/social-x.svg"
alt="x-image"
/>
</a>
<a
href="https://t.me/+WmZpena91_dlNDhk"
target="_blank"
rel="noopener noreferrer"
>
<img
src="https://cdn.pillarx.app/social-telegram.svg"
alt="telegram-image"
/>
</a>
<a
href="https://chat.pillar.fi/"
target="_blank"
rel="noopener noreferrer"
>
<img
src="https://cdn.pillarx.app/social-discord.svg"
alt="discord-image"
/>
</a>
🤖 Prompt for AI Agents
In src/components/LandingPage/Footer/index.jsx around lines 25 to 54, the anchor
tags use target="_blank" with rel="noreferrer" only; update each of those anchor
tags to include noopener as well (e.g., rel="noreferrer noopener") to ensure
maximum compatibility and security when opening external links in a new tab.

@ashutoshamazix ashutoshamazix merged commit 06daea5 into staging Oct 24, 2025
6 checks passed
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