CSS file organization - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use multiple CSS files in a project?

Which of the following is the main reason to split CSS into multiple files in a large web project?

A To make the website load slower by adding more HTTP requests

B To organize styles by components or features for easier maintenance

C To confuse developers by scattering styles across many files

D To prevent styles from applying to any HTML elements

💡 Hint

Think about how organizing your clothes in different drawers helps you find them faster.

Splitting CSS into multiple files helps keep styles organized by components or features, making it easier to maintain and update the code.

📝 Syntax

intermediate

Correct way to import CSS files

Which CSS code correctly imports another CSS file named "buttons.css" inside "styles.css"?

CSS

/* Inside styles.css */

A include 'buttons.css';

B import 'buttons.css';

C @import url('buttons.css');

D link rel='stylesheet' href='buttons.css';

💡 Hint

Think about how you include styles inside CSS files, not HTML tags.

The correct syntax to import CSS inside another CSS file is @import url('filename.css');

❓ layout

advanced

Effect of CSS file order on layout

Given two CSS files loaded in this order in HTML:

<link rel="stylesheet" href="base.css">
<link rel="stylesheet" href="theme.css">

If both files style the same element, which file's styles will apply?

A Styles from theme.css will override base.css

B Styles from base.css will override theme.css

C Both styles will apply equally causing a conflict

D Neither style will apply because of conflict

💡 Hint

Later styles in CSS files override earlier ones if selectors have the same specificity.

CSS rules loaded later override earlier ones if they have the same specificity. Since theme.css is loaded after base.css, its styles take precedence.

❓ accessibility

advanced

Organizing CSS for accessibility

Which CSS file organization approach best supports accessibility improvements?

A Separate a CSS file dedicated to accessibility styles like focus outlines and high contrast

B Mix accessibility styles randomly with all other styles in one big file

C Avoid writing any accessibility styles in CSS

D Put accessibility styles only in inline styles inside HTML

💡 Hint

Think about how having a special drawer for important tools helps you find them quickly.

Having a dedicated CSS file for accessibility styles helps developers easily find and update those styles, improving maintainability and accessibility.

❓ selector

expert

Specificity and file organization impact

You have two CSS files:

1. components.css with selector .btn { color: blue; }
2. overrides.css with selector button.btn { color: red; }

Both files are loaded in this order:
<link rel="stylesheet" href="components.css">
<link rel="stylesheet" href="overrides.css">

What color will a <button class="btn"> show?

A Red, because components.css styles are ignored

B Blue, because components.css is loaded first

C Blue, because .btn selector is more specific than button.btn

D Red, because overrides.css has a more specific selector and is loaded last

💡 Hint

More specific selectors override less specific ones if loaded later.

The selector button.btn is more specific than .btn alone, and since overrides.css is loaded after components.css, the button text will be red.

Practice

1. What is the main reason to organize CSS into separate files like reset.css, base.css, and layout.css?

easy

A. To avoid using HTML

B. To make the website load slower

C. To confuse other developers

D. To keep styles easy to manage and maintain

Solution

1. Step 1: Understand CSS file organization purpose

   Organizing CSS into separate files helps keep styles clear and manageable.

2. Step 2: Evaluate the options

   Only To keep styles easy to manage and maintain correctly states the benefit of easier management and maintenance.

3. Final Answer:

   To keep styles easy to manage and maintain -> Option D

4. Quick Check:

   Organizing CSS = easier management [OK]

Hint: Separate CSS files for clarity and easier updates [OK]

Common Mistakes:

• Thinking multiple files slow down the site
• Believing CSS files are only for decoration
• Ignoring the importance of file naming

2. Which of the following is the correct way to link multiple CSS files in an HTML document?

easy

A. <link rel="stylesheet" href="reset.css"><link rel="stylesheet" href="base.css">

B. <style src="reset.css"><style src="base.css">

C. <script src="reset.css"><script src="base.css">

D. <link href="reset.css" rel="script"><link href="base.css" rel="script">

Solution

1. Step 1: Identify correct HTML tag for CSS linking

   The <link> tag with rel="stylesheet" is used to link CSS files.

2. Step 2: Check the options for correct syntax

   <link rel="stylesheet" href="reset.css"><link rel="stylesheet" href="base.css"> uses <link rel="stylesheet" href="file.css"> correctly; others use wrong tags or attributes.

3. Final Answer:

   <link rel="stylesheet" href="reset.css"><link rel="stylesheet" href="base.css"> -> Option A

4. Quick Check:

   Link CSS with <link rel="stylesheet"> [OK]

Hint: Use to add CSS files [OK]

Common Mistakes:

• Using <style> tag with src attribute
• Using <script> tag for CSS files
• Mixing rel attribute values

3. Given these CSS files linked in this order:
<link rel="stylesheet" href="reset.css">
<link rel="stylesheet" href="base.css">
<link rel="stylesheet" href="layout.css">
Which file's styles will apply if all three define the same property for body?

medium

A. reset.css

B. base.css

C. layout.css

D. None, styles will conflict and not apply

Solution

1. Step 1: Understand CSS cascade order

   When multiple CSS files define the same property, the last linked file's style overrides earlier ones.

2. Step 2: Identify the last linked CSS file

   The last linked file is layout.css, so its styles apply.

3. Final Answer:

   layout.css -> Option C

4. Quick Check:

   Last linked CSS overrides earlier ones [OK]

Hint: Last CSS file linked wins on conflicts [OK]

Common Mistakes:

• Thinking reset.css overrides others
• Believing styles merge without override
• Assuming conflicts cause errors

4. You have these CSS files:
reset.css, base.css, components.css
But your styles from components.css are not applying. What is the most likely cause?

medium

A. You linked components.css before reset.css

B. You forgot to link components.css in your HTML

C. You used <script> tag instead of <link> for CSS

D. You wrote CSS rules inside reset.css instead

Solution

1. Step 1: Check if CSS file is linked in HTML

   If components.css is not linked, its styles won't apply.

2. Step 2: Evaluate other options

   Link order affects overrides but won't stop styles entirely; wrong tag causes no styles; writing rules in another file doesn't affect components.css styles.

3. Final Answer:

   You forgot to link components.css in your HTML -> Option B

4. Quick Check:

   Missing link tag means no styles applied [OK]

Hint: Always confirm CSS files are linked in HTML [OK]

Common Mistakes:

• Linking CSS files in wrong order
• Using <script> instead of <link>
• Assuming CSS files auto-load without linking

5. You want to organize your CSS for a large website. Which of these is the best practice for file organization?

hard

A. Split CSS into files like reset.css, base.css, layout.css, and components.css with clear comments

B. Put all styles in one big CSS file to reduce HTTP requests

C. Write CSS inside HTML files only to keep everything together

D. Use random file names to avoid caching issues

Solution

1. Step 1: Consider maintainability and clarity

   Splitting CSS into logical files with clear names and comments helps manage large projects.

2. Step 2: Evaluate other options

   One big file can be hard to maintain; inline CSS in HTML is messy; random file names cause confusion and caching problems.

3. Final Answer:

   Split CSS into files like reset.css, base.css, layout.css, and components.css with clear comments -> Option A

4. Quick Check:

   Logical CSS file splitting improves maintainability [OK]

Hint: Use clear, logical CSS files with comments for big projects [OK]

Common Mistakes:

• Putting all CSS in one file without structure
• Mixing CSS inside HTML files
• Using unclear or random file names