Text wrap fix and removal of header

[ragnep]

Summary by CodeRabbit

• New Features

  • Content display components now support optional text clamping control.

• Style

  • Removed the hero header banner from the home page.
  • Boosted card text clamping moved to the text element and now uses full-width text styling.
  • Improved vertical alignment and reduced top padding in the now-minting section for more consistent layout.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Removed the HeroHeader component and its re-export; added a conditional shouldClamp prop to ContentDisplay (default true) to control text clamping; adjusted BoostedDropCardHome to move line-clamp from the container to the text class; tweaked spacing/vertical alignment in NowMintingSection.

Changes

Cohort / File(s)	Summary
Hero header removal components/home/HomePageContent.tsx, components/home/hero/HeroHeader.tsx, components/home/hero/index.ts	Deleted the HeroHeader component and removed its import/re-export; HomePageContent no longer renders the hero header.
ContentDisplay API components/waves/drops/ContentDisplay.tsx	Added public prop shouldClamp?: boolean (default true); conditionalizes the line-clamp class into inner text span instead of hard-coding it on the container.
Boosted drop card update components/home/boosted/BoostedDropCardHome.tsx	Moved truncation (tw-line-clamp-6) from the container to the textClassName prop and added tw-w-full; reordered class tokens in container.
Now minting layout adjustments components/home/now-minting/NowMintingSection.tsx	Removed md:tw-pt-16 from loading branch and added tw-items-center to skeleton and content grids for vertical centering.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• Boosted wave preview #1727 — Modifies ContentDisplay behavior and consumers; closely related to the shouldClamp API changes.
• Submission carousel ux improvements #1756 — Edits overlapping UI files (BoostedDropCardHome, ContentDisplay, HomePageContent); changes are code-level adjacent.

Suggested reviewers

• simo6529
• prxt6529

Poem

🐰🌿 I nudged the hero off stage tonight,
Gave text a choice to swallow line or bite.
Cards wear their trims, grids stand tall and true,
A rabbit hops — the UI looks anew! 🎨🐇

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ 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 captures the two main changes: removal of the HeroHeader component and text wrapping adjustments in ContentDisplay and related components.

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

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

components/home/now-minting/NowMintingSection.tsx (1)

31-36: Pre-existing bug: Skeleton grid items won't render.

This code has two issues:

1. new Array(4) creates a sparse array with empty slots that .map() skips entirely
2. The spread syntax {...array} spreads as props, not children

This means the loading skeleton for the stats grid renders nothing.

🐛 Proposed fix

               <div className="tw-grid tw-grid-cols-2 tw-gap-4">
-                {...new Array(4).map((_, i) => (
+                {Array.from({ length: 4 }).map((_, i) => (
                   <div key={i} className="tw-space-y-2">
                     <div className="tw-h-4 tw-w-16 tw-animate-pulse tw-rounded tw-bg-iron-800/50" />
                     <div className="tw-h-6 tw-w-24 tw-animate-pulse tw-rounded tw-bg-iron-800/50" />
                   </div>
                 ))}
               </div>

🤖 Fix all issues with AI agents

In `@components/home/boosted/BoostedDropCardHome.tsx`:
- Around line 105-110: ContentDisplay is being passed shouldClamp={false} while
its textClassName includes "tw-line-clamp-6", causing a semantic mismatch;
either remove "tw-line-clamp-6" from the textClassName to fully disable clamping
when shouldClamp is false, or set shouldClamp to true (or rename/extend
shouldClamp) so it also controls the inner text clamp; update the ContentDisplay
usage (the ContentDisplay component call with props previewContent, shouldClamp,
and textClassName) and/or the ContentDisplay implementation so the shouldClamp
prop consistently governs line-clamping for both container and inner text.

In `@components/waves/drops/ContentDisplay.tsx`:
- Around line 23-27: The clamp class currently stored in clampClass is being
added to containerClasses which is the outer flex span and breaks layout; remove
clampClass from containerClasses and instead conditionally apply
"tw-line-clamp-1" to the inner text span's class list (use shouldClamp to
decide). Concretely: stop including clampClass in containerClasses, and update
the span that renders the text (the inner text span element) to include
"tw-line-clamp-1" when shouldClamp is true so only the text is clipped and the
outer flex (containerClasses) remains tw-flex for media thumbnails.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud