Tailwind CSS integration in Astro - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add Tailwind CSS to your Astro project by installing the correct package.

Astro

npm install [1]

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

Atailwindcss

Btailwind-astro

C@astrojs/tailwind

Dastrocss

Attempts:

3 left

💡 Hint

Common Mistakes

Installing only 'tailwindcss' without the Astro-specific integration.

Using unofficial or misspelled package names.

The official way to integrate Tailwind CSS with Astro is to install the @astrojs/tailwind integration package. This handles the setup including Tailwind CSS itself.

2fill in blank

medium

Complete the code to create the Tailwind config file using the CLI command.

Astro

npx tailwindcss init [1]

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

A-p

B--postcss

Ccreate

D-c

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting the PostCSS flag and only creating tailwind.config.

Using invalid flags like '--config' or 'create'.

The command npx tailwindcss init -p creates both the tailwind.config.mjs and postcss.config.cjs files, which are required for Tailwind in Astro projects.

3fill in blank

hard

Fix the error in the Tailwind config file by completing the content paths array correctly.

Astro

export default {
  content: [[1]],
  theme: {
    extend: {},
  },
  plugins: [],
}

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

A'./public/**/*.{astro,html,js,jsx,ts,tsx}'

B'./node_modules/**/*.{astro,html,js,jsx,ts,tsx}'

C'./dist/**/*.{astro,html,js,jsx,ts,tsx}'

D'./src/**/*.{astro,html,js,jsx,ts,tsx}'

Attempts:

3 left

💡 Hint

Common Mistakes

Including folders like node_modules or dist which are not source files.

Missing file extensions in the glob pattern.

The content array should include the source files where Tailwind classes are used. Usually, this is the src folder with extensions like astro, html, js, jsx, ts, and tsx.

4fill in blank

hard

Complete the astro.config.mjs code to add the Tailwind integration.

Astro

import [1] from "[2]";

  integrations: [[1]()],

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

Atailwindcss

B@astrojs/tailwind

Ctailwind

Dastro-tailwind

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'tailwindcss' instead of the Astro integration package.

Incorrect variable name or package path.

Import the Tailwind integration conventionally as tailwind from "@astrojs/tailwind", then add tailwind() to the integrations array in astro.config.mjs.

5fill in blank

hard

Fill all three blanks to configure Tailwind in Astro's main CSS file with directives for base, components, and utilities.

Astro

@tailwind [1];
@tailwind [2];
@tailwind [3];

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

Abase

Bcomponents

Cutilities

Dstyles

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing the order of directives.

Using incorrect directive names like 'styles'.

Tailwind CSS requires three directives in your main CSS file: @tailwind base;, @tailwind components;, and @tailwind utilities; to include all parts of the framework.

Practice

1. What is the main purpose of integrating Tailwind CSS in an Astro project?

easy

A. To quickly style components using utility classes

B. To add JavaScript functionality to Astro components

C. To manage backend API routes

D. To optimize image loading in Astro

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: Connect Tailwind with Astro

   Integrating Tailwind in Astro allows using these utility classes directly in Astro components for fast styling.

3. Final Answer:

   To quickly style components using utility classes -> Option A

4. Quick Check:

   Tailwind CSS = Fast styling [OK]

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

Common Mistakes:

• Confusing Tailwind with JavaScript frameworks
• Thinking Tailwind manages backend or images
• Assuming Tailwind adds functionality beyond CSS

2. Which of the following is the correct way to include Tailwind CSS directives in your Astro project's CSS file?

easy

A. @tailwind base; @tailwind components; @tailwind utilities;

B. import tailwind from 'tailwindcss';

C. tailwind { base, components, utilities }

D. base components utilities

Solution

1. Step 1: Recall Tailwind CSS setup

   Tailwind requires adding its directives in a CSS file using @tailwind base, components, and utilities.

2. Step 2: Identify correct syntax

   The correct syntax uses semicolons and the @tailwind keyword for each section.

3. Final Answer:

   @tailwind base; @tailwind components; @tailwind utilities; -> Option A

4. Quick Check:

   Tailwind directives start with @tailwind [OK]

Hint: Tailwind directives always start with @tailwind [OK]

Common Mistakes:

• Using import statements instead of directives
• Missing semicolons after directives
• Trying to use HTML tags for Tailwind directives

3. Given this Astro component snippet using Tailwind CSS:

<div class="bg-blue-500 text-white p-4 rounded">Hello Astro</div>

What will be the visual result in the browser?

medium

A. A white background box with blue text and no padding

B. A blue background box with white text, padding, and rounded corners

C. Text with no background and default styling

D. A red background box with white text and sharp corners

Solution

1. Step 1: Interpret Tailwind classes

   bg-blue-500 sets a medium blue background, text-white sets white text color, p-4 adds padding, rounded adds rounded corners.

2. Step 2: Visualize the result

   The div will appear as a blue box with white text, some padding inside, and smooth rounded edges.

3. Final Answer:

   A blue background box with white text, padding, and rounded corners -> Option B

4. Quick Check:

   bg-blue-500 + text-white + p-4 + rounded = blue box with white text [OK]

Hint: Match Tailwind classes to colors and spacing visually [OK]

Common Mistakes:

• Mixing background and text colors
• Ignoring padding or rounded corners
• Assuming default styles override Tailwind

4. You added Tailwind CSS to your Astro project but the styles are not applying. Which of these is the most likely cause?

medium

A. You wrote Tailwind directives inside an HTML file instead of CSS

B. You used invalid Tailwind class names in your components

C. You installed Tailwind but did not restart the Astro dev server

D. You forgot to import the CSS file with Tailwind directives in your layout

Solution

1. Step 1: Check Tailwind CSS import

   Tailwind directives must be in a CSS file that is imported in your Astro layout or root component to apply styles.

2. Step 2: Understand impact of missing import

   If the CSS file is not imported, Tailwind styles won't load, so components show unstyled HTML.

3. Final Answer:

   You forgot to import the CSS file with Tailwind directives in your layout -> Option D

4. Quick Check:

   Missing CSS import = no Tailwind styles [OK]

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

Common Mistakes:

• Assuming Tailwind works without importing CSS
• Restarting server without fixing import
• Writing directives in wrong file types

5. You want to make a responsive Astro component using Tailwind CSS that shows a red background on small screens and green on medium and larger screens. Which class combination achieves this?

hard

A. bg-red-500 lg:bg-green-500

B. bg-green-500 sm:bg-red-500

C. bg-red-500 md:bg-green-500

D. bg-green-500 md:bg-red-500

Solution

1. Step 1: Understand Tailwind responsive prefixes

   In Tailwind, unprefixed classes apply to all screen sizes. Prefixes like md: apply styles at medium screen sizes and above.

2. Step 2: Apply classes for desired behavior

   bg-red-500 sets red background by default (small screens). md:bg-green-500 overrides background to green on medium and larger screens.

3. Final Answer:

   bg-red-500 md:bg-green-500 -> Option C

4. Quick Check:

   Default red + md prefix green = responsive colors [OK]

Hint: Use unprefixed for base, md: for medium+ screens [OK]

Common Mistakes:

• Reversing screen size prefixes
• Using sm: instead of md: for medium screens
• Applying green as default instead of red