Overriding color palette in Tailwind - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of overriding the color palette in Tailwind CSS?

Overriding the color palette lets you customize the default colors to match your brand or design needs, making your website unique and consistent.

beginner

Where do you define custom colors to override the default palette in Tailwind CSS?

You define custom colors inside the tailwind.config.js file under the theme.extend.colors section.

intermediate

How do you keep the default colors and add new custom colors in Tailwind?

Use theme.extend.colors to add new colors without removing the default palette. This way, you extend instead of replace the colors.

intermediate

What happens if you define colors directly under theme.colors instead of theme.extend.colors?

Defining colors directly under theme.colors replaces the entire default color palette, removing all default colors.

beginner

Show a simple example of overriding the color palette to add a custom blue color named brandBlue.

In tailwind.config.js:

module.exports = {
  theme: {
    extend: {
      colors: {
        brandBlue: '#1E40AF'
      }
    }
  }
}

Where should you add custom colors to keep the default Tailwind colors?

A Inside theme.extend.colors

B Inside theme.colors

C Inside plugins array

D Inside purge array

Adding custom colors inside theme.extend.colors extends the default palette without removing it.

What is the effect of defining colors directly under theme.colors in tailwind.config.js?

A It removes all default colors and replaces them

B It causes an error

C It has no effect

D It extends the default colors

Defining colors directly under theme.colors replaces the entire default palette.

Which file do you edit to override the Tailwind color palette?

A index.html

B package.json

C tailwind.config.js

D styles.css

The tailwind.config.js file is where you customize Tailwind settings including colors.

If you want a custom color named 'brandRed' with hex #FF0000, how do you add it without losing default colors?

A Add brandRed under theme.colors

B Add brandRed in index.html

C Add brandRed in styles.css

D Add brandRed under theme.extend.colors

Adding under theme.extend.colors keeps default colors and adds brandRed.

Why is it important to override colors instead of editing Tailwind source files?

A Because Tailwind source files are read-only

B To keep Tailwind updates easy and avoid losing changes

C Because colors cannot be changed

D To make the website load faster

Overriding colors in config keeps your changes safe during Tailwind updates.

Explain how to add a new custom color to Tailwind CSS without losing the default colors.

Think about extending the theme instead of replacing it.

Describe the difference between defining colors under theme.colors and theme.extend.colors in Tailwind.

One replaces, the other extends.

Practice

1. What is the main purpose of overriding the color palette in Tailwind CSS?

easy

A. To add or change colors to match your brand or design needs

B. To remove all default colors from Tailwind

C. To disable Tailwind's color utilities completely

D. To change the font sizes in Tailwind

Solution

1. Step 1: Understand Tailwind's default colors

   Tailwind provides a default color palette for quick styling.

2. Step 2: Purpose of overriding colors

   Overriding lets you add or change colors to fit your brand or design.

3. Final Answer:

   To add or change colors to match your brand or design needs -> Option A

4. Quick Check:

   Overriding colors = Customize palette [OK]

Hint: Overriding colors means customizing palette, not removing defaults [OK]

Common Mistakes:

• Thinking overriding removes all default colors
• Confusing color palette with font sizes
• Believing overriding disables Tailwind features

2. Which is the correct way to add a custom color named brandBlue without removing default colors in tailwind.config.js?

easy

A. extend: { colors: { brandBlue: '#1DA1F2' } }

B. colors: { brandBlue: '#1DA1F2' }

C. theme: { colors: { brandBlue: '#1DA1F2' } }

D. colors: extend { brandBlue: '#1DA1F2' }

Solution

1. Step 1: Use extend inside theme

   To add colors without removing defaults, use extend inside theme.

2. Step 2: Correct syntax for adding colors

   The correct syntax is extend: { colors: { brandBlue: '#1DA1F2' } }.

3. Final Answer:

   extend: { colors: { brandBlue: '#1DA1F2' } } -> Option A

4. Quick Check:

   Use extend to add colors [OK]

Hint: Always put new colors inside extend.colors to keep defaults [OK]

Common Mistakes:

• Adding colors directly under colors removes defaults
• Wrong object nesting in config
• Syntax errors like missing braces

3. Given this tailwind.config.js snippet, what background color will bg-brandBlue apply?

module.exports = {
  theme: {
    extend: {
      colors: {
        brandBlue: '#1DA1F2'
      }
    }
  }
}

medium

A. A light gray color

B. The default Tailwind blue color

C. A bright blue color #1DA1F2

D. No color, it will cause an error

Solution

1. Step 1: Check the custom color definition

   The config adds brandBlue with hex #1DA1F2.

2. Step 2: Understand class usage

   The class bg-brandBlue uses this custom color as background.

3. Final Answer:

   A bright blue color #1DA1F2 -> Option C

4. Quick Check:

   bg-brandBlue = #1DA1F2 [OK]

Hint: Custom colors apply exactly as defined in config [OK]

Common Mistakes:

• Assuming default blue is used instead
• Thinking it causes an error without import
• Confusing color names with default palette

4. What is wrong with this Tailwind config snippet if you want to add a custom color but keep defaults?

module.exports = {
  theme: {
    colors: {
      brandRed: '#E02424'
    }
  }
}

medium

A. Custom colors must be outside the theme object

B. The color hex code is invalid

C. The config syntax is missing a comma

D. It removes all default colors because it overwrites colors directly

Solution

1. Step 1: Check how colors are added

   Adding colors directly under colors replaces all default colors.

2. Step 2: Correct way to keep defaults

   Use extend: { colors: { brandRed: '#E02424' } } inside theme to add without removing.

3. Final Answer:

   It removes all default colors because it overwrites colors directly -> Option D

4. Quick Check:

   Direct colors overwrite defaults [OK]

Hint: Direct colors overwrite defaults; use extend to add [OK]

Common Mistakes:

• Not using extend and losing default colors
• Thinking hex code is wrong
• Misplacing config keys

5. You want to override the Tailwind color palette to add brandGreen and also change the default blue color to #005f73. Which config snippet correctly does this?

hard

A. theme: { extend: { colors: { brandGreen: '#0a9396' } }, blue: '#005f73' }

B. theme: { extend: { colors: { brandGreen: '#0a9396', blue: '#005f73' } } }

C. theme: { extend: { colors: { brandGreen: '#0a9396' } }, colors: { blue: '#005f73' } }

D. theme: { colors: { brandGreen: '#0a9396', blue: '#005f73' } }

Solution

1. Step 1: Adding new colors

   Use theme.extend.colors to add brandGreen without removing defaults.

2. Step 2: Overriding existing colors

   To change default blue, use extend.colors.blue: '#005f73'; this overrides it while keeping other defaults.

3. Step 3: Correct config

   Place both in extend.colors: { brandGreen: '#0a9396', blue: '#005f73' }.

4. Final Answer:

   theme: { extend: { colors: { brandGreen: '#0a9396', blue: '#005f73' } } } -> Option B

5. Quick Check:

   New + override = extend.colors [OK]

Hint: Use extend.colors for adding new colors and overriding existing ones [OK]

Common Mistakes:

• Defining overrides under theme.colors (loses default palette)
• Overwriting colors without extend losing defaults
• Incorrect nesting of colors object