Bird
Raised Fist0
Tailwindmarkup~10 mins

Tailwind with Next.js - Interactive Code Practice

Choose your learning style10 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to add Tailwind CSS to a Next.js project by importing the CSS file.

Tailwind
import '[1]';

export default function App({ Component, pageProps }) {
  return <Component {...pageProps} />;
}
Drag options to blanks, or click blank then click option'
Amain.css
Btailwind.css
C../styles/globals.css
Dindex.css
Attempts:
3 left
💡 Hint
Common Mistakes
Using a CSS file name that does not exist in the project.
Forgetting to import the CSS file in the _app.js or _app.tsx file.
2fill in blank
medium

Complete the code to create a responsive container using Tailwind CSS in a Next.js component.

Tailwind
<div className="[1]">
  <h1 className="text-2xl font-bold">Welcome to Next.js with Tailwind!</h1>
</div>
Drag options to blanks, or click blank then click option'
Acontainer mx-auto px-4
Bmax-w-full p-2
Cflex justify-center items-center
Dbg-gray-100 rounded-lg
Attempts:
3 left
💡 Hint
Common Mistakes
Using flex classes instead of container for layout.
Missing horizontal margin auto to center the container.
3fill in blank
hard

Fix the error in the Tailwind class usage to make the button have a blue background and light blue text.

Tailwind
<button className="bg-[1]-500 text-[2]-100 px-4 py-2 rounded">
  Click me
</button>
Drag options to blanks, or click blank then click option'
Ablue
Bred
Cgreen
Dyellow
Attempts:
3 left
💡 Hint
Common Mistakes
Using a color that does not match the background and text contrast.
Using colors that are not part of Tailwind's default palette.
4fill in blank
hard

Fill both blanks to create a flex container that centers items vertically and horizontally.

Tailwind
<div className="flex [1] [2] h-screen">
  <p className="text-lg">Centered content</p>
</div>
Drag options to blanks, or click blank then click option'
Ajustify-center
Bitems-start
Citems-center
Djustify-end
Attempts:
3 left
💡 Hint
Common Mistakes
Mixing up justify and items classes.
Using start or end instead of center for alignment.
5fill in blank
hard

Fill all three blanks to create a Next.js page with a responsive header using Tailwind CSS.

Tailwind
export default function Home() {
  return (
    <header className="bg-[1]-600 p-[2]">
      <h1 className="text-[3]-100 text-3xl font-semibold">My Next.js Site</h1>
    </header>
  );
}
Drag options to blanks, or click blank then click option'
Agreen
B6
Cgray
Dblue
Attempts:
3 left
💡 Hint
Common Mistakes
Using colors that do not contrast well.
Using padding values that are too small or too large.

Practice

(1/5)
1. What is the main purpose of using Tailwind CSS in a Next.js project?
easy
A. To write custom JavaScript functions
B. To manage server-side routing
C. To quickly style components using utility classes
D. To handle database connections

Solution

  1. Step 1: Understand Tailwind CSS role

    Tailwind CSS provides utility classes for styling HTML elements quickly without writing custom CSS.
  2. Step 2: Identify Next.js features

    Next.js handles routing and server-side rendering, not styling or database management.
  3. Final Answer:

    To quickly style components using utility classes -> Option C
  4. Quick Check:

    Tailwind CSS = Utility-first styling [OK]
Hint: Tailwind is for styling, not logic or routing [OK]
Common Mistakes:
  • Confusing Tailwind with JavaScript logic
  • Thinking Tailwind manages routing or backend
  • Assuming Tailwind replaces Next.js features
2. Which of the following is the correct way to add Tailwind CSS classes to a Next.js component's div element?
easy
A.
Content
B.
Content
C.
Content
D.
Content

Solution

  1. Step 1: Recall JSX syntax for class names

    In React and Next.js, use className with double quotes for CSS classes.
  2. Step 2: Check each option

    <div className="bg-blue-500 text-white p-4">Content</div> uses correct JSX syntax with double quotes. <div class="bg-blue-500 text-white p-4">Content</div> uses plain HTML class, which is invalid in JSX. <div className={bg-blue-500 text-white p-4}>Content</div> treats the classes as a JavaScript expression without proper quotes. <div className=bg-blue-500 text-white p-4>Content</div> lacks quotes around the class names.
  3. Final Answer:

    <div className="bg-blue-500 text-white p-4">Content</div> -> Option A
  4. Quick Check:

    JSX uses className="..." [OK]
Hint: Use className with double quotes in JSX [OK]
Common Mistakes:
  • Using plain class instead of className in JSX
  • Missing quotes around class names
  • Using invalid JSX syntax for className
3. Given this Next.js component using Tailwind CSS, what will be the background color of the button on a small screen?
export default function Button() {
  return (
    <button className="bg-green-500 sm:bg-red-500 text-white p-3">Click Me</button>
  )
}
medium
A. Green background
B. Red background
C. No background color
D. Blue background

Solution

  1. Step 1: Understand Tailwind responsive prefixes

    The class bg-green-500 applies by default. The sm:bg-red-500 applies only on small screens and above (min-width 640px).
  2. Step 2: Identify screen size effect

    On screens smaller than 640px, only bg-green-500 applies. On small screens and larger, bg-red-500 overrides the background.
  3. Final Answer:

    Green background -> Option A
  4. Quick Check:

    Default class applies below sm breakpoint [OK]
Hint: Responsive classes apply only at or above their breakpoint [OK]
Common Mistakes:
  • Assuming sm: classes apply on all screen sizes
  • Ignoring default class without prefix
  • Confusing breakpoint directions
4. You have this Next.js component code:
export default function Header() {
  return (
    <header className="flex justify-center items-center p-4">
      <h1 className="text-2xl font-bold">Welcome</h1>
    </header>
  )
}

But the header content is not centered vertically. What is the likely cause?
medium
A. Using p-4 breaks flexbox layout
B. Missing min-h-screen or height on header to enable vertical centering
C. Tailwind CSS is not installed
D. Incorrect use of justify-center instead of items-center

Solution

  1. Step 1: Understand flexbox vertical centering

    Flexbox vertical centering with items-center works if the container has height. Without height, vertical centering has no effect.
  2. Step 2: Check header height

    The header has padding but no height or min-height. Adding min-h-screen or a fixed height allows vertical centering.
  3. Final Answer:

    Missing min-h-screen or height on header to enable vertical centering -> Option B
  4. Quick Check:

    Flex vertical center needs container height [OK]
Hint: Flex vertical center needs container height [OK]
Common Mistakes:
  • Thinking justify-center controls vertical alignment
  • Assuming padding sets height
  • Ignoring need for Tailwind installation
5. You want to create a responsive navigation bar in Next.js using Tailwind CSS that stacks vertically on mobile and horizontally on desktop. Which combination of Tailwind classes achieves this?
hard
A.
B.
C.
D.

Solution

  1. Step 1: Understand layout direction classes

    flex-col stacks items vertically; flex-row arranges items horizontally.
  2. Step 2: Apply responsive prefixes

    Using flex flex-col md:flex-row means vertical stacking by default (mobile) and horizontal layout on medium screens and above (desktop).
  3. Step 3: Check other options

    <nav className="grid grid-cols-4 md:grid-cols-1 gap-4 p-4">...</nav> uses grid-cols-4 by default, spreading items horizontally on mobile instead of stacking vertically. <nav className="block md:flex-row gap-4 p-4">...</nav> misses flex class, so md:flex-row won't apply properly. <nav className="flex-row flex md:flex-col gap-4 p-4">...</nav> reverses directions incorrectly.
  4. Final Answer:

    <nav className="flex flex-col md:flex-row gap-4 p-4">...</nav> -> Option D
  5. Quick Check:

    flex-col mobile + md:flex-row desktop = responsive nav [OK]
Hint: Use flex-col mobile, md:flex-row desktop for responsive nav [OK]
Common Mistakes:
  • Forgetting to add base flex class
  • Using wrong order of flex-row and flex-col
  • Confusing grid with flex for simple nav layout
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard