Component-based file organization in SASS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the variables file in Sass.

SASS

@use '[1]';

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

Avariables

Bmixins

Creset

Dbase

Attempts:

3 left

💡 Hint

Common Mistakes

Using @import instead of @use

Including the underscore or file extension in the import path

The @use rule imports the variables file so you can use its variables.

2fill in blank

medium

Complete the code to include the mixins file in your main Sass file.

SASS

@use '[1]';

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

Athemes

Butilities

Ccomponents

Dmixins

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to import a file that does not exist

Using @import instead of @use

The @use rule imports the mixins file so you can use its mixin functions.

3fill in blank

hard

Fix the error in the import statement for the base styles file.

SASS

@use '[1]';

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

Abase

B_base.scss

Cbase.scss

Dstyles/base

Attempts:

3 left

💡 Hint

Common Mistakes

Including the underscore in the import path

Including the file extension

When using @use, omit the underscore and file extension. Just use base.

4fill in blank

hard

Fill both blanks to create a component partial and import it correctly.

SASS

// In components/_button.scss
.button {
  background-color: [1];
}

// In main.scss
@use '[2]';

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

A$primary-color

Bcomponents/button

Ccomponents/buttons

D$secondary-color

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong variable for color

Including underscore or extension in import path

The button component uses the $primary-color variable. The import path is components/button without underscore or extension.

5fill in blank

hard

Fill all three blanks to create a utility partial, use a mixin, and import it properly.

SASS

// In utilities/_spacing.scss
@mixin [1]($size) {
  margin: $size;
}

// In main.scss
@use '[2]';

.container {
  @include utilities.[3](1rem);
}

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

Aspacing

Butilities

Dmixins

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong mixin name

Incorrect import path

Calling mixin without namespace

The mixin is named spacing. The utilities partial is imported with @use 'utilities';. The mixin is called as utilities.spacing.

Practice

1. What is the main benefit of using component-based file organization in Sass?

easy

A. It breaks styles into small, manageable parts for easier maintenance.

B. It automatically compiles Sass to CSS without errors.

C. It reduces the file size of the final CSS output.

D. It allows Sass to run faster in the browser.

Solution

1. Step 1: Understand component-based organization

   This method splits styles into smaller files, each for a component or feature.

2. Step 2: Recognize the benefit

   Smaller files are easier to maintain and reuse, improving project organization.

3. Final Answer:

   It breaks styles into small, manageable parts for easier maintenance. -> Option A

4. Quick Check:

   Component-based organization = easier maintenance [OK]

Hint: Think: smaller files mean easier style management [OK]

Common Mistakes:

• Confusing file size reduction with organization benefits
• Thinking Sass runs in the browser
• Assuming automatic error fixing

2. Which of the following is the correct way to name a Sass partial file for a button component?

easy

A. partial-button.scss

B. button.scss

C. button_partial.scss

D. _button.scss

Solution

1. Step 1: Recall Sass partial naming convention

   Partial files start with an underscore (_) to indicate they are imported, not compiled alone.

2. Step 2: Identify correct naming

   The correct format is underscore + component name + .scss, like _button.scss.

3. Final Answer:

   _button.scss -> Option D

4. Quick Check:

   Partial files start with _ [OK]

Hint: Partial Sass files always start with an underscore _ [OK]

Common Mistakes:

• Omitting the underscore for partial files
• Adding extra words like 'partial' in the filename
• Using hyphens incorrectly

3. Given these Sass files:

@import 'reset';
@import 'header';
@import 'button';

body { font-family: Arial; }
.button { background: blue; }

Which file is likely a partial and not compiled alone?

medium

A. button.scss

B. _header.scss

C. _button.scss

D. reset.scss

Solution

1. Step 1: Identify partial files by underscore

   Files starting with _ are partials, meant to be imported, not compiled alone.

2. Step 2: Check options for underscore prefix

   Both _button.scss and _header.scss have the underscore, so they are partials.

3. Final Answer:

   _button.scss and _header.scss -> Option C

4. Quick Check:

   Partial files start with _ [OK]

Hint: Look for underscore _ prefix to find partial files [OK]

Common Mistakes:

• Choosing files without underscore as partials
• Confusing import statements with file names
• Ignoring naming conventions

4. You have a main Sass file styles.scss importing partials:

@import 'header';
@import 'footer';

body { margin: 0; }

But the styles from _footer.scss are not applied. What is the likely problem?

medium

A. The _footer.scss file is missing the underscore.

B. The _footer.scss file is not saved in the same folder.

C. The import statement should use @use instead of @import.

D. The styles.scss file must be named main.scss.

Solution

1. Step 1: Check import path and file location

   For @import to work, the partial file must be in the same folder or correct path.

2. Step 2: Identify likely cause

   If styles from _footer.scss are missing, it is likely the file is not in the same folder or path is wrong.

3. Final Answer:

   The _footer.scss file is not saved in the same folder. -> Option B

4. Quick Check:

   File location must match import path [OK]

Hint: Check file location matches import path [OK]

Common Mistakes:

• Thinking @import must be replaced by @use always
• Assuming file name of main file matters
• Ignoring file location issues

5. You want to organize your Sass files for a website with header, footer, and buttons. Which structure follows best practices for component-based file organization?

hard

A. styles.scss, _header.scss, _footer.scss, _button.scss, _variables.scss

B. header.scss, footer.scss, button.scss, variables.scss

C. _styles.scss, header.scss, footer.scss, button.scss

D. styles.scss, header.scss, footer.scss, button.scss

Solution

1. Step 1: Identify partial files with underscore

   Partial files start with underscore (_) and hold component styles.

2. Step 2: Confirm main file without underscore

   Main file (styles.scss) imports partials and compiles to CSS.

3. Step 3: Check for variables partial

   Variables often stored in a partial like _variables.scss for reuse.

4. Final Answer:

   styles.scss, _header.scss, _footer.scss, _button.scss, _variables.scss -> Option A

5. Quick Check:

   Main file + underscore partials = best practice [OK]

Hint: Main file no underscore; components start with underscore [OK]

Common Mistakes:

• Naming all files without underscore
• Using underscore for main file
• Missing variables partial