Masonry-style grid in Tailwind - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ layout

intermediate

What is the visual effect of this Tailwind CSS grid code?

Consider this Tailwind CSS snippet for a grid container:

class="grid grid-cols-3 gap-4 auto-rows-min"

What will the grid layout look like when items have different heights?

A A single column layout with items stacked vertically.

B A 3-column grid where rows adjust their height individually to fit each item, creating a masonry effect.

C A 3-column grid where all rows have the same height, matching the tallest item in each row.

D A 3-column grid with fixed row heights, causing overflow if items are taller.

💡 Hint

Think about how 'auto-rows-min' affects row height in a grid.

The 'auto-rows-min' sets the minimum row height, but all rows in a grid have the same height per row line. So each row's height matches the tallest item in that row, not individual items. This means no masonry effect.

❓ selector

intermediate

Which Tailwind utility enables a masonry-style column layout?

You want to create a masonry-style grid with columns that flow vertically and items stacked unevenly. Which Tailwind CSS utility class helps achieve this?

A grid-cols-3

B grid-flow-row

C flex flex-wrap

D columns-3

💡 Hint

Masonry layouts often use CSS columns, not grid columns.

The 'columns-3' utility creates CSS columns that flow vertically, stacking items in a masonry style. 'grid-cols-3' creates grid columns but does not produce masonry.

🧠 Conceptual

advanced

Why does a CSS Grid not create a true masonry layout by default?

Given a CSS Grid container with multiple columns and items of varying heights, why does it not produce a masonry effect where items stack vertically without gaps?

A Because grid rows are always the same height across the entire row, so items align horizontally.

B Because grid columns automatically adjust their width to fit items, preventing masonry.

C Because grid items cannot span multiple rows or columns.

D Because grid containers do not support gaps between items.

💡 Hint

Think about how grid rows behave in height.

CSS Grid defines rows that span the full width, so all items in a row share the same height. This prevents items from stacking unevenly vertically like masonry.

❓ rendering

advanced

What is the rendered output of this Tailwind CSS snippet?

Given this HTML and Tailwind CSS:

<div class="columns-2 gap-4">
  <div class="bg-blue-300 p-4">Short</div>
  <div class="bg-green-300 p-4 h-32">Tall</div>
  <div class="bg-red-300 p-4">Medium height</div>
</div>

How will the items be arranged visually?

A A 2-column grid with rows aligned horizontally, all rows same height as tallest item in that row.

B Two vertical columns with items stacked top to bottom in each column, uneven heights creating a masonry effect.

C Items stacked vertically in a single column with gaps between them.

D Items arranged horizontally in a single row with equal widths.

💡 Hint

CSS columns flow vertically, stacking items unevenly.

The 'columns-2' class creates two CSS columns. Items flow vertically filling the first column top to bottom, then the second column, producing a masonry effect with uneven heights.

❓ accessibility

expert

How to ensure keyboard accessibility in a masonry-style grid using CSS columns?

When using CSS columns (e.g., Tailwind's 'columns-3') for a masonry layout, what is a key accessibility concern for keyboard users?

A Keyboard users may navigate items out of visual order because DOM order flows top to bottom, left to right visually but columns flow top to bottom per column.

B CSS columns automatically reorder DOM elements to match visual order, so no concern.

C Keyboard users cannot tab through items inside CSS columns.

D Screen readers ignore items inside CSS columns.

💡 Hint

Think about how DOM order and visual order differ in CSS columns.

CSS columns flow content vertically per column, but DOM order is linear top to bottom. Keyboard navigation follows DOM order, which may not match visual reading order, confusing users.

Practice

1. What does the Tailwind class columns-3 do in a masonry-style grid layout?

easy

A. It sets the font size to 3 rem.

B. It creates 3 rows with equal height.

C. It adds 3 pixels of margin between grid items.

D. It splits the container into 3 vertical columns for items to flow into.

Solution

1. Step 1: Understand the columns-3 class

   This class divides the container into 3 vertical columns, allowing items to flow vertically like bricks in a wall.

2. Step 2: Differentiate from rows and spacing

   It does not create rows or set spacing or font size; those are controlled by other classes like gap- or text-.

3. Final Answer:

   It splits the container into 3 vertical columns for items to flow into. -> Option D

4. Quick Check:

   columns-3 means 3 vertical columns [OK]

Hint: Remember columns-3 means 3 vertical columns, not rows [OK]

Common Mistakes:

• Confusing columns with rows
• Thinking it sets spacing or font size
• Assuming it creates fixed-height rows

2. Which Tailwind class correctly adds horizontal and vertical gaps between items in a masonry grid?

easy

A. space-x-4

B. columns-4

C. gap-4

D. m-4

Solution

1. Step 1: Identify gap class usage

   The gap-4 class adds consistent horizontal and vertical spacing between grid items.

2. Step 2: Differentiate from other spacing classes

   space-x-4 adds only horizontal spacing between flex items, m-4 adds margin around an element, and columns-4 sets column count, not spacing.

3. Final Answer:

   gap-4 -> Option C

4. Quick Check:

   Use gap-4 for spacing in grids [OK]

Hint: Use gap-4 for both horizontal and vertical spacing [OK]

Common Mistakes:

• Using space-x-4 which only adds horizontal space
• Confusing margin (m-4) with gap
• Using columns-4 to add space instead of columns

3. Given this HTML snippet using Tailwind:

<div class="columns-2 gap-3">
  <div class="bg-blue-300 p-4">Item 1</div>
  <div class="bg-green-300 p-4">Item 2</div>
  <div class="bg-red-300 p-4">Item 3</div>
  <div class="bg-yellow-300 p-4">Item 4</div>
</div>

How will the items be arranged visually?

medium

A. Four horizontal rows with items side by side.

B. Two vertical columns with items flowing top to bottom in each column.

C. A single column with all items stacked vertically.

D. Items arranged in a 2x2 grid with equal height rows.

Solution

1. Step 1: Understand columns-2 effect

   The container is split into 2 vertical columns. Items flow vertically in each column, filling the first column top to bottom, then the second.

2. Step 2: Analyze gap and item styling

   The gap-3 adds spacing between columns and rows. Each item has padding and background color but no fixed height, so heights can vary.

3. Final Answer:

   Two vertical columns with items flowing top to bottom in each column. -> Option B

4. Quick Check:

   columns-2 means 2 vertical columns [OK]

Hint: Columns flow vertically, not horizontally [OK]

Common Mistakes:

• Thinking columns create rows
• Assuming equal height rows automatically
• Ignoring vertical flow in columns

4. You wrote this Tailwind code for a masonry grid:

<div class="columns-3 gap-4">
  <div class="p-4">Item A</div>
  <div class="p-4">Item B</div>
  <div class="p-4">Item C</div>
</div>

But the items appear stacked in one column instead of three. What is the likely cause?

medium

A. The container div is missing a width or max-width, so columns collapse.

B. The gap-4 class is invalid and breaks layout.

C. The items need flex class to arrange in columns.

D. Tailwind does not support columns-3 for masonry layouts.

Solution

1. Step 1: Check container sizing

   Without a set width or max-width, the container may shrink to fit content, causing columns to collapse into one.

2. Step 2: Verify other classes

   gap-4 is valid, and columns-3 works for masonry. Flex is not needed here because columns use CSS multi-column layout.

3. Final Answer:

   The container div is missing a width or max-width, so columns collapse. -> Option A

4. Quick Check:

   Container width needed for columns to show [OK]

Hint: Ensure container has width for columns to display [OK]

Common Mistakes:

• Assuming gap-4 breaks layout
• Adding flex unnecessarily
• Thinking Tailwind lacks columns support

5. You want a responsive masonry grid that shows 1 column on small screens, 2 columns on medium, and 4 columns on large screens using Tailwind. Which class combination achieves this?

hard

A. columns-1 md:columns-2 lg:columns-4 gap-6

B. grid grid-cols-1 md:grid-cols-2 lg:grid-cols-4 gap-6

C. flex flex-wrap gap-6 columns-4

D. columns-4 md:columns-2 lg:columns-1 gap-6

Solution

1. Step 1: Understand responsive columns classes

   Using columns-1 md:columns-2 lg:columns-4 sets the number of columns based on screen size: 1 for small, 2 for medium, 4 for large.

2. Step 2: Confirm gap usage

   gap-6 adds consistent spacing between items across all screen sizes.

3. Step 3: Differentiate from grid and flex

   Grid and flex layouts are different from masonry columns. grid grid-cols-1 md:grid-cols-2 lg:grid-cols-4 gap-6 uses grid, which is not masonry style. flex flex-wrap gap-6 columns-4 mixes flex and columns incorrectly. columns-4 md:columns-2 lg:columns-1 gap-6 reverses column counts.

4. Final Answer:

   columns-1 md:columns-2 lg:columns-4 gap-6 -> Option A

5. Quick Check:

   Responsive columns use breakpoint prefixes [OK]

Hint: Use responsive prefixes with columns-{n} for masonry grids [OK]

Common Mistakes:

• Using grid instead of columns for masonry
• Mixing flex with columns incorrectly
• Reversing responsive column counts