Why design systems need SASS - The Real Reasons

The Big Idea

What if you could change your entire website's look by editing just one line of code?

The Scenario

Imagine you are building a website with many pages, each needing consistent colors, fonts, and spacing. You write plain CSS for every style, copying and pasting the same values everywhere.

The Problem

When you want to change a color or font, you must find and update every place manually. This is slow, easy to miss spots, and causes inconsistent styles across pages.

The Solution

SASS lets you create variables for colors, fonts, and sizes. Change a variable once, and all styles using it update automatically. It also helps organize styles with reusable pieces.

Before vs After

✗ Before

body { color: #333333; }
h1 { color: #333333; }

✓ After

$text-color: #333333;
body { color: $text-color; }
h1 { color: $text-color; }

What It Enables

SASS makes design systems easy to maintain and update, ensuring consistent style across a whole website with minimal effort.

Real Life Example

A company website with dozens of pages can quickly update its brand color by changing one SASS variable, instantly refreshing the entire site's look.

Key Takeaways

Manual CSS is repetitive and error-prone for design systems.

SASS variables and features simplify managing consistent styles.

Design systems become easier to update and maintain with SASS.

Practice

1. Why do design systems benefit from using SASS?

easy

A. Because SASS allows reuse of styles with variables and mixins

B. Because SASS automatically creates images for design systems

C. Because SASS replaces HTML in design systems

D. Because SASS is a programming language for backend servers

Solution

1. Step 1: Understand SASS features

   SASS provides variables, mixins, and extends to reuse styles easily.

2. Step 2: Connect features to design systems

   Design systems need consistent styles and easy updates, which SASS helps with.

3. Final Answer:

   Because SASS allows reuse of styles with variables and mixins -> Option A

4. Quick Check:

   Reuse and consistency = A [OK]

Hint: Think about style reuse and consistency in design systems [OK]

Common Mistakes:

• Confusing SASS with image or backend tools
• Thinking SASS replaces HTML
• Ignoring the role of variables and mixins

2. Which of the following is the correct way to declare a variable in SASS?

easy

A. $primary-color: #3498db;

B. var primary-color = #3498db;

C. primary-color: #3498db;

D. #primary-color = #3498db;

Solution

1. Step 1: Recall SASS variable syntax

   SASS variables start with a dollar sign ($) followed by the name and value.

2. Step 2: Check each option

   Only $primary-color: #3498db; uses the correct syntax: $primary-color: #3498db;.

3. Final Answer:

   $primary-color: #3498db; -> Option A

4. Quick Check:

   SASS variables start with $ = A [OK]

Hint: Remember SASS variables always start with $ [OK]

Common Mistakes:

• Using JavaScript or CSS variable syntax
• Omitting the $ sign
• Using incorrect assignment symbols

3. Given the SASS code:

$base-color: #333;
@mixin button-style {
  background-color: $base-color;
  border-radius: 0.5rem;
}
.button {
  @include button-style;
  color: white;
}

What will be the background color of the .button class in the compiled CSS?

medium

A. transparent

B. white

C. #333

D. 0.5rem

Solution

1. Step 1: Understand the mixin usage

   The mixin button-style sets background-color to $base-color, which is #333.

2. Step 2: Check the included styles in .button

   The .button class includes the mixin, so its background color is #333.

3. Final Answer:

   #333 -> Option C

4. Quick Check:

   Mixin sets background-color = #333 [OK]

Hint: Look where variables are used inside mixins [OK]

Common Mistakes:

• Confusing text color with background color
• Ignoring mixin inclusion
• Thinking border-radius affects color

4. Identify the error in this SASS code snippet used in a design system:

$font-size: 1.2rem
.title {
  font-size: $font-size;
}

medium

A. Incorrect variable name syntax

B. Mixin not included

C. Wrong property name font-size

D. Missing semicolon after variable declaration

Solution

1. Step 1: Check variable declaration syntax

   SASS variables must end with a semicolon (;). The code misses it after $font-size: 1.2rem.

2. Step 2: Verify other parts

   Variable name and property are correct; no mixin is needed here.

3. Final Answer:

   Missing semicolon after variable declaration -> Option D

4. Quick Check:

   Semicolon missing = B [OK]

Hint: Always end SASS variable lines with a semicolon [OK]

Common Mistakes:

• Forgetting semicolons after variables
• Confusing variable syntax with CSS
• Assuming mixins are always required

5. In a large design system, how does using SASS variables and mixins help when the primary brand color changes?

hard

A. You need to rewrite all mixins to reflect the new color

B. You only update the color in one place, and all styles update automatically

C. SASS automatically detects brand changes without code updates

D. You must manually change the color in every CSS file

Solution

1. Step 1: Understand variable role in design systems

   SASS variables store values like colors in one place for easy updates.

2. Step 2: Apply to brand color change scenario

   Changing the variable updates all styles using it, avoiding manual edits everywhere.

3. Final Answer:

   You only update the color in one place, and all styles update automatically -> Option B

4. Quick Check:

   Single source update = D [OK]

Hint: Change variables once to update all related styles [OK]

Common Mistakes:

• Thinking manual changes are needed everywhere
• Believing SASS auto-detects brand changes
• Assuming mixins must be rewritten