masonry
Masonry layouts stack items of varying heights in columns without distinct rows, filling gaps like a brick wall. Use this skill when designing or optimizing Pinterest-style galleries, portfolios, and discovery-focused platforms with image-heavy content. It covers when to choose masonry over grid or bento layouts, implementation approaches using CSS columns or JavaScript libraries, accessibility considerations, and SEO challenges with infinite scroll.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/masonry && cp -r /tmp/masonry/skills/components/layout/masonry ~/.claude/skills/masonrySKILL.md
# Components: Masonry Layout Guides masonry layout design for content with varying heights. Masonry stacks items in columns without distinct rows; items fill gaps like a brick wall. Best for image galleries, portfolios, and discovery-focused platforms. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## When to Use Masonry | Use masonry when | Use grid when | |------------------|---------------| | **Varying heights** | Equal-height items | | Image-heavy; varied aspect ratios | Products, templates (consistent) | | Gallery, portfolio, showcase | Card grid | | Discovery, browsing; visual-first | Structured browsing | See **grid** for equal-height grid; **card** for card structure. ## Masonry vs Grid vs Bento vs Carousel | Layout | Structure | Best for | |--------|-----------|----------| | **Grid** | Equal rows and columns; uniform items | Products, templates, features | | **Masonry** | Columns; items stack without rows; gaps filled | Pinterest, Behance; varied content | | **Bento** | Intentional sections; predefined sizes | Homepage, dashboard; Apple-style | | **Carousel** | Slides; one/few visible; swipe/click | Testimonials, logos, featured items; see **carousel** | ## Masonry Structure | Element | Purpose | |---------|---------| | **Columns** | 2–4 columns; fluid or fixed | | **Items** | Varying heights; natural aspect ratio | | **Gap** | Consistent horizontal and vertical spacing | | **Order** | Top-to-bottom fill within columns | ## Implementation - **CSS columns**: `column-count`; simple, no JS; but items flow top-to-bottom then next column - **Masonry.js / libraries**: True masonry (left-to-right fill); may need JS - **CSS Grid + `grid-auto-flow: dense`**: Approximate; no JS; see **grid** for dense grid **Note**: Pure masonry can create accessibility challenges (screen reader order); ensure logical DOM order. ## SEO Considerations **Masonry + infinite scroll = content not crawlable.** Masonry galleries often use infinite scroll or lazy load; crawlers cannot emulate scroll or "Load more" clicks, so content beyond the initial view is not discoverable. | If you use | Then | |------------|------| | **Infinite scroll** | Provide paginated component pages with full URLs; implement pushState; see **site-crawlability** for search-friendly infinite scroll | | **Lazy load** | Ensure content exists in HTML or is reachable via crawlable links | | **Pagination** | Prefer for SEO-critical content; crawlers can follow next/prev links | **Reference**: [Google – Infinite scroll search-friendly recommendations](https://developers.google.com/search/blog/2014/02/infinite-scroll-search-friendly) ## Best Practices | Principle | Practice | |-----------|----------| | **Visual-first** | Thumbnails; minimal text | | **Aspect ratio** | Preserve original; avoid forced cropping | | **Lazy load** | Many images; load on scroll | | **Performance** | Masonry can be heavy; consider grid for simpler cases | ## Use Cases | Use case | Format | Page Skill | |----------|--------|------------| | **Showcase / Gallery** | User work; varied sizes | **showcase-page-generator** | | **Portfolio** | Projects; mixed media | — | | **Pinterest-style** | Pins; discovery | — | | **Image-heavy blog** | Blog with varied images | **blog-page-generator** | ## Related Skills - **site-crawlability**: Infinite scroll SEO; paginated component pages; search-friendly implementation - **grid**: Equal-height grid; when masonry is overkill - **carousel**: Carousel for slides/rotation; when masonry is overkill - **card**: Card structure; masonry often uses cards - **showcase-page-generator**: Gallery masonry - **image-optimization**: Lazy load, aspect ratio, LCP
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.