Why migration to modern SASS matters - See It in Action

Why migration to modern SASS matters

📖 Scenario: You work for a small web design team. Your team currently uses old SASS syntax in your stylesheets. You want to show why moving to modern SASS syntax is important for better code and easier maintenance.

🎯 Goal: Create a simple SASS stylesheet using modern SASS features like variables, nesting, and mixins to demonstrate the benefits of migrating from old SASS syntax.

📋 What You'll Learn

Use SASS variables to store colors

Use nesting to organize CSS selectors

Create and use a mixin for reusable styles

Write code using modern SASS syntax (no indented syntax)

💡 Why This Matters

🌍 Real World

Modern SASS helps teams write cleaner, more maintainable CSS for websites and apps.

💼 Career

Knowing modern SASS syntax is valuable for front-end developers working on scalable projects.

1

Set up color variables

Create two SASS variables called $primary-color and $secondary-color with values #3498db and #2ecc71 respectively.

SASS

# Your code here

Hint

Use $variable-name: value; syntax to create variables in SASS.

2

Add nested styles for a button

Create a CSS selector .button and nest inside it a selector for &:hover. Set the background color of .button to $primary-color and the background color of &:hover to $secondary-color.

SASS

$primary-color: #3498db;
$secondary-color: #2ecc71;

// Add nested styles for .button and &:hover below

Hint

Use nesting by placing &:hover inside .button block.

3

Create a mixin for rounded corners

Create a mixin called rounded-corners that sets border-radius to 0.5rem. Then include this mixin inside the .button selector.

SASS

$primary-color: #3498db;
$secondary-color: #2ecc71;

.button {
  background-color: $primary-color;
  &:hover {
    background-color: $secondary-color;
  }
}

// Create mixin rounded-corners and include it in .button

Hint

Define mixins with @mixin name { } and use them with @include name;.

4

Add a media query with nesting

Inside the .button selector, add a media query for screen widths less than 600px using @media (max-width: 600px). Inside this media query, set the font-size of .button to 1.2rem.

SASS

$primary-color: #3498db;
$secondary-color: #2ecc71;

@mixin rounded-corners {
  border-radius: 0.5rem;
}

.button {
  background-color: $primary-color;
  @include rounded-corners;
  &:hover {
    background-color: $secondary-color;
  }

  // Add media query for max-width 600px here
}

Hint

Use nesting to place media queries inside selectors for cleaner code.

Practice

1. Why is migrating to modern SASS important for organizing styles?

easy

A. Because modern SASS uses modules to keep code clean and avoid conflicts

B. Because modern SASS removes all CSS features

C. Because modern SASS only works with JavaScript

D. Because modern SASS disables variables

Solution

1. Step 1: Understand the role of modules in modern SASS

   Modern SASS introduces modules to organize styles better and prevent naming conflicts.

2. Step 2: Compare with old SASS style management

   Old SASS mixes all styles globally, causing conflicts and messy code.

3. Final Answer:

   Because modern SASS uses modules to keep code clean and avoid conflicts -> Option A

4. Quick Check:

   Modules improve style organization = D [OK]

Hint: Remember: modules keep styles neat and conflict-free [OK]

Common Mistakes:

• Thinking modern SASS removes CSS features
• Believing modern SASS only works with JavaScript
• Assuming variables are disabled in modern SASS

2. Which of the following is the correct syntax to import a module in modern SASS?

easy

A. @import 'colors';

B. @use 'colors';

C. import colors from 'colors';

D. #use colors;

Solution

1. Step 1: Identify modern SASS import syntax

   Modern SASS uses @use to import modules, replacing @import.

2. Step 2: Check each option

   @use 'colors'; uses @use 'colors'; which is correct. @import 'colors'; uses old syntax. JavaScript-style import and #use are invalid.

3. Final Answer:

   @use 'colors'; -> Option B

4. Quick Check:

   @use is modern import syntax = A [OK]

Hint: Modern SASS imports use '@use', not '@import' [OK]

Common Mistakes:

• Using old '@import' instead of '@use'
• Trying JavaScript import syntax in SASS
• Using invalid symbols like '#use'

3. What will be the output CSS of this modern SASS code?

@use 'sass:color';
$base: #c6538c;
.button {
  background-color: color.scale($base, $lightness: 20%);
}

medium

A. .button { background-color: color.scale(#c6538c, $lightness: 20%); }

B. .button { background-color: #c6538c; }

C. .button { background-color: #d175a3; }

D. Syntax error

Solution

1. Step 1: Understand color.scale function

   The color.scale function lightens the base color by 20% lightness.

2. Step 2: Calculate the resulting color

   Lightening #c6538c by 20% results in #d175a3, which is the new background color.

3. Final Answer:

   .button { background-color: #d175a3; } -> Option C

4. Quick Check:

   color.scale lightens color = C [OK]

Hint: color.scale changes color brightness; expect a lighter shade [OK]

Common Mistakes:

• Expecting original color without change
• Thinking color.scale returns code, not color
• Assuming syntax error due to module use

4. Identify the error in this modern SASS code:

@use 'sass:math';
$size: 10px;
.box {
  width: math.div($size, 2);
  height: math.div($size, 0);
}

medium

A. Division by zero error in math.div($size, 0)

B. Incorrect module name 'sass:math'

C. Missing semicolon after $size declaration

D. math.div does not exist in modern SASS

Solution

1. Step 1: Check math.div usage

   math.div divides numbers safely in modern SASS; dividing by zero is invalid.

2. Step 2: Identify the error

   math.div($size, 0) causes a division by zero error, which is not allowed.

3. Final Answer:

   Division by zero error in math.div($size, 0) -> Option A

4. Quick Check:

   Division by zero causes error = A [OK]

Hint: Check for zero in math.div to avoid errors [OK]

Common Mistakes:

• Thinking 'sass:math' is invalid module
• Ignoring division by zero
• Assuming missing semicolon causes error

5. You want to migrate old SASS code using @import to modern SASS modules. Which approach correctly updates the code to avoid global namespace conflicts?

// Old code
@import 'buttons';
@import 'colors';

.button {
  color: $primary-color;
}

hard

A. @use 'buttons';
@use 'colors';

.button {
color: $primary-color;
}

B. @use 'buttons';
@use 'colors';

.button {
color: colors-primary-color;
}

C. @import 'buttons';
@import 'colors';

.button {
color: colors.$primary-color;
}

D. @use 'buttons';
@use 'colors' as c;

.button {
color: c.$primary-color;
}

Solution

1. Step 1: Understand namespace in modern SASS modules

   Modern SASS requires using namespaces to avoid conflicts, often with aliases.

2. Step 2: Check each option for correct namespace usage

   @use 'buttons'; @use 'colors' as c; .button { color: c.$primary-color; } uses @use 'colors' as c; and accesses variable as c.$primary-color, which is correct. @use 'buttons'; @use 'colors'; .button { color: $primary-color; } misses namespace prefix. @import 'buttons'; @import 'colors'; .button { color: colors.$primary-color; } uses old @import. @use 'buttons'; @use 'colors'; .button { color: colors-primary-color; } uses invalid variable name.

3. Final Answer:

   @use 'buttons'; @use 'colors' as c; .button { color: c.$primary-color; } -> Option D

4. Quick Check:

   Use namespaces with aliases = B [OK]

Hint: Use '@use' with aliases to avoid global conflicts [OK]

Common Mistakes:

• Not using namespace prefix for variables
• Continuing to use '@import' instead of '@use'
• Using invalid variable names without $ or dash