Reducing compiled CSS size in SASS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to use a variable for the primary color.

SASS

$primary-color: [1];
.button {
  background-color: $primary-color;
}

Drag options to blanks, or click blank then click option'

Acolor-primary

Bblue

Cprimary

D#3498db

Attempts:

3 left

💡 Hint

Common Mistakes

Using a variable name as a value instead of a color code.

Forgetting the $ sign for variables.

Using a variable like $primary-color with a hex color code helps reuse the color and reduces repetition in compiled CSS.

2fill in blank

medium

Complete the code to nest the styles for the button's hover state.

SASS

.button {
  background-color: #3498db;
  [1] {
    background-color: #2980b9;
  }
}

Drag options to blanks, or click blank then click option'

A&:hover

B:hover

C.hover

D#hover

Attempts:

3 left

💡 Hint

Common Mistakes

Using :hover without & causes invalid nesting.

Using class or id selectors incorrectly.

Using & in Sass refers to the parent selector, so &:hover nests the hover style inside .button.

3fill in blank

hard

Fix the error in the mixin usage to reduce repeated code.

SASS

@mixin button-style($bg-color) {
  background-color: $bg-color;
  color: white;
  padding: 1rem;
}

.primary-button {
  [1] button-style(#3498db);
}

Drag options to blanks, or click blank then click option'

A@include

B@use

C@import

D@extend

Attempts:

3 left

💡 Hint

Common Mistakes

Using @use or @import instead of @include for mixins.

Forgetting the @ symbol.

To use a mixin in Sass, you write @include followed by the mixin name and arguments.

4fill in blank

hard

Fill both blanks to create a map of colors and access a color in the style.

SASS

$colors: (primary: #3498db, secondary: #2ecc71);

.button {
  background-color: map-get($colors, [1]);
  color: [2];
}

Drag options to blanks, or click blank then click option'

Aprimary

B#fff

Csecondary

D#000

Attempts:

3 left

💡 Hint

Common Mistakes

Using quotes around the key in map-get.

Choosing a text color that doesn't contrast well.

map-get($colors, primary) gets the primary color from the map. Using #fff for text color ensures good contrast.

5fill in blank

hard

Fill all three blanks to create a loop that generates margin classes with decreasing sizes.

SASS

@for $i from [1] through [2] {
  .m-#{$i} {
    margin: [3]rem;
  }
}

Drag options to blanks, or click blank then click option'

A5

B1

C$i

D0.5

Attempts:

3 left

💡 Hint

Common Mistakes

Reversing the loop start and end values.

Using a fixed margin instead of the loop variable.

The loop runs from 1 through 5, creating classes .m-1 to .m-5 with margin equal to $i rem units.

Practice

1. Which of the following is the best way to reduce the size of compiled CSS when using Sass?

easy

A. Write very deep nesting of selectors for clarity

B. Use variables and mixins to avoid repeating the same styles

C. Add comments in Sass files to explain styles

D. Use many separate Sass files without combining them

Solution

1. Step 1: Understand Sass features for reuse

   Variables and mixins let you reuse style code instead of repeating it multiple times.

2. Step 2: Compare with other options

   Deep nesting creates many selectors increasing CSS size. Comments do not reduce CSS size. Many files without combining can increase HTTP requests.

3. Final Answer:

   Use variables and mixins to avoid repeating the same styles -> Option B

4. Quick Check:

   Reuse styles = smaller CSS [OK]

Hint: Reuse styles with variables and mixins to shrink CSS [OK]

Common Mistakes:

• Thinking deep nesting reduces CSS size
• Believing comments affect compiled CSS size
• Assuming splitting files always reduces size

2. Which Sass syntax correctly defines a mixin to reduce repeated styles?

easy

A. @function button-style() {\n padding: 1rem;\n border-radius: 0.5rem;\n}

B. @include button-style {\n padding: 1rem;\n border-radius: 0.5rem;\n}

C. @extend button-style {\n padding: 1rem;\n border-radius: 0.5rem;\n}

D. @mixin button-style {\n padding: 1rem;\n border-radius: 0.5rem;\n}

Solution

1. Step 1: Identify mixin syntax

   The correct way to define a mixin is using @mixin name { ... }.

2. Step 2: Differentiate from other directives

   @include is used to use a mixin, not define it. @function defines functions, not mixins. @extend is for inheritance, not mixin definition.

3. Final Answer:

   @mixin button-style { padding: 1rem; border-radius: 0.5rem; } -> Option D

4. Quick Check:

   Define mixin = @mixin [OK]

Hint: Define mixins with @mixin, use with @include [OK]

Common Mistakes:

• Confusing @include with @mixin for definition
• Using @function instead of @mixin
• Trying to define mixin with @extend

3. Given this Sass code, what will be the compiled CSS size impact?

$color: blue;

.button {
  color: $color;
  @include rounded-corners;
}

@mixin rounded-corners {
  border-radius: 0.5rem;
  border: 1px solid $color;
}

medium

A. The CSS will be larger because mixins duplicate code each use

B. The CSS will be smaller because styles are reused via mixin

C. The CSS will have syntax errors and not compile

D. The CSS will ignore the mixin and only use color

Solution

1. Step 1: Understand mixin behavior

   Mixins insert their styles wherever included, duplicating code each time.

2. Step 2: Analyze code impact

   Since @include rounded-corners adds border-radius and border styles inside .button, these styles are duplicated in CSS for each use.

3. Final Answer:

   The CSS will be larger because mixins duplicate code each use -> Option A

4. Quick Check:

   Mixins duplicate styles = larger CSS [OK]

Hint: Mixins duplicate styles; use carefully to reduce size [OK]

Common Mistakes:

• Assuming mixins always reduce CSS size
• Thinking variables reduce duplication inside mixins
• Believing mixins cause syntax errors here

4. This Sass code aims to reduce CSS size but causes unexpected large output. What is the error?

.card {
  .header {
    color: red;
    .title {
      font-weight: bold;
    }
  }
}

medium

A. Mixins are not included for repeated styles

B. Missing semicolons cause syntax errors

C. Nesting is too deep, creating many selectors increasing CSS size

D. Variables are not used for colors

Solution

1. Step 1: Examine nesting depth

   The code nests .header inside .card and .title inside .header, creating selectors like .card .header .title.

2. Step 2: Understand CSS size impact

   Deep nesting creates many combined selectors, increasing compiled CSS size and complexity.

3. Final Answer:

   Nesting is too deep, creating many selectors increasing CSS size -> Option C

4. Quick Check:

   Deep nesting = bigger CSS [OK]

Hint: Keep nesting shallow to avoid large CSS selectors [OK]

Common Mistakes:

• Ignoring nesting depth impact on CSS size
• Looking for syntax errors when none exist
• Thinking variables fix nesting issues

5. You want to reduce compiled CSS size by reusing button styles but avoid duplication from mixins. Which Sass feature helps achieve this best?

hard

A. Use @extend to share styles between selectors

B. Use deeply nested selectors for buttons

C. Use multiple mixins for each style property

D. Write all styles inline without variables

Solution

1. Step 1: Understand @extend behavior

   @extend shares selectors in compiled CSS, avoiding duplication by merging rules.

2. Step 2: Compare with mixins

   Mixins duplicate styles each use, increasing CSS size. @extend reuses styles without duplication.

3. Final Answer:

   Use @extend to share styles between selectors -> Option A

4. Quick Check:

   @extend shares styles, reduces CSS size [OK]

Hint: Use @extend to share styles without duplicating CSS [OK]

Common Mistakes:

• Using mixins expecting no duplication
• Nesting deeply to reuse styles
• Avoiding variables and mixins altogether