Component library patterns (Headless UI) in Tailwind - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Headless UI component?

A Headless UI component provides the logic and accessibility features without any built-in styles. You add your own styles, often with Tailwind CSS, to control how it looks.

beginner

Why use Headless UI components instead of styled components?

Headless UI lets you control the design fully while handling complex behaviors and accessibility. This means you get a flexible, accessible component without style restrictions.

intermediate

How does Headless UI improve accessibility?

It manages keyboard navigation, ARIA roles, and focus control automatically, so users with keyboards or screen readers can use components easily.

beginner

What Tailwind CSS feature pairs well with Headless UI?

Tailwind CSS utility classes pair well because you can style Headless UI components easily and responsively without writing custom CSS.

beginner

Name a common Headless UI component and its purpose.

The <code>Menu</code> component creates accessible dropdown menus that handle keyboard and focus behavior but let you style the menu yourself.

What does a Headless UI component NOT provide?

A Accessibility features

B Component logic

C Keyboard navigation

D Built-in styles

Headless UI components provide logic and accessibility but no built-in styles, so you can style them yourself.

Which Tailwind CSS feature helps style Headless UI components?

A Animations only

B Utility classes

C Grid system only

D Deprecated classes

Tailwind's utility classes let you quickly add styles to Headless UI components without writing custom CSS.

How does Headless UI help users with keyboards?

A By managing focus and keyboard controls

B By adding animations

C By hiding components

D By disabling keyboard navigation

Headless UI manages focus and keyboard controls to make components accessible for keyboard users.

Which of these is a Headless UI component?

A Menu

B Button with styles

C Styled Card

D Image slider with CSS

Menu is a common Headless UI component that provides accessible dropdown logic without styles.

What is the main benefit of using Headless UI?

A Pre-styled components

B No accessibility support

C Full control over styling with accessibility handled

D Only works with React

Headless UI gives you full styling control while handling accessibility and component logic.

Explain what a Headless UI component is and why it is useful in web development.

Think about how it separates look from behavior.

Describe how Tailwind CSS works well with Headless UI components.

Focus on styling flexibility and speed.

Practice

1. What is the main purpose of Headless UI in web development?

easy

A. To create animations for UI elements automatically

B. To offer pre-styled UI components ready to use

C. To replace Tailwind CSS for styling

D. To provide accessible component behavior without styling

Solution

1. Step 1: Understand Headless UI's role

   Headless UI provides the logic and accessibility for components but no styles.

2. Step 2: Compare with styling tools

   Styling is added separately, often with Tailwind CSS, so Headless UI focuses on behavior only.

3. Final Answer:

   To provide accessible component behavior without styling -> Option D

4. Quick Check:

   Headless UI = behavior only [OK]

Hint: Headless UI = logic + accessibility, no styles [OK]

Common Mistakes:

• Thinking Headless UI provides styles
• Confusing Headless UI with Tailwind CSS
• Assuming it creates animations automatically

2. Which of the following is the correct way to import a Headless UI component in a React project?

easy

A. import { Menu } from '@headlessui/react';

B. import Menu from 'headless-ui';

C. import { Menu } from 'tailwindcss';

D. import Menu from '@headlessui/css';

Solution

1. Step 1: Identify the correct package name

   The official Headless UI React package is '@headlessui/react'.

2. Step 2: Use named import for components

   Components like Menu are imported as named imports from '@headlessui/react'.

3. Final Answer:

   import { Menu } from '@headlessui/react'; -> Option A

4. Quick Check:

   Correct import syntax = import { Menu } from '@headlessui/react'; [OK]

Hint: Headless UI React imports use named imports from '@headlessui/react' [OK]

Common Mistakes:

• Using default import instead of named import
• Importing from 'tailwindcss' instead of '@headlessui/react'
• Using wrong package names like 'headless-ui' or '@headlessui/css'

3. Given this React code using Headless UI's Menu component, what will be the visible output when the button is clicked?

import { Menu } from '@headlessui/react';

export default function Example() {
  return (
    
      Options
      
        
          {({ active }) => (
            <a href='#' className={`${active ? 'bg-blue-500 text-white' : 'text-black'}`}>Account</a>
          )}
        
        
          {({ active }) => (
            <a href='#' className={`${active ? 'bg-blue-500 text-white' : 'text-black'}`}>Settings</a>
          )}
        
      
    
  );
}

medium

A. An error because Menu.Items is missing a wrapper element

B. A button labeled 'Options' that toggles a dropdown with 'Account' and 'Settings' links

C. A button labeled 'Options' with no dropdown appearing on click

D. Only a static list of 'Account' and 'Settings' links visible without a button

Solution

1. Step 1: Understand Menu component behavior

   The Menu.Button toggles visibility of Menu.Items as a dropdown.

2. Step 2: Check rendering of Menu.Items and Menu.Item

   Menu.Items contains two Menu.Item links that show with styling on hover (active).

3. Final Answer:

   A button labeled 'Options' that toggles a dropdown with 'Account' and 'Settings' links -> Option B

4. Quick Check:

   Menu.Button toggles dropdown = A button labeled 'Options' that toggles a dropdown with 'Account' and 'Settings' links [OK]

Hint: Menu.Button toggles Menu.Items dropdown visibility [OK]

Common Mistakes:

• Thinking dropdown is always visible
• Assuming Menu.Items needs extra wrapper
• Expecting error due to JSX structure

4. What is the main issue with this Headless UI Disclosure usage in React?

import { Disclosure } from '@headlessui/react';

export default function Example() {
  return (
    <Disclosure>
      <Disclosure.Button>Toggle</Disclosure.Button>
      <div>Hidden content</div>
    </Disclosure>
  );
}

medium

A. The hidden content should be wrapped in Disclosure.Panel for proper behavior

B. Disclosure.Button must be outside Disclosure component

C. The import statement is incorrect

D. Disclosure requires a state hook to work

Solution

1. Step 1: Check Disclosure structure

   Disclosure requires hidden content inside Disclosure.Panel for toggle functionality.

2. Step 2: Identify missing wrapper

   The <div>Hidden content</div> should be replaced with <Disclosure.Panel>Hidden content</Disclosure.Panel>.

3. Final Answer:

   The hidden content should be wrapped in Disclosure.Panel for proper behavior -> Option A

4. Quick Check:

   Disclosure.Panel wraps hidden content [OK]

Hint: Hidden content must be inside Disclosure.Panel [OK]

Common Mistakes:

• Placing hidden content directly without Disclosure.Panel
• Moving Disclosure.Button outside Disclosure
• Incorrect import or missing hooks

5. You want to create a custom dropdown menu using Headless UI's Menu component styled with Tailwind CSS. You want the menu items to close the menu when clicked and highlight on keyboard navigation. Which approach correctly combines Headless UI behavior with Tailwind styling?

hard

A. Use Menu.Button and style it only; menu items are plain HTML links without Headless UI components

B. Use Menu.Items without Menu.Button and add Tailwind hover classes manually

C. Use Menu.Button to toggle, wrap items in Menu.Items, and style Menu.Item using the active state with Tailwind classes

D. Use only Tailwind CSS dropdown utilities without Headless UI components

Solution

1. Step 1: Use Headless UI components for behavior

   Menu.Button toggles menu visibility; Menu.Items contains menu options; Menu.Item handles keyboard navigation and active state.

2. Step 2: Apply Tailwind CSS for styling active states

   Use the active render prop in Menu.Item to conditionally apply Tailwind classes for highlight on keyboard focus or hover.

3. Step 3: Ensure menu closes on item click

   Headless UI automatically closes the menu when a Menu.Item is clicked, preserving accessibility.

4. Final Answer:

   Use Menu.Button to toggle, wrap items in Menu.Items, and style Menu.Item using the active state with Tailwind classes -> Option C

5. Quick Check:

   Headless UI + Tailwind styling = Use Menu.Button to toggle, wrap items in Menu.Items, and style Menu.Item using the active state with Tailwind classes [OK]

Hint: Style Menu.Item active state with Tailwind inside Headless UI Menu [OK]

Common Mistakes:

• Styling only Menu.Button and ignoring Menu.Item active states
• Not using Menu.Item components for menu options
• Trying to build dropdown without Menu.Button