Tailwind CSS integration in NextJS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import Tailwind CSS styles in a Next.js app.

NextJS

import '[1]/globals.css';

Drag options to blanks, or click blank then click option'

Astyles

Btailwind

Cpublic

Dcss

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'tailwind' or 'css' as folder names which do not exist by default.

Trying to import from 'public' which is for static assets.

In Next.js, global styles including Tailwind CSS are usually imported from the styles folder.

2fill in blank

medium

Complete the code to add Tailwind directives in the CSS file.

NextJS

@tailwind base;
@tailwind components;
@tailwind [1];

Drag options to blanks, or click blank then click option'

Astyles

Butilities

Cimports

Dmodules

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'styles' or 'imports' which are not valid Tailwind directives.

Missing the semicolon at the end.

The @tailwind utilities; directive adds Tailwind's utility classes to your CSS.

3fill in blank

hard

Fix the error in the Tailwind config export statement.

NextJS

export default [1] content: ['./app/**/*.{js,ts,jsx,tsx}'], theme: { extend: {} } }

Drag options to blanks, or click blank then click option'

Amodule

Bconfig

Cconst

D{

Attempts:

3 left

💡 Hint

Common Mistakes

Writing 'module' or 'const' after export default which is incorrect syntax.

Omitting the opening curly brace.

The export default statement must be followed by an object literal starting with {.

4fill in blank

hard

Fill both blanks to configure Tailwind to scan the correct folders.

NextJS

content: ['./[1]/**/*.{js,ts,jsx,tsx}', './[2]/**/*.{js,ts,jsx,tsx}']

Drag options to blanks, or click blank then click option'

Aapp

Bpages

Ccomponents

Dpublic

Attempts:

3 left

💡 Hint

Common Mistakes

Including 'public' which is for static files, not code.

Using 'components' which is not scanned by default.

Tailwind scans both the app and pages folders for class names in Next.js projects.

5fill in blank

hard

Fill all three blanks to add Tailwind classes to a Next.js component.

NextJS

export default function Button() {
  return <button className="[1] [2] [3]">Click me</button>;
}

Drag options to blanks, or click blank then click option'

Abg-blue-500

Btext-white

Cp-4

Dborder-2

Attempts:

3 left

💡 Hint

Common Mistakes

Using border classes instead of padding.

Missing text color class.

These classes add a blue background, white text, and padding to the button.

Practice

1. What is the main purpose of integrating Tailwind CSS in a Next.js project?

easy

A. To handle server-side rendering manually

B. To add backend API routes

C. To manage database connections

D. To quickly style components using utility classes

Solution

1. Step 1: Understand Tailwind CSS role

   Tailwind CSS provides utility classes for styling UI elements quickly without writing custom CSS.

2. Step 2: Relate to Next.js integration

   In Next.js, Tailwind is used to style components easily, not for backend or rendering logic.

3. Final Answer:

   To quickly style components using utility classes -> Option D

4. Quick Check:

   Tailwind CSS = Utility-first styling [OK]

Hint: Tailwind is for styling, not backend or rendering [OK]

Common Mistakes:

• Confusing Tailwind with backend or API features
• Thinking Tailwind manages server rendering
• Assuming Tailwind handles database

2. Which file must you import Tailwind's base styles into for a Next.js project?

easy

A. next.config.js

B. tailwind.config.js

C. pages/_app.js or app/layout.js

D. package.json

Solution

1. Step 1: Identify where global styles go in Next.js

   Global CSS imports happen in pages/_app.js for pages router or app/layout.js for app router.

2. Step 2: Understand Tailwind import location

   Tailwind's base styles are imported in these files to apply styles app-wide.

3. Final Answer:

   pages/_app.js or app/layout.js -> Option C

4. Quick Check:

   Global CSS import = _app.js or layout.js [OK]

Hint: Import Tailwind CSS in your main app wrapper file [OK]

Common Mistakes:

• Trying to import styles in tailwind.config.js
• Importing in next.config.js which is config only
• Adding styles in package.json which is metadata

3. Given this Next.js component using Tailwind CSS, what color will the button text be?

export default function Button() {
  return <button className="text-red-500 hover:text-blue-500">Click me</button>;
}

medium

A. Red text that turns blue on hover

B. Blue text that turns red on hover

C. Always blue text

D. Always red text with no hover effect

Solution

1. Step 1: Analyze the Tailwind classes

   The button has text-red-500 which sets text color red initially, and hover:text-blue-500 which changes text color to blue on hover.

2. Step 2: Understand hover behavior

   When the mouse is over the button, the text color changes to blue; otherwise, it stays red.

3. Final Answer:

   Red text that turns blue on hover -> Option A

4. Quick Check:

   text-red-500 + hover:text-blue-500 = red then blue on hover [OK]

Hint: Hover classes override base styles on mouse over [OK]

Common Mistakes:

• Ignoring hover prefix and thinking text is always blue
• Confusing initial and hover colors
• Assuming no color change on hover

4. You added Tailwind CSS to your Next.js app but styles are not applying. What is a likely cause?

medium

A. You forgot to import 'tailwind.css' in your main app file

B. You didn't install React correctly

C. You used invalid JSX syntax in components

D. You didn't restart the Next.js server after installing Tailwind

Solution

1. Step 1: Check Tailwind CSS import

   If Tailwind styles are missing, often the CSS file with Tailwind directives is not imported in _app.js or layout.js.

2. Step 2: Consider other causes

   While restarting server helps, missing import is the primary cause. React install or JSX errors cause different issues.

3. Final Answer:

   You forgot to import 'tailwind.css' in your main app file -> Option A

4. Quick Check:

   Missing Tailwind import = no styles [OK]

Hint: Always import Tailwind CSS file in your main app file [OK]

Common Mistakes:

• Assuming React install affects Tailwind styles
• Ignoring missing CSS import
• Not restarting server but that alone won't fix missing styles

5. You want to create a responsive Next.js component using Tailwind CSS that shows a green background on small screens and blue on medium and larger screens. Which class combination achieves this?

hard

A. "bg-blue-500 md:bg-green-500"

B. "bg-green-500 md:bg-blue-500"

C. "md:bg-green-500 bg-blue-500"

D. "bg-green-500 bg-blue-500 md:bg-green-500"

Solution

1. Step 1: Understand Tailwind responsive prefixes

   Classes without prefix apply to all screen sizes. Prefix md: applies styles at medium screens and above.

2. Step 2: Apply background colors correctly

   To have green on small screens, use bg-green-500. To override with blue on medium+, use md:bg-blue-500.

3. Final Answer:

   "bg-green-500 md:bg-blue-500" -> Option B

4. Quick Check:

   Small = green, Medium+ = blue with md: prefix [OK]

Hint: Use base class for small, md: prefix for medium+ [OK]

Common Mistakes:

• Reversing colors with md prefix
• Using multiple base classes causing conflicts
• Not understanding responsive prefixes