File architecture patterns (7-1 pattern) in SASS - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the 7-1 pattern folder structure

In the 7-1 Sass architecture pattern, how many folders are typically used to organize Sass files (excluding the main entry file)?

A 8 folders

B 1 folder

C 6 folders

D 7 folders

💡 Hint

Think about the name '7-1' and what it represents in folder organization.

The '7-1' pattern uses 7 folders to organize Sass partials and 1 main file that imports them all. This helps keep styles modular and maintainable.

📝 Syntax

intermediate

Correct import syntax in main.scss

Which import statement correctly imports the '_buttons.scss' partial from the 'components' folder in the 7-1 pattern inside 'main.scss'?

SASS

@import 'components/buttons';

A @import 'components/buttons';

B @import 'components/_buttons.scss';

C @import 'buttons';

D @import 'components/buttons.scss';

💡 Hint

Remember Sass partials start with underscore and you omit it and the extension when importing.

In Sass, when importing partials, you omit the underscore and file extension. So '@import 'components/buttons';' correctly imports '_buttons.scss' from the components folder.

❓ layout

advanced

Visualizing the 7-1 folder structure

Which folder below is NOT part of the standard 7 folders in the 7-1 Sass pattern?

A components

B utilities

C widgets

D base

💡 Hint

Recall the common folder names like base, components, utilities, but not 'widgets'.

The standard 7 folders are base, components, layout, pages, themes, abstracts (or utilities), and vendors. 'Widgets' is not a standard folder in the 7-1 pattern.

❓ accessibility

advanced

Accessibility considerations in Sass architecture

How can the 7-1 Sass pattern help improve accessibility in a large project?

A It automatically adds ARIA attributes to HTML elements.

B By separating styles into logical folders, it helps developers maintain consistent focus and state styles for accessibility.

C It enforces color contrast ratios through folder naming.

D It disables animations globally to reduce motion sickness.

💡 Hint

Think about how organization helps developers write better accessible styles.

The 7-1 pattern organizes styles so developers can easily find and maintain focus, hover, and other state styles that improve accessibility. It does not add ARIA or enforce contrast automatically.

🧠 Conceptual

expert

Why use the 7-1 pattern in large Sass projects?

What is the main advantage of using the 7-1 Sass architecture pattern in large projects?

A It improves code maintainability by separating concerns into dedicated folders and files.

B It forces all styles to be written in one file to avoid conflicts.

C It allows Sass to compile faster by limiting the number of files.

D It reduces the final CSS file size by compressing styles automatically.

💡 Hint

Think about how organizing code helps teams work better and avoid confusion.

The 7-1 pattern helps keep styles modular and organized, making it easier to maintain and scale large projects. It does not compress or speed up compilation by itself.

Practice

1. What is the main purpose of the 7-1 pattern in Sass file architecture?

easy

A. To organize Sass files into 7 folders and 1 main file for better maintainability

B. To reduce the size of CSS files by minifying them

C. To automatically generate JavaScript files from Sass

D. To combine all CSS files into one without folders

Solution

1. Step 1: Understand the 7-1 pattern structure

   The 7-1 pattern divides Sass files into 7 folders for different style parts and 1 main file to import them.

2. Step 2: Identify the purpose of this organization

   This structure helps keep styles easy to find, maintain, and scale in projects.

3. Final Answer:

   To organize Sass files into 7 folders and 1 main file for better maintainability -> Option A

4. Quick Check:

   7-1 pattern = organize files [OK]

Hint: Remember 7 folders + 1 main file = organized Sass [OK]

Common Mistakes:

• Thinking it minifies CSS
• Confusing with JavaScript generation
• Assuming it merges CSS without folders

2. Which of the following is the correct way to import a partial named _buttons.scss in the main main.scss file using the 7-1 pattern?

easy

A. @import '_buttons.scss';

B. @import 'buttons/_buttons';

C. @import 'buttons.scss';

D. @import 'buttons';

Solution

1. Step 1: Recall Sass partial import rules

   When importing partials, omit the underscore and file extension in the import statement.

2. Step 2: Apply to _buttons.scss

   So, to import _buttons.scss, write @import 'buttons'; in main.scss.

3. Final Answer:

   @import 'buttons'; -> Option D

4. Quick Check:

   Omit underscore and extension in imports [OK]

Hint: Drop underscore and .scss when importing partials [OK]

Common Mistakes:

• Including underscore in import
• Adding .scss extension
• Using wrong folder path syntax

3. Given this folder structure in the 7-1 pattern:
sass/
├── abstracts/_variables.scss
├── base/_reset.scss
├── components/_buttons.scss
└── main.scss
And main.scss contains:
@import 'abstracts/variables';
@import 'base/reset';
@import 'components/buttons';
What will happen when you compile main.scss?

medium

A. All styles from variables, reset, and buttons partials are combined into one CSS file

B. Only the styles from main.scss are compiled, ignoring partials

C. Compilation fails due to missing underscores in import

D. CSS file is created but empty because partials are not linked

Solution

1. Step 1: Understand import behavior in Sass

   Importing partials in main.scss includes their styles in the compiled CSS output.

2. Step 2: Check import syntax and file names

   Imports correctly reference partials without underscores, so Sass finds and includes them.

3. Final Answer:

   All styles from variables, reset, and buttons partials are combined into one CSS file -> Option A

4. Quick Check:

   Imports combine partials into CSS [OK]

Hint: Imports merge partials into one CSS file [OK]

Common Mistakes:

• Thinking underscores must be in import
• Assuming partials compile separately
• Believing empty CSS if partials imported

4. You have this import in main.scss:
@import 'layout/grid';
But compiling gives an error: File to import not found or unreadable: layout/_grid.scss.
What is the most likely cause?

medium

A. You must include the underscore in the import statement

B. The file _grid.scss is missing inside the layout folder

C. The main.scss file is not saved

D. Sass does not support nested folders in imports

Solution

1. Step 1: Understand Sass import error

   The error means Sass cannot find the partial file _grid.scss inside the layout folder.

2. Step 2: Check file existence

   Most likely, the file is missing or misnamed, causing the import to fail.

3. Final Answer:

   The file _grid.scss is missing inside the layout folder -> Option B

4. Quick Check:

   Missing partial file causes import error [OK]

Hint: Check if partial file exists in folder before importing [OK]

Common Mistakes:

• Including underscore in import path
• Ignoring file save status
• Assuming Sass can't import from folders

5. In the 7-1 pattern, you want to add a new folder themes for different color themes. How should you update your main.scss to include a partial _dark.scss inside themes without breaking the pattern?

hard

A. @import 'dark'; // Import without folder path

B. @import '_dark.scss'; // Import partial directly without folder

C. @import 'themes/dark'; // Add import in main.scss to include theme styles

D. Create a new main file inside themes and import it separately

Solution

1. Step 1: Follow 7-1 pattern folder structure

   Adding a new folder themes fits the pattern as an additional folder for partials.

2. Step 2: Import partial correctly in main.scss

   Use @import 'themes/dark'; to import _dark.scss inside themes folder, omitting underscore and extension.

3. Final Answer:

   @import 'themes/dark'; // Add import in main.scss to include theme styles -> Option C

4. Quick Check:

   Import partial with folder path, no underscore [OK]

Hint: Import new folder partials with folder name + partial name [OK]

Common Mistakes:

• Importing partial without folder path
• Including underscore in import
• Creating separate main files breaking pattern