Card component patterns in Tailwind - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ rendering

intermediate

What will this Tailwind card component visually display?

Consider this card component code using Tailwind CSS. What will you see rendered in the browser?

Tailwind

<article class="max-w-sm rounded-lg shadow-lg overflow-hidden bg-white dark:bg-gray-800">
  <img class="w-full h-48 object-cover" src="https://via.placeholder.com/400x200" alt="Sample image" />
  <div class="p-4">
    <h2 class="text-xl font-semibold text-gray-900 dark:text-white">Card Title</h2>
    <p class="mt-2 text-gray-600 dark:text-gray-300">This is a simple card description.</p>
    <button class="mt-4 px-4 py-2 bg-blue-600 text-white rounded hover:bg-blue-700 focus:outline-none focus:ring-2 focus:ring-blue-500">Click Me</button>
  </div>
</article>

A A card with a black background and white text but no image or button.

B A card with a red background, no image, and a button that is disabled and gray.

C A white card with rounded corners and shadow, showing an image on top, a title, description, and a blue button below.

D A card with square corners, no shadow, and text only with no button or image.

💡 Hint

Look at the classes for background, shadow, and button styling.

The card uses white background with dark mode support, rounded corners, shadow, an image on top, text content, and a blue button with hover and focus styles.

❓ selector

intermediate

Which Tailwind CSS selector targets the card's button on hover?

Given a card with a button styled using Tailwind CSS, which selector applies styles only when the button is hovered by the mouse?

Tailwind

<button class="mt-4 px-4 py-2 bg-blue-600 text-white rounded hover:bg-blue-700">Click Me</button>

A .hover\:bg-blue-700:hover

B .bg-blue-600:hover

C .hover-bg-blue-700

D .button:hover

💡 Hint

Tailwind uses special syntax for hover states in class names.

Tailwind generates CSS with selectors like .hover\:bg-blue-700:hover to apply styles on hover for that class.

❓ layout

advanced

How to make cards display in a responsive grid with 3 columns on large screens?

You want to show multiple card components in a grid that has 1 column on small screens, 2 columns on medium, and 3 columns on large screens using Tailwind CSS. Which container class achieves this?

Tailwind

<section class="???">
  <!-- multiple card components here -->
</section>

A grid-cols-3 grid gap-4

B flex flex-wrap justify-between

C block md:grid-cols-2 lg:grid-cols-3

D grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 gap-6

💡 Hint

Use Tailwind's grid and responsive column classes.

The class 'grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 gap-6' creates a grid with 1 column by default, 2 on medium screens, and 3 on large screens with spacing.

❓ accessibility

advanced

Which ARIA attribute improves accessibility for a card used as a clickable link?

If a card is clickable and acts like a link, which ARIA attribute should you add to the card container to help screen readers understand its role?

Tailwind

<article class="card" tabindex="0">
  <!-- card content -->
</article>

A role="link"

B aria-pressed="true"

C aria-hidden="true"

D role="button"

💡 Hint

Think about the semantic role that matches a clickable link.

Using role="link" tells assistive technologies that the element behaves like a link, improving accessibility.

🧠 Conceptual

expert

What is the main benefit of using Tailwind's utility classes for card components over traditional CSS files?

Why do many developers prefer Tailwind CSS utility classes when building card components instead of writing separate CSS stylesheets?

A Utility classes automatically generate JavaScript for card animations.

B Utility classes allow faster styling directly in HTML, reducing context switching and improving consistency.

C Utility classes require no HTML changes and only work with inline styles.

D Utility classes prevent any customization of card styles to keep design uniform.

💡 Hint

Think about how utility classes affect workflow and code organization.

Tailwind's utility classes let developers style elements quickly inside HTML, avoiding separate CSS files and making design consistent and maintainable.

Practice

1. What is the main purpose of a card component in web design using Tailwind?

easy

A. To add background music to a website section

B. To create complex animations on a webpage

C. To replace the entire page layout with a single element

D. To group related content like images, text, and buttons in a neat box

Solution

1. Step 1: Understand the role of card components

   Cards are designed to group related content visually, such as images, text, and actions, making information easy to scan.

2. Step 2: Identify the correct purpose

   Options A, B, and C describe unrelated or incorrect uses of cards in web design.

3. Final Answer:

   To group related content like images, text, and buttons in a neat box -> Option D

4. Quick Check:

   Card purpose = Group related content [OK]

Hint: Cards group content visually in boxes [OK]

Common Mistakes:

• Thinking cards are for animations
• Confusing cards with page layout containers
• Assuming cards add multimedia like music

2. Which Tailwind class correctly adds padding inside a card component?

easy

A. p-4

B. m-4

C. text-center

D. bg-gray-200

Solution

1. Step 1: Understand Tailwind padding classes

   The class p-4 adds padding inside an element, creating space between content and edges.

2. Step 2: Differentiate from other classes

   m-4 adds margin outside the element, text-center centers text, and bg-gray-200 sets background color.

3. Final Answer:

   p-4 -> Option A

4. Quick Check:

   Padding inside card = p-4 [OK]

Hint: Padding starts with 'p-', margin with 'm-' [OK]

Common Mistakes:

• Confusing padding (p-) with margin (m-)
• Using text alignment instead of spacing
• Mixing background color with spacing classes

3. What will be the visual effect of this Tailwind card code snippet?

<div class="max-w-sm rounded overflow-hidden shadow-lg p-6">
  <img class="w-full" src="image.jpg" alt="Sample" />
  <div class="pt-4">Card content here</div>
</div>

medium

A. A full-width card with no shadow and no image

B. A card with no padding and square corners

C. A small card with rounded corners, shadow, padding, and a full-width image on top

D. A card with a border but no shadow or padding

Solution

1. Step 1: Analyze the container classes

   max-w-sm limits width to small size, rounded adds rounded corners, shadow-lg adds a large shadow, and p-6 adds padding inside the card.

2. Step 2: Check image and content layout

   w-full on the image makes it full width inside the card, and pt-4 adds top padding to the content below the image.

3. Final Answer:

   A small card with rounded corners, shadow, padding, and a full-width image on top -> Option C

4. Quick Check:

   Rounded + shadow + padding + full image = A small card with rounded corners, shadow, padding, and a full-width image on top [OK]

Hint: Look for rounded, shadow, padding classes for card style [OK]

Common Mistakes:

• Ignoring padding and shadow effects
• Assuming image is not full width
• Confusing max width with full width

4. Identify the error in this Tailwind card snippet:

<div class="rounded shadow p-4">
  <img src="photo.jpg" />
  <button class="bg-blue-500 text-white p-2">Click</button>
</div>

What is missing for accessibility?

medium

A. The div is missing a background color

B. The img tag is missing an alt attribute

C. The button is missing a hover effect class

D. The padding class on the button is incorrect

Solution

1. Step 1: Check image accessibility

   The img tag lacks an alt attribute, which is important for screen readers to describe the image.

2. Step 2: Review other options

   Button hover effects and background colors are style choices, not accessibility requirements. Padding on the button is valid.

3. Final Answer:

   The img tag is missing an alt attribute -> Option B

4. Quick Check:

   Missing alt attribute = accessibility issue [OK]

Hint: Always add alt text to images for accessibility [OK]

Common Mistakes:

• Ignoring missing alt attributes on images
• Confusing style issues with accessibility
• Assuming padding errors cause accessibility problems

5. You want to create a responsive card grid using Tailwind that shows 1 column on small screens and 3 columns on large screens. Which class combination achieves this?

hard

A. grid grid-cols-1 lg:grid-cols-3 gap-6

B. flex flex-col lg:flex-row gap-6

C. block lg:grid-cols-3 gap-6

D. grid-cols-3 grid gap-6 lg:grid-cols-1

Solution

1. Step 1: Understand responsive grid classes

   grid-cols-1 sets 1 column by default (small screens), and lg:grid-cols-3 changes to 3 columns on large screens. gap-6 adds spacing between grid items.

2. Step 2: Evaluate other options

   flex flex-col lg:flex-row gap-6 uses flex layout, which can work but does not define columns explicitly. block lg:grid-cols-3 gap-6 uses block which disables grid. grid-cols-3 grid gap-6 lg:grid-cols-1 reverses column counts incorrectly.

3. Final Answer:

   grid grid-cols-1 lg:grid-cols-3 gap-6 -> Option A

4. Quick Check:

   Responsive grid columns = grid grid-cols-1 lg:grid-cols-3 gap-6 [OK]

Hint: Use grid-cols-1 and lg:grid-cols-3 for responsive columns [OK]

Common Mistakes:

• Using flex instead of grid for column control
• Setting grid-cols-3 before lg breakpoint
• Forgetting to add grid container class