Button component patterns in Tailwind - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a primary button in UI design?

A primary button is the main action button on a page. It usually stands out with a strong color to guide users to the most important action.

beginner

How do you create a button with Tailwind CSS that looks disabled?

Use classes like opacity-50 and cursor-not-allowed to show the button is disabled.

beginner

Why use semantic <button> elements instead of <div> for buttons?

Semantic <button> elements are accessible by default. They support keyboard navigation and screen readers, improving usability for all users.

beginner

What Tailwind classes help create a button with a hover effect?

Use classes like hover:bg-blue-700 or hover:text-white to change background or text color when the user hovers over the button.

intermediate

How can you make a button responsive using Tailwind CSS?

Use responsive prefixes like sm:, md:, lg: to adjust padding, font size, or width on different screen sizes.

Which HTML element is best for creating accessible buttons?

A <div>

B <button>

C <span>

D <a>

The

What Tailwind class would you use to make a button's background blue on hover?

A hover:text-blue-500

B text-blue-500

C bg-blue-500

D hover:bg-blue-500

The class hover:bg-blue-500 changes the background color to blue when the user hovers over the button.

How do you visually indicate a disabled button in Tailwind CSS?

A text-red-500

B hover:bg-gray-500

C opacity-50 cursor-not-allowed

D bg-green-500

Using opacity-50 makes the button look faded, and cursor-not-allowed changes the cursor to show it is disabled.

Which Tailwind class helps make a button's text bold?

A font-bold

B text-bold

C font-light

D text-lg

font-bold makes the text inside the button bold.

To make a button wider on medium screens and above, which prefix would you use?

A md:

B sm:

C lg:

D xl:

The md: prefix applies styles starting at medium screen sizes.

Explain how to build an accessible and visually clear button using Tailwind CSS.

Think about accessibility, visual feedback, and states.

Describe how responsive design affects button styling in Tailwind CSS.

Consider how buttons look and behave on phones vs desktops.

Practice

1. Which Tailwind class is best to make a button visually indicate it is clickable?

easy

A. cursor-pointer

B. text-center

C. bg-gray-100

D. p-4

Solution

1. Step 1: Understand cursor styles in Tailwind

   The class cursor-pointer changes the mouse cursor to a hand icon, signaling clickability.

2. Step 2: Compare other classes

   text-center centers text, bg-gray-100 sets background color, and p-4 adds padding, none indicate clickability.

3. Final Answer:

   cursor-pointer -> Option A

4. Quick Check:

   Clickable cursor = cursor-pointer [OK]

Hint: Clickable buttons use cursor-pointer class [OK]

Common Mistakes:

• Confusing padding or color classes with clickability
• Using text alignment classes for button behavior
• Ignoring cursor style for user feedback

2. Which of these is the correct Tailwind syntax to create a blue button with white text and rounded corners?

easy

A. Click me

B. Click me

C. Click me

D. Click me

Solution

1. Step 1: Check Tailwind color and border radius classes

   bg-blue-500 is a valid blue background, text-white sets white text, and rounded adds small rounded corners.

2. Step 2: Identify incorrect syntax in other options

   blue-bg and white-text are not Tailwind classes; bg-blue is incomplete; rounded-full makes fully round shape but text is black, not white.

3. Final Answer:

   <button class='bg-blue-500 text-white rounded'>Click me</button> -> Option C

4. Quick Check:

   Correct Tailwind classes = Click me [OK]

Hint: Use bg-color, text-color, and rounded classes correctly [OK]

Common Mistakes:

• Using non-existent Tailwind class names
• Mixing text colors incorrectly
• Confusing rounded and rounded-full classes

3. What will be the visual effect of this button?

<button class='bg-green-600 hover:bg-green-700 text-white font-bold py-2 px-4 rounded'>Submit</button>

medium

A. Green button that becomes lighter on hover with normal text and square corners

B. Green button that darkens on hover with white bold text and rounded corners

C. Button with no color change on hover and black text

D. Button with red background and white text

Solution

1. Step 1: Analyze background and hover classes

   bg-green-600 sets a green background; hover:bg-green-700 makes it darker green on hover.

2. Step 2: Check text and shape styling

   text-white sets white text, font-bold makes text bold, rounded adds rounded corners.

3. Final Answer:

   Green button that darkens on hover with white bold text and rounded corners -> Option B

4. Quick Check:

   Hover darkens green, white bold text = Green button that darkens on hover with white bold text and rounded corners [OK]

Hint: Hover:bg-darken-color changes button shade on hover [OK]

Common Mistakes:

• Assuming hover makes color lighter instead of darker
• Ignoring font-bold effect
• Confusing rounded with square corners

4. Identify the error in this Tailwind button code:

<button class='bg-red-500 hover:bg-red-600 text-white rounded p-3 disabled:opacity-50 disabled:pointer-events-none' disabled>Delete</button>

medium

A. The hover:bg-red-600 class will not work when disabled

B. The disabled attribute is missing

C. The pointer-events-none class disables all clicks even when enabled

D. The opacity-50 class is applied incorrectly

Solution

1. Step 1: Understand disabled state styling

   The disabled attribute disables the button, so hover styles do not apply when disabled.

2. Step 2: Analyze hover and disabled interaction

   hover:bg-red-600 works only when button is enabled; when disabled, hover has no effect.

3. Final Answer:

   The hover:bg-red-600 class will not work when disabled -> Option A

4. Quick Check:

   Hover ignored when disabled = The hover:bg-red-600 class will not work when disabled [OK]

Hint: Hover styles don't apply on disabled buttons [OK]

Common Mistakes:

• Thinking disabled attribute is missing
• Believing pointer-events-none disables clicks always
• Misunderstanding opacity-50 usage

5. You want a responsive button that is full width on small screens but auto width on medium and larger screens. Which Tailwind class set achieves this?

hard

A. w-full w-auto md:px-6 py-3 bg-indigo-600 text-white rounded

B. w-auto md:w-full px-6 py-3 bg-indigo-600 text-white rounded

C. w-auto px-6 py-3 bg-indigo-600 text-white rounded md:w-auto

D. w-full md:w-auto px-6 py-3 bg-indigo-600 text-white rounded

Solution

1. Step 1: Understand responsive width classes

   w-full makes button full width; md:w-auto overrides width to auto on medium screens and up.

2. Step 2: Check other classes for correctness

   px-6 py-3 add padding, bg-indigo-600 sets background, text-white sets text color, rounded rounds corners.

3. Final Answer:

   w-full md:w-auto px-6 py-3 bg-indigo-600 text-white rounded -> Option D

4. Quick Check:

   Full width small, auto medium+ = w-full md:w-auto px-6 py-3 bg-indigo-600 text-white rounded [OK]

Hint: Use w-full then md:w-auto for responsive widths [OK]

Common Mistakes:

• Reversing width classes order
• Duplicating width classes without breakpoints
• Misplacing responsive prefixes