Skip to content
This repository was archived by the owner on Jun 7, 2026. It is now read-only.

fix: improve products grid layout responsiveness#394

Open
toadkicker wants to merge 2 commits into
mainfrom
worktree-fix-github-docs-layout
Open

fix: improve products grid layout responsiveness#394
toadkicker wants to merge 2 commits into
mainfrom
worktree-fix-github-docs-layout

Conversation

@toadkicker

Copy link
Copy Markdown
Contributor

Summary

  • Replace fixed 3-column grid with auto-fit layout for 5 product cards
  • Grid now adapts 1-3 columns based on viewport width
  • Fixes awkward spacing and overlapping layout issues

Changes

  • repeat(auto-fit, minmax(300px, 1fr)) for flexible columns
  • Added max-width constraint and center alignment
  • Cards flow naturally: 3 on top row, 2 on bottom

Test plan

  • Open docs/index.html in browser
  • Verify 5 product cards display correctly
  • Check responsive behavior at different viewport widths

🤖 Generated with Claude Code

Replace fixed 3-column grid with auto-fit layout that adapts to content.
The 5 product cards now flow naturally without awkward spacing.

Changes:
- Use repeat(auto-fit, minmax(300px, 1fr)) for flexible columns
- Add max-width constraint and center alignment
- Grid now adapts from 1-3 columns based on viewport width

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@greptile-apps

greptile-apps Bot commented May 14, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Replaces the fixed repeat(3, 1fr) grid columns with repeat(auto-fit, minmax(300px, 1fr)) on .products-grid, and adds max-width: 1200px; margin: 0 auto; for a centered, bounded layout.

  • The auto-fit change is correct and achieves the described 1–3 column adaptive layout; at 1200px max-width, 3 columns of ≥300px fit naturally, giving 3+2 for 5 cards.
  • The pre-existing @media (max-width: 768px) override at line 113–115 still forces single-column up to 768px, effectively suppressing the 2-column layout auto-fit would produce in the 620–768px range — worth verifying this is the intended breakpoint behavior.

Confidence Score: 4/5

Safe to merge — the grid change is straightforward and correct; the only open question is whether the 768px breakpoint intentionally suppresses the 2-column layout auto-fit would otherwise show.

The auto-fit grid change works as described and the max-width centering is harmless. The one thing worth a second look is the interaction between the new auto-fit behavior and the pre-existing 768px media query: at tablet widths (620–768px) the grid could show 2 columns but the override holds it to 1, which may or may not match the intended design.

docs/assets/css/index.css — specifically the existing @media (max-width: 768px) block and whether its breakpoint aligns with the new auto-fit column behavior.

Important Files Changed

Filename Overview
docs/assets/css/index.css Replaces fixed repeat(3, 1fr) grid with auto-fit + minmax(300px, 1fr) and adds max-width: 1200px; margin: 0 auto;. The existing @media (max-width: 768px) override at line 113–115 may suppress the 2-column layout auto-fit would otherwise show in the 620–768px range.

Comments Outside Diff (1)

  1. docs/assets/css/index.css, line 113-115 (link)

    P2 Media query may be over-aggressive after auto-fit change

    auto-fit with minmax(300px, 1fr) naturally collapses to 1 column once the viewport is narrower than ~620px (2×300px + 20px gap). But this existing override forces single-column all the way up to 768px, silently preventing the 2-column layout that auto-fit would otherwise produce between ~620–768px. The PR description says "1–3 columns based on viewport width," so the suppressed 2-column range at tablet sizes may be unintentional. If you want the 2-column layout to appear at those widths, the breakpoint here could be lowered to 620px.

    Prompt To Fix With AI
    This is a comment left during a code review.
    Path: docs/assets/css/index.css
    Line: 113-115
    
    Comment:
    **Media query may be over-aggressive after `auto-fit` change**
    
    `auto-fit` with `minmax(300px, 1fr)` naturally collapses to 1 column once the viewport is narrower than ~620px (2×300px + 20px gap). But this existing override forces single-column all the way up to 768px, silently preventing the 2-column layout that `auto-fit` would otherwise produce between ~620–768px. The PR description says "1–3 columns based on viewport width," so the suppressed 2-column range at tablet sizes may be unintentional. If you want the 2-column layout to appear at those widths, the breakpoint here could be lowered to `620px`.
    
    How can I resolve this? If you propose a fix, please make it concise.

    Fix in Claude Code

Fix All in Claude Code

Prompt To Fix All With AI
Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
docs/assets/css/index.css:113-115
**Media query may be over-aggressive after `auto-fit` change**

`auto-fit` with `minmax(300px, 1fr)` naturally collapses to 1 column once the viewport is narrower than ~620px (2×300px + 20px gap). But this existing override forces single-column all the way up to 768px, silently preventing the 2-column layout that `auto-fit` would otherwise produce between ~620–768px. The PR description says "1–3 columns based on viewport width," so the suppressed 2-column range at tablet sizes may be unintentional. If you want the 2-column layout to appear at those widths, the breakpoint here could be lowered to `620px`.

Reviews (1): Last reviewed commit: "fix: improve products grid layout respon..." | Re-trigger Greptile

Changes:
- Remove identity-strip section (redundant with boundary cards)
- 2x2 grid for main products (Protocol, Papillon, Chrysalis, Extension)
- "Work With Us" spans full width as prominent CTA

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@toadkicker toadkicker closed this Jun 4, 2026
@toadkicker toadkicker reopened this Jun 4, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant