Custom spacing scale in Tailwind - Practice Problems & Coding Challenges

Challenge - 5 Problems

📝 Syntax

intermediate

Correct syntax to add a custom spacing scale in Tailwind CSS

Which option correctly adds a custom spacing value of 72 equal to 18rem in the Tailwind CSS configuration?

Tailwind

module.exports = {
  theme: {
    extend: {
      spacing: {
        // Your custom spacing here
      }
    }
  }
}

A 72: "18rem"

B 72: 18rem

C "72": "18rem"

D "72": 18rem

💡 Hint

Remember that keys in the spacing object should be strings and values should be strings with units.

In Tailwind CSS config, custom spacing keys must be strings and values must be strings with units like 'rem'. Option C uses correct string syntax for both key and value.

🧠 Conceptual

intermediate

Understanding the effect of custom spacing scale

If you add a custom spacing scale "72": "18rem" to your Tailwind config, what will class="p-72" do in your HTML?

A Apply padding of 18rem on all sides

B Apply padding of 72px on all sides

C Apply margin of 18rem on all sides

D Apply padding of 72rem on all sides

💡 Hint

The class p-72 uses the custom spacing value you defined.

The p-72 class applies padding on all sides using the spacing scale key '72'. Since '72' is set to '18rem', padding will be 18rem.

❓ selector

advanced

Custom spacing scale and responsive variants

Given this Tailwind config snippet adding "72": "18rem" to spacing, which class applies a margin of 18rem only on medium screens and larger?

A md:m-72

B margin-md-72

C m-md-72

D m-72

💡 Hint

Tailwind uses prefixes like md: for responsive variants.

The md:m-72 class applies margin 18rem starting at the medium breakpoint. Other options are invalid syntax.

❓ layout

advanced

Using custom spacing scale with Flexbox gap

You added "72": "18rem" to your spacing scale. Which class correctly applies a horizontal gap of 18rem between flex items?

Tailwind

<div class="flex">
  <div>Item 1</div>
  <div>Item 2</div>
</div>

A gap-18rem

B gap-72-x

C gap-x-[18rem]

D gap-x-72

💡 Hint

Tailwind uses gap-x- for horizontal gaps with spacing keys.

The class gap-x-72 applies horizontal gap using the spacing scale key '72' which equals 18rem. Option D uses arbitrary values but is not needed here.

❓ accessibility

expert

Accessibility considerations when using large custom spacing

You added a very large custom spacing scale "128": "32rem" and use p-128 on a container. What is a potential accessibility concern?

A Large padding improves readability for all users without any downside

B Excessive padding may cause content to be pushed off screen on small devices, harming usability

C Screen readers will ignore padding, so no accessibility impact

D Large padding automatically triggers high contrast mode for better accessibility

💡 Hint

Think about how very large spacing affects small screens and user experience.

Using very large padding like 32rem can push content outside the visible area on small screens, making it hard to use. This harms accessibility and responsive design.

Practice

1. What is the main purpose of adding a custom spacing scale in Tailwind CSS?

easy

A. To create new spacing sizes beyond the default ones

B. To change the color palette of the project

C. To add new font families

D. To enable JavaScript animations

Solution

1. Step 1: Understand Tailwind spacing scale

   Tailwind provides default spacing sizes, but sometimes you need sizes not included by default.

2. Step 2: Purpose of custom spacing scale

   Adding a custom spacing scale lets you define new spacing values to use in classes like padding or margin.

3. Final Answer:

   To create new spacing sizes beyond the default ones -> Option A

4. Quick Check:

   Custom spacing scale = new spacing sizes [OK]

Hint: Custom spacing adds new size options beyond defaults [OK]

Common Mistakes:

• Confusing spacing scale with colors or fonts
• Thinking it enables animations
• Assuming it changes existing default sizes

2. Which of the following is the correct way to add a custom spacing value of 72 (18rem) in Tailwind config?

easy

A. "extend: { colors: { 72: '18rem' } }" inside tailwind.config.js

B. "spacing: { 72: '18rem' }" at the root of tailwind.config.js

C. "extend: { spacing: { 72: '18rem' } }" inside tailwind.config.js

D. "extend: { fontSize: { 72: '18rem' } }" inside tailwind.config.js

Solution

1. Step 1: Locate correct config property for spacing

   Custom spacing values go inside the extend.spacing object in tailwind.config.js.

2. Step 2: Check syntax correctness

   "extend: { spacing: { 72: '18rem' } }" inside tailwind.config.js correctly places 72: '18rem' inside extend.spacing. Other options put spacing at root or wrong keys like colors or fontSize.

3. Final Answer:

   "extend: { spacing: { 72: '18rem' } }" inside tailwind.config.js -> Option C

4. Quick Check:

   Custom spacing inside extend.spacing [OK]

Hint: Custom spacing must be inside extend.spacing [OK]

Common Mistakes:

• Placing spacing directly at root instead of extend
• Adding spacing under colors or fontSize
• Using incorrect syntax or missing quotes

3. Given this Tailwind config snippet:

{
  extend: {
    spacing: {
      84: '21rem'
    }
  }
}

What will be the padding size applied by the class p-84 in HTML?

medium

A. 8.4rem padding on all sides

B. No padding applied, class invalid

C. 2.1rem padding on all sides

D. 21rem padding on all sides

Solution

1. Step 1: Understand custom spacing value

   The config defines spacing 84 as '21rem', so class p-84 means padding: 21rem.

2. Step 2: Interpret class effect

   Class p-84 applies padding of 21rem on all sides of the element.

3. Final Answer:

   21rem padding on all sides -> Option D

4. Quick Check:

   p-84 = padding 21rem [OK]

Hint: Class p-84 uses spacing 84 value exactly [OK]

Common Mistakes:

• Confusing 84 with 8.4 or 2.1 rem
• Thinking class is invalid without default spacing
• Assuming padding applies only to one side

4. You added this to your tailwind.config.js:

extend: {
  spacing: {
    100: '25rem'
  }
}

But using m-100 in HTML does not apply margin. What is the likely problem?

medium

A. The spacing value '25rem' is invalid

B. You forgot to restart the build process after config change

C. Class name should be m-10 instead of m-100

D. Tailwind does not support custom spacing values

Solution

1. Step 1: Check if config syntax is correct

   The config syntax is correct; 100: '25rem' inside extend.spacing is valid.

2. Step 2: Understand Tailwind build process

   After changing tailwind.config.js, you must restart the build or dev server to apply changes.

3. Final Answer:

   You forgot to restart the build process after config change -> Option B

4. Quick Check:

   Restart build after config update [OK]

Hint: Restart build after config edits to apply changes [OK]

Common Mistakes:

• Assuming spacing value format is wrong
• Using wrong class name syntax
• Thinking Tailwind disallows custom spacing

5. You want to add two custom spacing sizes: 72 (18rem) and 84 (21rem). How should you write the extend.spacing part in tailwind.config.js to use both sizes correctly?

hard

A. { extend: { spacing: { 72: '18rem', 84: '21rem' } } }

B. { extend: { spacing: { '72': 18, '84': 21 } } }

C. { spacing: { 72: '18rem', 84: '21rem' } }

D. { extend: { spacing: [72, 84] } }

Solution

1. Step 1: Correct syntax for multiple custom spacings

   Custom spacing values go inside extend.spacing as key-value pairs with keys as numbers and values as strings with units.

2. Step 2: Analyze incorrect options

   Placing spacing at the root overrides defaults. Using string keys or numeric values without units is invalid. Arrays are not supported for spacing definitions.

3. Final Answer:

   { extend: { spacing: { 72: '18rem', 84: '21rem' } } } -> Option A

4. Quick Check:

   Multiple spacings as key-value pairs in extend.spacing [OK]

Hint: Use object with keys and rem strings inside extend.spacing [OK]

Common Mistakes:

• Using numbers without units for spacing values
• Placing spacing outside extend
• Using arrays instead of objects for spacing