41.1 Config in CSS
Config in CSS is part of the Tailwind CSS 4.3 workflow. Learn what the underlying CSS property or layout rule does first, then use the utility class to apply that rule consistently in markup.
Step by step
- Identify the CSS behavior behind Config in CSS.
- Build a very small HTML example before placing it inside a large component.
- Apply the Tailwind utilities and inspect the result at multiple viewport widths.
- Add interaction, dark mode, RTL, or accessibility states when the component needs them.
- Refactor repeated markup into a reusable component only after the visual rule is understood.
10 practical examples
- Apply Config in CSS to a course website and explain the decision you made.
- Apply Config in CSS to a online store and explain the decision you made.
- Apply Config in CSS to a banking app and explain the decision you made.
- Apply Config in CSS to a school portal and explain the decision you made.
- Apply Config in CSS to a clinic booking system and explain the decision you made.
- Apply Config in CSS to a dashboard and explain the decision you made.
- Apply Config in CSS to a restaurant site and explain the decision you made.
- Apply Config in CSS to a mobile app and explain the decision you made.
- Apply Config in CSS to a creator site and explain the decision you made.
- Apply Config in CSS to a business landing page and explain the decision you made.
Hands-on example
<div class="flex flex-wrap items-center gap-4 rounded-xl border bg-white p-6 shadow-sm">
<span class="font-semibold text-slate-900">Config in CSS</span>
</div>Expected output
A working responsive example demonstrating Config in CSS, with no page-wide overflow and clear behavior across breakpoints.
Practice exercise
Create a fresh example for Config in CSS using a different product, screen, component, or content set. Explain what changed and why.
41.2 Extending Theme
Extending Theme is part of the Tailwind CSS 4.3 workflow. Learn what the underlying CSS property or layout rule does first, then use the utility class to apply that rule consistently in markup.
Step by step
- Identify the CSS behavior behind Extending Theme.
- Build a very small HTML example before placing it inside a large component.
- Apply the Tailwind utilities and inspect the result at multiple viewport widths.
- Add interaction, dark mode, RTL, or accessibility states when the component needs them.
- Refactor repeated markup into a reusable component only after the visual rule is understood.
10 practical examples
- Apply Extending Theme to a course website and explain the decision you made.
- Apply Extending Theme to a online store and explain the decision you made.
- Apply Extending Theme to a banking app and explain the decision you made.
- Apply Extending Theme to a school portal and explain the decision you made.
- Apply Extending Theme to a clinic booking system and explain the decision you made.
- Apply Extending Theme to a dashboard and explain the decision you made.
- Apply Extending Theme to a restaurant site and explain the decision you made.
- Apply Extending Theme to a mobile app and explain the decision you made.
- Apply Extending Theme to a creator site and explain the decision you made.
- Apply Extending Theme to a business landing page and explain the decision you made.
Hands-on example
<div class="flex flex-wrap items-center gap-4 rounded-xl border bg-white p-6 shadow-sm">
<span class="font-semibold text-slate-900">Extending Theme</span>
</div>Expected output
A working responsive example demonstrating Extending Theme, with no page-wide overflow and clear behavior across breakpoints.
Practice exercise
Create a fresh example for Extending Theme using a different product, screen, component, or content set. Explain what changed and why.
41.3 Custom Utilities
Custom Utilities is part of the Tailwind CSS 4.3 workflow. Learn what the underlying CSS property or layout rule does first, then use the utility class to apply that rule consistently in markup.
Step by step
- Identify the CSS behavior behind Custom Utilities.
- Build a very small HTML example before placing it inside a large component.
- Apply the Tailwind utilities and inspect the result at multiple viewport widths.
- Add interaction, dark mode, RTL, or accessibility states when the component needs them.
- Refactor repeated markup into a reusable component only after the visual rule is understood.
10 practical examples
- Apply Custom Utilities to a course website and explain the decision you made.
- Apply Custom Utilities to a online store and explain the decision you made.
- Apply Custom Utilities to a banking app and explain the decision you made.
- Apply Custom Utilities to a school portal and explain the decision you made.
- Apply Custom Utilities to a clinic booking system and explain the decision you made.
- Apply Custom Utilities to a dashboard and explain the decision you made.
- Apply Custom Utilities to a restaurant site and explain the decision you made.
- Apply Custom Utilities to a mobile app and explain the decision you made.
- Apply Custom Utilities to a creator site and explain the decision you made.
- Apply Custom Utilities to a business landing page and explain the decision you made.
Hands-on example
<div class="flex flex-wrap items-center gap-4 rounded-xl border bg-white p-6 shadow-sm">
<span class="font-semibold text-slate-900">Custom Utilities</span>
</div>Expected output
A working responsive example demonstrating Custom Utilities, with no page-wide overflow and clear behavior across breakpoints.
Practice exercise
Create a fresh example for Custom Utilities using a different product, screen, component, or content set. Explain what changed and why.
41.4 Custom Variants
Custom Variants is part of the Tailwind CSS 4.3 workflow. Learn what the underlying CSS property or layout rule does first, then use the utility class to apply that rule consistently in markup.
Step by step
- Identify the CSS behavior behind Custom Variants.
- Build a very small HTML example before placing it inside a large component.
- Apply the Tailwind utilities and inspect the result at multiple viewport widths.
- Add interaction, dark mode, RTL, or accessibility states when the component needs them.
- Refactor repeated markup into a reusable component only after the visual rule is understood.
10 practical examples
- Apply Custom Variants to a course website and explain the decision you made.
- Apply Custom Variants to a online store and explain the decision you made.
- Apply Custom Variants to a banking app and explain the decision you made.
- Apply Custom Variants to a school portal and explain the decision you made.
- Apply Custom Variants to a clinic booking system and explain the decision you made.
- Apply Custom Variants to a dashboard and explain the decision you made.
- Apply Custom Variants to a restaurant site and explain the decision you made.
- Apply Custom Variants to a mobile app and explain the decision you made.
- Apply Custom Variants to a creator site and explain the decision you made.
- Apply Custom Variants to a business landing page and explain the decision you made.
Hands-on example
<div class="flex flex-wrap items-center gap-4 rounded-xl border bg-white p-6 shadow-sm">
<span class="font-semibold text-slate-900">Custom Variants</span>
</div>Expected output
A working responsive example demonstrating Custom Variants, with no page-wide overflow and clear behavior across breakpoints.
Practice exercise
Create a fresh example for Custom Variants using a different product, screen, component, or content set. Explain what changed and why.
41.5 Source Directives
Source Directives is part of the Tailwind CSS 4.3 workflow. Learn what the underlying CSS property or layout rule does first, then use the utility class to apply that rule consistently in markup.
Step by step
- Identify the CSS behavior behind Source Directives.
- Build a very small HTML example before placing it inside a large component.
- Apply the Tailwind utilities and inspect the result at multiple viewport widths.
- Add interaction, dark mode, RTL, or accessibility states when the component needs them.
- Refactor repeated markup into a reusable component only after the visual rule is understood.
10 practical examples
- Apply Source Directives to a course website and explain the decision you made.
- Apply Source Directives to a online store and explain the decision you made.
- Apply Source Directives to a banking app and explain the decision you made.
- Apply Source Directives to a school portal and explain the decision you made.
- Apply Source Directives to a clinic booking system and explain the decision you made.
- Apply Source Directives to a dashboard and explain the decision you made.
- Apply Source Directives to a restaurant site and explain the decision you made.
- Apply Source Directives to a mobile app and explain the decision you made.
- Apply Source Directives to a creator site and explain the decision you made.
- Apply Source Directives to a business landing page and explain the decision you made.
Hands-on example
<div class="flex flex-wrap items-center gap-4 rounded-xl border bg-white p-6 shadow-sm">
<span class="font-semibold text-slate-900">Source Directives</span>
</div>Expected output
A working responsive example demonstrating Source Directives, with no page-wide overflow and clear behavior across breakpoints.
Practice exercise
Create a fresh example for Source Directives using a different product, screen, component, or content set. Explain what changed and why.
Chapter 41 review — 10 questions and answers
1. What is the main purpose of Config in CSS?
Answer: Config in CSS is part of the Tailwind CSS 4.3 workflow. Learn what the underlying CSS property or layout rule does first, then use the utility class to apply that rule consistently in markup.
2. What is a common mistake with Config in CSS?
Answer: Using Config in CSS as memorized class names without understanding the CSS behavior, responsive context, accessibility, or component structure.
3. What is the main purpose of Extending Theme?
Answer: Extending Theme is part of the Tailwind CSS 4.3 workflow. Learn what the underlying CSS property or layout rule does first, then use the utility class to apply that rule consistently in markup.
4. What is a common mistake with Extending Theme?
Answer: Using Extending Theme as memorized class names without understanding the CSS behavior, responsive context, accessibility, or component structure.
5. What is the main purpose of Custom Utilities?
Answer: Custom Utilities is part of the Tailwind CSS 4.3 workflow. Learn what the underlying CSS property or layout rule does first, then use the utility class to apply that rule consistently in markup.
6. What is a common mistake with Custom Utilities?
Answer: Using Custom Utilities as memorized class names without understanding the CSS behavior, responsive context, accessibility, or component structure.
7. What is the main purpose of Custom Variants?
Answer: Custom Variants is part of the Tailwind CSS 4.3 workflow. Learn what the underlying CSS property or layout rule does first, then use the utility class to apply that rule consistently in markup.
8. What is a common mistake with Custom Variants?
Answer: Using Custom Variants as memorized class names without understanding the CSS behavior, responsive context, accessibility, or component structure.
9. What is the main purpose of Source Directives?
Answer: Source Directives is part of the Tailwind CSS 4.3 workflow. Learn what the underlying CSS property or layout rule does first, then use the utility class to apply that rule consistently in markup.
10. What is a common mistake with Source Directives?
Answer: Using Source Directives as memorized class names without understanding the CSS behavior, responsive context, accessibility, or component structure.