layer5io / layer5io/layer5

fix(ui): uneven heights and layout overflow in testimonial cards on `/pricing`

Open
#8,045 2 comments 0 reactions 1 assignee View on GitHub

@DRafi2006 is already working on this.

Since Sep 12, 2026.

framework/gatsby help wanted kind/bug
Dominant language
JavaScript
Stars
1.1k
Forks
1.6k
Avg merge
2d 10h
Merged PRs (30d)
18

Description

Description

On the Pricing page (/pricing) under the "Hear what other users have to say..." review carousel, the testimonial cards exhibit noticeable visual and responsive layout defects:

  1. Unequal Card Heights Across Carousel Slides:
    Individual testimonial cards vary drastically in height depending on quote length (e.g., ~550px for longer quotes vs. ~380px for shorter quotes). Because slides do not stretch to uniform heights, shorter cards leave large, unsightly gaps of empty space underneath them.

  2. Asymmetrical / Off-Center Text Padding on Type-Two Cards:
    On type-two cards (with the centered circular avatar at the top), .type-two-quote-base has padding: 60px 30px 50px 100px;. This disproportionate 100px left padding vs 30px right padding on viewports > 768px severely squeezes the quote into a narrow, right-skewed column that is visibly misaligned with the centered avatar.

  3. Massive Decorative Quotation Mark Overflow (type-three):
    In type-three cards, the decorative quotation mark glyph (.type-three-quote-qmark) is styled with font-size: 280pt (~373px) positioned at top: 140px. Because .type-three-quote lacks overflow: hidden;, this giant glyph bleeds out of the bottom corner of cards with shorter text onto the dark page background.


Screenshot / Visual Evidence

https://github.com/user-attachments/assets/5e765240-382b-4c9b-9b6b-913043f95494


Steps to Reproduce
  1. Open https://layer5.io/pricing (or run gatsby develop locally and visit http://localhost:8000/pricing).
  2. Toggle to Dark Mode.
  3. Scroll down to the "Hear what other users have to say..." section.
  4. Resize the browser to a tablet/foldable width (e.g., 853px or 800px – 1024px).
  5. Compare the heights of side-by-side cards (e.g., Mrittika Ganguli vs. Maximiliano Churichi) and observe:
    • The jagged, uneven bottom alignment.
    • The heavy 100px left indentation on Maximiliano's card.

Expected Behavior
  • All testimonial cards within the active carousel view should stretch to equal heights (height: 100%) so the bottom borders and author metadata align consistently.
  • Padding inside type-two cards should be balanced horizontally (e.g., padding: 60px 30px 40px 30px) so text remains centered under the avatar across all screen sizes.
  • Decorative quotation marks should stay contained within card boundaries without spilling onto the page background (overflow: hidden).

Affected Files & Code References
  • src/reusecore/Blockquote/Blockquote-image/blockquote-image.style.js:

    • Lines 186–193 (.type-two-quote .type-two-quote-base):
      padding: 60px 30px 50px 100px; /* Asymmetric 100px left vs 30px right */
      
    • Lines 235–241 (.type-three-quote):
      Missing overflow: hidden; causing the 280pt font-size glyph from line 279 to overflow.
    • Lines 17–20 (section.bq-section):
      Fixed padding: 30px; margin-bottom: 60px; causing excessive inner margin when multiple slides render at mid-screen widths.
  • src/sections/Pricing/review-slider.js:

    • Lines 72–76 & 79–86:
      Slick slider container needs .slick-track { display: flex; } and .slick-slide > div { height: 100%; } to ensure cards stretch to uniform height.

Suggested Fix
  1. In blockquote-image.style.js:
    • Balance the padding on .type-two-quote .type-two-quote-base:
      padding: 60px 30px 40px 30px;
      
    • Add overflow: hidden; to .type-three-quote.
    • Set .bq-quote and .type-one-wrapper to height: 100%; display: flex; flex-direction: column; so cards expand to fill slide height.
  2. In review-slider.js:
    • Add flex stretch rules to .slick-track and .slick-slide so all rendered cards in the row share the height of the tallest card.

Contributor Labels
  • area/ui
  • component/pricing
  • good first issue
  • kind/bug

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.