Custom spacing scale in Tailwind - Browser Rendering Trace

Render Flow - Custom spacing scale

Read tailwind.config.js

↓

Parse theme.extend.spacing

↓

Generate CSS classes for spacing

↓

Apply classes in HTML

↓

Browser calculates box model with new spacing

↓

Render updated layout

Tailwind reads the custom spacing scale from the config file, generates new CSS classes, and applies them to elements, changing their spacing visually.

Render Steps - 3 Steps

Code Added:Add div element with class 'p-7 m-9 bg-blue-200'

Before

[ ] (empty page)

→

After

[__________]
[ Custom ]
[  Box   ]
[__________]

The div appears as a blue box with default size but no spacing applied yet.

🔧 Browser Action:Creates DOM node and applies base styles

Code Sample

A blue box with padding and margin using custom spacing values from the Tailwind config.

Tailwind

<div class="p-7 m-9 bg-blue-200">
  Custom spacing example
</div>

Tailwind

/* tailwind.config.js snippet */
module.exports = {
  theme: {
    extend: {
      spacing: {
        '7': '1.75rem',
        '9': '2.25rem'
      }
    }
  }
}

Render Quiz - 3 Questions

After applying step 2, what visual change do you see inside the box?

A The box gets a border

B The box background color changes

C The text moves inward with extra space around it

D The box moves down the page

Common Confusions - 2 Topics

Why doesn't my custom spacing value work?

You must add the custom spacing in tailwind.config.js under theme.extend.spacing and restart the build process to generate new classes.

💡 Custom spacing classes only appear after Tailwind rebuilds with updated config (see render_steps 1 and 2).

Why is padding inside the box bigger but margin outside doesn't push other elements?

Margin pushes other elements away, but if no siblings or container edges exist, it looks like empty space around the box.

💡 Margin affects space outside the element boundary; padding affects space inside (render_steps 2 vs 3).

Property Reference

Property	Value Applied	Visual Effect	Common Use
p-7	1.75rem	Adds padding inside element	Increase inner spacing
m-9	2.25rem	Adds margin outside element	Increase outer spacing
Default spacing	varies (e.g., 1rem, 0.5rem)	Standard spacing steps	Quick layout adjustments

Concept Snapshot

Custom spacing scale in Tailwind lets you define new spacing sizes. Add values under theme.extend.spacing in tailwind.config.js. Use classes like p-7 or m-9 to apply padding or margin. Padding adds space inside the element; margin adds space outside. Remember to rebuild Tailwind after changing config to see updates.

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