Bird
Raised Fist0
SASSmarkup~5 mins

ITCSS methodology with SASS

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Introduction

ITCSS helps organize CSS in a clear way so styles don't get messy. Using SASS with ITCSS makes writing and managing styles easier and faster.

When your website styles start to get big and hard to manage.
When you want to keep your CSS organized by layers.
When working with a team to avoid style conflicts.
When you want to reuse styles easily with variables and mixins.
When you want to write CSS that is easier to maintain and update.
Syntax
SASS
// ITCSS folder structure example

// 1. Settings: variables, colors, fonts
// _settings.scss

// 2. Tools: mixins, functions
// _tools.scss

// 3. Generic: resets, box-sizing
// _generic.scss

// 4. Elements: basic HTML elements styles
// _elements.scss

// 5. Objects: reusable components, layout
// _objects.scss

// 6. Components: specific UI parts
// _components.scss

// 7. Utilities: helpers, helper classes
// _utilities.scss

// main.scss
@use 'settings';
@use 'tools';
@use 'generic';
@use 'elements';
@use 'objects';
@use 'components';
@use 'utilities';

Each layer builds on the previous one, from general to specific.

SASS partial files start with an underscore (_) and are imported into a main file.

Examples
Define colors and fonts as variables to reuse them easily.
SASS
// _settings.scss
$primary-color: #3498db;
$font-stack: 'Arial, sans-serif';
Create a mixin to center content with flexbox.
SASS
// _tools.scss
@mixin center-flex {
  display: flex;
  justify-content: center;
  align-items: center;
}
Reset default browser styles for consistency.
SASS
// _generic.scss
* {
  box-sizing: border-box;
  margin: 0;
  padding: 0;
}
Style a button using variables and mixins from earlier layers.
SASS
// _components.scss
.button {
  background-color: $primary-color;
  color: white;
  padding: 1rem 2rem;
  border-radius: 0.5rem;
  @include center-flex;
}
Sample Program

This example shows a simple webpage with a styled button. The styles are organized using ITCSS layers in one SASS file. Variables and mixins make the code easy to read and reuse.

SASS
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8" />
  <meta name="viewport" content="width=device-width, initial-scale=1" />
  <title>ITCSS with SASS Example</title>
  <link rel="stylesheet" href="styles.css" />
</head>
<body>
  <button class="button">Click Me</button>
</body>
</html>

/* styles.scss */

// 1. Settings
$primary-color: #3498db;
$font-stack: 'Arial, sans-serif';

// 2. Tools
@mixin center-flex {
  display: flex;
  justify-content: center;
  align-items: center;
}

// 3. Generic
* {
  box-sizing: border-box;
  margin: 0;
  padding: 0;
}

// 4. Elements
body {
  font-family: $font-stack;
  background-color: #f0f0f0;
  height: 100vh;
  display: flex;
  justify-content: center;
  align-items: center;
}

// 5. Objects
// (empty for this example)

// 6. Components
.button {
  background-color: $primary-color;
  color: white;
  padding: 1rem 2rem;
  border-radius: 0.5rem;
  cursor: pointer;
  @include center-flex;
  font-size: 1.25rem;
  transition: background-color 0.3s ease;
}
.button:hover {
  background-color: darken($primary-color, 10%);
}

// 7. Utilities
// (empty for this example)
OutputSuccess
Important Notes

ITCSS helps keep styles predictable and easy to find.

Use SASS features like variables and mixins to avoid repeating code.

Start with general styles and move to specific ones to avoid conflicts.

Summary

ITCSS organizes CSS into layers from general to specific.

SASS makes writing and managing these layers easier with variables and mixins.

Using ITCSS with SASS helps keep your styles clean, reusable, and easy to maintain.

Practice

(1/5)
1. What is the main purpose of the ITCSS methodology when organizing SASS files?
easy
A. To avoid using variables and mixins in SASS
B. To write all styles in one large file for faster loading
C. To arrange styles from general to specific for better maintainability
D. To use only inline styles instead of external stylesheets

Solution

  1. Step 1: Understand ITCSS structure

    ITCSS organizes CSS layers from very general styles to very specific ones.
  2. Step 2: Connect ITCSS with maintainability

    This layering helps keep styles clean and easy to maintain by controlling specificity and order.
  3. Final Answer:

    To arrange styles from general to specific for better maintainability -> Option C
  4. Quick Check:

    ITCSS = organize styles general to specific [OK]
Hint: ITCSS means layering styles from broad to narrow [OK]
Common Mistakes:
  • Thinking ITCSS means one big file
  • Believing ITCSS avoids variables
  • Confusing ITCSS with inline styles
2. Which of the following is the correct order of ITCSS layers from top (most general) to bottom (most specific)?
easy
A. Utilities, Components, Objects, Elements, Generic, Tools, Settings
B. Settings, Tools, Generic, Elements, Objects, Components, Utilities
C. Components, Utilities, Objects, Elements, Generic, Tools, Settings
D. Generic, Settings, Tools, Elements, Objects, Components, Utilities

Solution

  1. Step 1: Recall ITCSS layer order

    The correct ITCSS order starts with Settings (variables), then Tools (mixins), Generic (resets), Elements, Objects, Components, and finally Utilities.
  2. Step 2: Match options with this order

    Only Settings, Tools, Generic, Elements, Objects, Components, Utilities lists the layers in this exact order from general to specific.
  3. Final Answer:

    Settings, Tools, Generic, Elements, Objects, Components, Utilities -> Option B
  4. Quick Check:

    ITCSS order = Settings to Utilities [OK]
Hint: Remember: Settings and Tools come first, Utilities last [OK]
Common Mistakes:
  • Mixing up Utilities and Settings order
  • Placing Components before Objects
  • Confusing Generic with Settings
3. Given this SASS partial import order in ITCSS:
@import 'settings';
@import 'tools';
@import 'generic';
@import 'elements';
@import 'objects';
@import 'components';
@import 'utilities';

What will be the color of a button if:
- Settings define $primary-color: blue;
- Components style button background as $primary-color;
- Utilities override button background to red;
Assuming no other styles affect the button, what color will it show?
medium
A. Green
B. Blue
C. Default browser color
D. Red

Solution

  1. Step 1: Understand import order and CSS cascade

    ITCSS imports from general to specific. Utilities are last and have highest specificity.
  2. Step 2: Determine which style applies last

    Utilities override Components because they come later, so button background becomes red.
  3. Final Answer:

    Red -> Option D
  4. Quick Check:

    Last imported style wins = Red [OK]
Hint: Last imported layer overrides earlier styles [OK]
Common Mistakes:
  • Assuming Components override Utilities
  • Ignoring import order effect
  • Thinking variables change color directly
4. You wrote this SASS import order for ITCSS:
@import 'utilities';
@import 'components';
@import 'objects';
@import 'elements';
@import 'generic';
@import 'tools';
@import 'settings';

What is the main problem with this order?
medium
A. The layers are imported in reverse order, causing specificity issues
B. There are missing variables in the settings layer
C. Mixins are not used in the tools layer
D. Utilities should be imported before settings

Solution

  1. Step 1: Check ITCSS recommended import order

    ITCSS requires importing from Settings to Utilities, not the reverse.
  2. Step 2: Identify consequence of reversed order

    Importing Utilities first means general styles override specific ones, breaking intended cascade.
  3. Final Answer:

    The layers are imported in reverse order, causing specificity issues -> Option A
  4. Quick Check:

    Reverse import order breaks ITCSS layering [OK]
Hint: Always import from Settings to Utilities, not backwards [OK]
Common Mistakes:
  • Thinking missing variables cause import order errors
  • Confusing mixins usage with import order
  • Believing utilities come before settings
5. You want to add a new component style for a card in your SASS project using ITCSS. Where should you place the card styles and why?
.card {
@include box-shadow($shadow-color);
background-color: $card-bg;
}
hard
A. In the Components layer, because cards are reusable UI parts
B. In the Utilities layer, because cards are small helper classes
C. In the Settings layer, because cards define variables
D. In the Generic layer, because cards reset default styles

Solution

  1. Step 1: Identify what a card represents

    A card is a reusable UI component with specific styles and structure.
  2. Step 2: Match card to ITCSS layer

    Components layer holds reusable UI parts like buttons, cards, modals.
  3. Final Answer:

    In the Components layer, because cards are reusable UI parts -> Option A
  4. Quick Check:

    Reusable UI parts = Components layer [OK]
Hint: Put UI parts like cards in Components layer [OK]
Common Mistakes:
  • Placing cards in Utilities or Settings layers
  • Confusing Generic with Components
  • Thinking cards are just variables