Container query preparation in SASS - Mini Project: Build & Apply

Container Query Preparation with Sass

📖 Scenario: You are building a responsive card component that changes its style based on the size of its container, not just the viewport. This is useful for flexible layouts where cards can appear in different sized containers.

🎯 Goal: Create a Sass stylesheet that sets up a container query for a card component. The card should have a base style and a different background color when its container is at least 30rem wide.

📋 What You'll Learn

Use a CSS container class .card-container with the name card-container

Create a card class .card with base styles

Add a container query inside Sass that changes the card background color when the container width is at least 30rem

Use Sass nesting to organize the styles

💡 Why This Matters

🌍 Real World

Container queries let you build components that adapt to their container size, not just the screen size. This is useful in complex layouts like dashboards, widgets, or modular UI where components appear in different sized spaces.

💼 Career

Understanding container queries and Sass nesting is valuable for front-end developers working on modern responsive designs, improving user experience and maintainability.

1

Set up the base card styles

Create a Sass class called .card with these styles: padding: 1rem, border-radius: 0.5rem, and background-color: #f0f0f0.

SASS

.card {
  // Your code here
}

Hint

Use the .card selector and add the styles inside curly braces.

2

Add container declaration

Create a .card-container class with container-type: inline-size and container-name: card-container.

SASS

.card {
  padding: 1rem;
  border-radius: 0.5rem;
  background-color: #f0f0f0;
}

// Your code here

Hint

Create the .card-container selector and add container-type: inline-size; and container-name: card-container; inside it.

3

Write the container query

Inside the .card class, add a container query using @container card-container (min-width: 30rem) that changes the background-color to #d0e6f7.

SASS

.card-container {
  container-type: inline-size;
  container-name: card-container;
}

.card {
  padding: 1rem;
  border-radius: 0.5rem;
  background-color: #f0f0f0;
  // Your code here
}

Hint

Use @container card-container (min-width: 30rem) inside .card and nest the style change.

4

Complete with responsive font size

Add inside the container query a style to set font-size: 1.25rem for the .card.

SASS

.card-container {
  container-type: inline-size;
  container-name: card-container;
}

.card {
  padding: 1rem;
  border-radius: 0.5rem;
  background-color: #f0f0f0;

  @container card-container (min-width: 30rem) {
    background-color: #d0e6f7;
    // Your code here
  }
}

Hint

Inside the container query block, add font-size: 1.25rem; to increase text size.

Practice

1. What is the main purpose of using @container in Sass?

easy

A. To reset all container styles

B. To create animations for containers

C. To define variables inside containers

D. To apply styles based on the size of an element's container

Solution

1. Step 1: Understand container queries

   Container queries allow styling elements depending on their container's size, not the viewport.

2. Step 2: Role of @container in Sass

   The @container rule in Sass is used to write container queries clearly and apply styles conditionally based on container size.

3. Final Answer:

   To apply styles based on the size of an element's container -> Option D

4. Quick Check:

   Container queries = style by container size [OK]

Hint: Remember: @container styles depend on container size, not viewport [OK]

Common Mistakes:

• Confusing container queries with media queries
• Thinking @container creates animations
• Using @container to define variables

2. Which CSS property must be set on a container element to enable container queries in Sass?

easy

A. container-type

B. container-size

C. container-query

D. container-style

Solution

1. Step 1: Identify container query activation property

   To use container queries, the container must declare container-type to enable size-based queries.

2. Step 2: Verify other options

   container-size, container-query, and container-style are not valid CSS properties for this purpose.

3. Final Answer:

   container-type -> Option A

4. Quick Check:

   Enable container queries = container-type [OK]

Hint: Set container-type to activate container queries on an element [OK]

Common Mistakes:

• Using non-existent properties like container-query
• Confusing container-type with container-size
• Forgetting to set container-type on the container

3. Given the Sass code below, what background color will the .box have if its container width is 500px?

@container (min-width: 600px) {
  .box {
    background-color: blue;
  }
}
.box {
  background-color: red;
}

medium

A. Blue

B. Red

C. No background color

D. Green

Solution

1. Step 1: Understand the container query condition

   The container query applies styles only if the container's width is at least 600px.

2. Step 2: Check container width against condition

   The container width is 500px, which is less than 600px, so the container query block does not apply.

3. Step 3: Determine fallback style

   The .box outside the container query has background-color: red;, so this style applies.

4. Final Answer:

   Red -> Option B

5. Quick Check:

   Container width 500px < 600px = red background [OK]

Hint: Check container width against min-width condition to pick color [OK]

Common Mistakes:

• Assuming container query applies regardless of container size
• Confusing container width with viewport width
• Ignoring fallback styles outside @container

4. Identify the error in the following Sass container query code:

@container (max-width 400px) {
  .card {
    padding: 1rem;
  }
}

medium

A. Container queries cannot use max-width

B. Incorrect selector inside @container

C. Missing colon after max-width

D. Padding value should be in px, not rem

Solution

1. Step 1: Check container query syntax

   The condition inside @container must have a colon after the property name, e.g., max-width: 400px.

2. Step 2: Verify other options

   The selector .card is valid, padding in rem is allowed, and max-width is a valid container query condition.

3. Final Answer:

   Missing colon after max-width -> Option C

4. Quick Check:

   Container query conditions need colons [OK]

Hint: Always use colon after property in container query conditions [OK]

Common Mistakes:

• Omitting colon in container query conditions
• Thinking max-width is invalid in container queries
• Confusing units for padding

5. You want to style a .card component differently when its container is narrower than 300px or wider than 700px using Sass container queries. Which of the following is the correct way to write this?

hard

A. @container (max-width: 300px), (min-width: 700px) { .card { font-size: 1.2rem; } }

B. @container (max-width: 300px) and (min-width: 700px) { .card { font-size: 1.2rem; } }

C. @container (max-width 300px), (min-width 700px) { .card { font-size: 1.2rem; } }

D. @container (width < 300px), (width > 700px) { .card { font-size: 1.2rem; } }

Solution

1. Step 1: Understand container query syntax for multiple conditions

   Multiple conditions separated by commas mean OR logic. Use colons after properties.

2. Step 2: Analyze each option

   @container (max-width: 300px), (min-width: 700px) { .card { font-size: 1.2rem; } } correctly uses commas and colons. @container (max-width: 300px) and (min-width: 700px) { .card { font-size: 1.2rem; } } uses AND which requires both conditions simultaneously (impossible here). @container (max-width 300px), (min-width 700px) { .card { font-size: 1.2rem; } } misses colons. @container (width < 300px), (width > 700px) { .card { font-size: 1.2rem; } } uses invalid syntax with < and >.

3. Final Answer:

   @container (max-width: 300px), (min-width: 700px) { .card { font-size: 1.2rem; } } -> Option A

4. Quick Check:

   Use commas for OR, colons after properties [OK]

Hint: Use commas for OR conditions and colons after properties [OK]

Common Mistakes:

• Using 'and' instead of commas for OR conditions
• Omitting colons in conditions
• Using invalid operators like < or > in container queries