Why reusable patterns matter in Tailwind - See It in Action

Why Reusable Patterns Matter with Tailwind CSS

📖 Scenario: You are building a simple webpage with several buttons that share the same style. Instead of repeating the same Tailwind CSS classes for each button, you will create a reusable pattern using Tailwind's @apply directive inside a CSS file. This helps keep your code clean and easy to maintain.

🎯 Goal: Create a reusable button style using Tailwind CSS's @apply directive and apply it to multiple buttons in your HTML. This will show how reusable patterns save time and reduce errors.

📋 What You'll Learn

Create a CSS class called .btn that uses Tailwind's @apply to add button styles

Add three buttons in HTML that use the btn class

Use Tailwind utility classes for colors, padding, border radius, and hover effect inside @apply

Ensure the buttons are accessible with aria-label attributes

Make the page responsive so buttons stack vertically on small screens

💡 Why This Matters

🌍 Real World

Reusable CSS patterns help developers avoid repeating the same styles many times. This makes websites easier to update and reduces mistakes.

💼 Career

Understanding how to create and use reusable styles with Tailwind CSS is a valuable skill for front-end developers working on scalable and maintainable projects.

1

Create the HTML structure with three buttons

Create an HTML file with a <main> section containing three <button> elements. Each button should have the text Button 1, Button 2, and Button 3 respectively. Add an aria-label attribute to each button with the same text as the button label.

Tailwind

Hint

Use three <button> tags inside <main>. Add aria-label attributes matching the button text.

2

Create a CSS file and define a reusable .btn class

Create a CSS file and define a class called .btn. Inside it, use Tailwind's @apply directive to add these utility classes: bg-blue-600, text-white, py-2, px-4, rounded, and hover:bg-blue-700.

Tailwind

  Button 1
  Button 2
  Button 3


/* Create .btn class with @apply here */

Hint

Use @apply inside .btn to add all the Tailwind classes in one line.

3

Apply the .btn class to all buttons

Add the class btn to each of the three <button> elements in your HTML so they all share the same style.

Tailwind

  Button 1
  Button 2
  Button 3


.btn {
  @apply bg-blue-600 text-white py-2 px-4 rounded hover:bg-blue-700;
}

Hint

Add class="btn" inside each <button> tag.

4

Make buttons stack vertically on small screens

Wrap the buttons inside a <div> with Tailwind classes flex flex-col gap-4 sm:flex-row sm:gap-2 to make them stack vertically on small screens and horizontally on larger screens.

Tailwind

  
    Button 1
    Button 2
    Button 3
  


.btn {
  @apply bg-blue-600 text-white py-2 px-4 rounded hover:bg-blue-700;
}

Hint

Use a <div> with Tailwind classes flex flex-col gap-4 sm:flex-row sm:gap-2 around the buttons.

Practice

1. Why is it important to use reusable patterns in Tailwind CSS?

easy

A. They require writing more CSS code manually.

B. They make the website load slower.

C. They save time and keep the design consistent across the site.

D. They prevent using Tailwind's utility classes.

Solution

1. Step 1: Understand the purpose of reusable patterns

   Reusable patterns help avoid repeating the same styles and keep the design uniform.

2. Step 2: Connect with Tailwind's approach

   Tailwind encourages using utility classes and reusable styles to speed up development and maintain consistency.

3. Final Answer:

   They save time and keep the design consistent across the site. -> Option C

4. Quick Check:

   Reusable patterns = save time + consistency [OK]

Hint: Reusable means save time and keep design same [OK]

Common Mistakes:

• Thinking reusable patterns slow down the site
• Believing reusable means writing more CSS manually
• Confusing reusable with avoiding Tailwind utilities

2. Which Tailwind CSS feature helps you create reusable style classes?

easy

A. The @apply directive

B. The @import rule

C. The @media query

D. The @font-face rule

Solution

1. Step 1: Identify Tailwind's reusable style feature

   The @apply directive lets you combine utility classes into one reusable class.

2. Step 2: Differentiate from other CSS rules

   @import loads CSS files, @media handles responsiveness, and @font-face loads fonts, none create reusable classes.

3. Final Answer:

   The @apply directive -> Option A

4. Quick Check:

   @apply = reusable styles [OK]

Hint: @apply combines utilities into reusable classes [OK]

Common Mistakes:

• Confusing @apply with @import
• Thinking @media creates reusable classes
• Mixing up CSS font rules with Tailwind features

3. What will be the visual result of this Tailwind CSS code?

<button class="btn-primary p-4">Click Me</button>

/* CSS */
.btn-primary {
  @apply bg-blue-600 text-white rounded-lg;
}

medium

A. A button with blue background, white text, rounded corners, and padding

B. A button with default styles and no color or padding

C. A button with red background and no rounded corners

D. A button with blue text and no background color

Solution

1. Step 1: Understand the @apply usage

   The .btn-primary class applies bg-blue-600, text-white, and rounded-lg styles.

2. Step 2: Combine with padding from HTML

   The button also has p-4 class adding padding around the content.

3. Final Answer:

   A button with blue background, white text, rounded corners, and padding -> Option A

4. Quick Check:

   bg-blue + text-white + rounded + p-4 = styled button [OK]

Hint: @apply adds Tailwind utilities to custom classes [OK]

Common Mistakes:

• Ignoring the padding class p-4
• Thinking @apply changes text color to blue
• Assuming no styles apply without inline utilities

4. Identify the error in this Tailwind CSS snippet using @apply:

.btn {
  @apply bg-green-500 text-white p-3 rounded;
}

.btn {
  @apply bg-red-500;
}

medium

A. You cannot use @apply twice on the same class.

B. The second @apply overrides the first, causing inconsistent styles.

C. Tailwind does not support @apply with color classes.

D. The syntax is invalid because @apply must be inside HTML.

Solution

1. Step 1: Analyze multiple @apply on same class

   Applying @apply twice on .btn means the second overrides the first styles.

2. Step 2: Understand style overriding in CSS

   The second @apply bg-red-500 replaces the green background, causing inconsistency.

3. Final Answer:

   The second @apply overrides the first, causing inconsistent styles. -> Option B

4. Quick Check:

   Multiple @apply on same class = override [OK]

Hint: Multiple @apply on one class overrides earlier styles [OK]

Common Mistakes:

• Thinking multiple @apply are not allowed at all
• Believing @apply cannot use color classes
• Confusing CSS syntax rules with HTML placement

5. You want to create a reusable button style with Tailwind that changes color on hover and has consistent padding. Which approach is best?

hard

A. Write all styles inline in HTML without reusable classes.

B. Create separate classes for padding and hover and never combine them.

C. Use only Tailwind's default button classes without customization.

D. Create a custom class using @apply with base styles and add hover utilities in HTML.

Solution

1. Step 1: Understand reusable pattern goals

   Reusable patterns should combine common styles and allow easy customization like hover effects.

2. Step 2: Evaluate options for combining base and hover styles

   Using @apply for base styles and adding hover utilities in HTML keeps code clean and flexible.

3. Step 3: Reject less efficient approaches

   Writing all inline repeats code, default classes may lack needed styles, and splitting padding and hover separately is less maintainable.

4. Final Answer:

   Create a custom class using @apply with base styles and add hover utilities in HTML. -> Option D

5. Quick Check:

   Reusable base + hover in HTML = best practice [OK]

Hint: Use @apply for base, hover in HTML for flexibility [OK]

Common Mistakes:

• Writing all styles inline causing repetition
• Relying only on default classes without customization
• Separating padding and hover styles unnecessarily