Configuration file structure in Tailwind - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the Tailwind configuration file export.

Tailwind

[1] theme: {}, plugins: [] }

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

Aexport default

Bmodule.exports =

Cexport =

Dmodule.exports = {

Attempts:

3 left

💡 Hint

Common Mistakes

Using ES module export syntax like 'export default' instead of CommonJS.

Missing the curly braces around the config object.

The Tailwind config file exports an object using module.exports = { ... } syntax.

2fill in blank

medium

Complete the code to add a custom color named 'brand' in the theme colors.

Tailwind

module.exports = { theme: { colors: { brand: '[1]' } }, plugins: [] }

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

Ared

B#ff0000

Cblue

Dgreen

Attempts:

3 left

💡 Hint

Common Mistakes

Using color names instead of hex codes for custom colors.

Forgetting to put the color value inside quotes.

Custom colors in Tailwind config are defined with hex color codes like '#ff0000'.

3fill in blank

hard

Fix the error in the Tailwind config to correctly extend the theme with new spacing.

Tailwind

module.exports = { theme: { extend: { spacing: { [1]: '72px' } } }, plugins: [] }

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

Apx72

B72

C18

D'72'

Attempts:

3 left

💡 Hint

Common Mistakes

Using the pixel value as the key instead of a number.

Putting the key in quotes which makes it a string.

Spacing keys are numbers or strings without quotes; '18' means 18 units, not '72'.

4fill in blank

hard

Fill both blanks to add a custom font family named 'heading' with fallback fonts.

Tailwind

module.exports = { theme: { extend: { fontFamily: { heading: [[1], [2]] } } }, plugins: [] }

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

A'Poppins'

B'sans-serif'

C'Arial'

D'serif'

Attempts:

3 left

💡 Hint

Common Mistakes

Not using quotes around font names.

Using only one font without fallback.

Custom fonts are strings in an array; first is the font name, second is fallback like 'sans-serif'.

5fill in blank

hard

Fill both blanks to add a plugin and enable dark mode in the config.

Tailwind

module.exports = { darkMode: '[1]', theme: { extend: {} }, plugins: [require('[2]')] }

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

Amedia

Bclass

C@tailwindcss/forms

D@tailwindcss/typography

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'media' for darkMode when 'class' is expected.

Forgetting to require the plugin by its exact name.

Dark mode is often enabled with 'class'; plugins are required by name like '@tailwindcss/forms'.

Practice

1. What is the main purpose of the content array in the Tailwind configuration file?

easy

A. To tell Tailwind which files to scan for class names

B. To define custom colors and fonts

C. To set the default font size for the project

D. To list plugins used by Tailwind

Solution

1. Step 1: Understand the role of content

   The content array lists files where Tailwind looks for class names to generate styles.

2. Step 2: Differentiate from other config parts

   Colors and fonts are set under theme.extend, not content.

3. Final Answer:

   To tell Tailwind which files to scan for class names -> Option A

4. Quick Check:

   content = files to scan [OK]

Hint: Remember: content = files Tailwind scans for classes [OK]

Common Mistakes:

• Confusing content with theme.extend
• Thinking content sets colors or fonts
• Assuming content lists plugins

2. Which of the following is the correct way to extend the color palette in tailwind.config.js?

easy

A. "colors: { extend: { primary: '#123456' } }"

B. "theme: { colors: { primary: '#123456' } }"

C. "extend: { theme: { colors: { primary: '#123456' } } }"

D. "theme: { extend: { colors: { primary: '#123456' } } }"

Solution

1. Step 1: Identify correct nesting for extending theme

   To add or change colors without overwriting defaults, use theme.extend.colors.

2. Step 2: Check each option's structure

   "theme: { extend: { colors: { primary: '#123456' } } }" correctly nests colors inside extend inside theme.

3. Final Answer:

   "theme: { extend: { colors: { primary: '#123456' } } }" -> Option D

4. Quick Check:

   Extend colors inside theme.extend [OK]

Hint: Use theme.extend to add colors, not theme alone [OK]

Common Mistakes:

• Putting colors directly under theme (overwrites defaults)
• Misplacing extend outside theme
• Wrong nesting order

3. Given this tailwind.config.js snippet, what will be the background color class for the custom color?

module.exports = {
  theme: {
    extend: {
      colors: {
        brand: '#1a202c'
      }
    }
  }
}

medium

A. bg-custom-brand

B. background-brand

C. bg-brand

D. brand-bg

Solution

1. Step 1: Understand Tailwind color class naming

   Custom colors added under colors get classes like bg-[colorName] for backgrounds.

2. Step 2: Match color name to class

   The color name is brand, so background class is bg-brand.

3. Final Answer:

   bg-brand -> Option C

4. Quick Check:

   Custom color 'brand' -> class 'bg-brand' [OK]

Hint: Custom colors use bg-[name] for backgrounds [OK]

Common Mistakes:

• Using wrong prefix like background- or brand-bg
• Adding extra words like custom
• Confusing text color with background color classes

4. Identify the error in this Tailwind config snippet:

module.exports = {
  content: ['./src/**/*.{html,js}'],
  theme: {
    colors: {
      primary: '#ff0000'
    },
    extend: {
      fontFamily: {
        sans: ['Arial', 'sans-serif']
      }
    }
  }
}

medium

A. content array syntax is incorrect

B. Colors should be inside extend, not directly under theme

C. fontFamily should not be inside extend

D. Missing comma after colors object

Solution

1. Step 1: Check placement of colors in config

   Directly placing colors under theme overwrites default colors, usually we extend them inside theme.extend.

2. Step 2: Verify other parts

   Content array syntax is correct, fontFamily can be extended inside extend, commas are properly placed.

3. Final Answer:

   Colors should be inside extend, not directly under theme -> Option B

4. Quick Check:

   Extend colors to avoid overwriting defaults [OK]

Hint: Put colors inside theme.extend to keep defaults [OK]

Common Mistakes:

• Placing colors directly under theme overwrites defaults
• Thinking content syntax is wrong
• Misplacing fontFamily outside extend

5. You want to add a new font family called heading and a custom color accent without removing Tailwind's defaults. Which config structure correctly achieves this?

hard

A. module.exports = {
theme: {
extend: {
fontFamily: { heading: ['Georgia', 'serif'] },
colors: { accent: '#ff6600' }
}
}
}

B. module.exports = {
extend: {
theme: {
fontFamily: { heading: ['Georgia', 'serif'] },
colors: { accent: '#ff6600' }
}
}
}

C. module.exports = {
theme: {
fontFamily: { heading: ['Georgia', 'serif'] },
colors: { accent: '#ff6600' }
}
}

D. module.exports = {
content: ['./src/**/*.{html,js}'],
theme: {
fontFamily: { heading: ['Georgia', 'serif'] },
extend: { colors: { accent: '#ff6600' } }
}
}

Solution

1. Step 1: Understand how to add without removing defaults

   To add fonts and colors without removing defaults, place them inside theme.extend.

2. Step 2: Check each option's structure

   module.exports = {
     theme: {
       extend: {
         fontFamily: { heading: ['Georgia', 'serif'] },
         colors: { accent: '#ff6600' }
       }
     }
   }

   correctly puts both fontFamily and colors inside extend under theme.

3. Final Answer:

   module.exports = { theme: { extend: { fontFamily: { heading: ['Georgia', 'serif'] }, colors: { accent: '#ff6600' } } } } -> Option A

4. Quick Check:

   Use theme.extend for adding fonts and colors [OK]

Hint: Always add new styles inside theme.extend to keep defaults [OK]

Common Mistakes:

• Adding new styles directly under theme (overwrites defaults)
• Misplacing extend outside theme
• Splitting fontFamily and colors incorrectly