Mobile-first philosophy in Tailwind - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to apply a blue background on mobile devices using Tailwind CSS.

Tailwind

<div class="bg-[1]-500 p-4">
  Mobile first background color
</div>

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

Ared

Bgreen

Cblue

Dyellow

Attempts:

3 left

💡 Hint

Common Mistakes

Using a color other than blue.

Adding screen size prefixes like md: which apply styles only on larger screens.

The class bg-blue-500 sets a blue background color. Tailwind applies this style by default on all screen sizes, starting with mobile.

2fill in blank

medium

Complete the code to make the text size larger on medium screens and above using Tailwind CSS.

Tailwind

<p class="text-base [1]:text-lg">
  Responsive text size
</p>

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

Amd

Bsm

Clg

Dxl

Attempts:

3 left

💡 Hint

Common Mistakes

Using sm: which applies on smaller screens than medium.

Using no prefix, which applies styles on all screen sizes.

The prefix md: applies styles starting at the medium screen size (tablet and up). Here, it changes text size to large on medium screens and bigger.

3fill in blank

hard

Fix the error in the code to correctly apply padding only on large screens and above.

Tailwind

<div class="[1]:p-8">
  Large screen padding
</div>

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

Alg

Bsm

Cxl

Dmd

Attempts:

3 left

💡 Hint

Common Mistakes

Using md: which applies on medium screens, not large.

Using sm: which applies on small screens.

The prefix lg: applies styles starting at large screen sizes (desktop and up). This sets padding to 8 only on large screens and bigger.

4fill in blank

hard

Fill both blanks to create a responsive layout with a column on mobile and a row on medium screens and above.

Tailwind

<div class="flex [1] [2]:flex-row">
  <div>Item 1</div>
  <div>Item 2</div>
</div>

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

Aflex-col

Bblock

Cmd

Dinline

Attempts:

3 left

💡 Hint

Common Mistakes

Using block or inline which are not flexbox directions.

Using the wrong screen size prefix.

By default, flex-col stacks items vertically (column) on mobile. The prefix md: changes layout to flex-row on medium screens and larger, arranging items horizontally.

5fill in blank

hard

Fill all three blanks to create a button that is full width on mobile, half width on medium screens, and has padding 2 on mobile and padding 4 on large screens.

Tailwind

<button class="w-[1] [2]:w-1/2 p-2 [3]:p-4">
  Responsive Button
</button>

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

Afull

Bmd

Clg

Dsm

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong width values like w-1/2 on mobile.

Mixing up screen size prefixes.

The class w-full makes the button full width on mobile. The prefix md: changes width to half on medium screens. Padding p-2 applies on mobile, and lg:p-4 increases padding on large screens.

Practice

1. What does the mobile-first philosophy mean in web design?

easy

A. Designing for small screens first, then adding styles for larger screens

B. Designing only for desktop screens

C. Designing for large screens first, then adjusting for smaller screens

D. Ignoring screen sizes and using fixed layouts

Solution

1. Step 1: Understand mobile-first philosophy

   Mobile-first means starting design with small screens like phones, then adding styles for bigger screens.

2. Step 2: Compare options

   Only Designing for small screens first, then adding styles for larger screens correctly describes this approach; others describe desktop-first or fixed layouts.

3. Final Answer:

   Designing for small screens first, then adding styles for larger screens -> Option A

4. Quick Check:

   Mobile-first = Start small screens first [OK]

Hint: Mobile-first means start small, then grow bigger [OK]

Common Mistakes:

• Thinking mobile-first means designing desktop first
• Confusing mobile-first with ignoring screen sizes
• Believing mobile-first means only designing for phones

2. Which Tailwind CSS class applies styles only on medium and larger screens?

easy

A. md:bg-blue-500

B. bg-blue-500

C. sm:bg-blue-500

D. lg:bg-blue-500

Solution

1. Step 1: Understand Tailwind screen prefixes

   In Tailwind, md: applies styles at medium screen size and above.

2. Step 2: Identify correct prefix for medium screens

   md:bg-blue-500 uses md:, so it applies on medium and larger screens. Others apply on small, large, or all screens.

3. Final Answer:

   md:bg-blue-500 -> Option A

4. Quick Check:

   md: means medium screens and up [OK]

Hint: Remember md: prefix targets medium+ screens [OK]

Common Mistakes:

• Confusing sm: with md:
• Using no prefix and expecting medium-only styles
• Mixing lg: with md:

3. Given this Tailwind code:

<div class="bg-red-500 md:bg-green-500">Box</div>

What background color will the box have on a small screen?

medium

A. Green

B. Red

C. No color

D. Blue

Solution

1. Step 1: Analyze classes on small screen

   The class bg-red-500 applies to all screens by default. The md:bg-green-500 applies only on medium and larger screens.

2. Step 2: Determine active class on small screen

   On small screens, md:bg-green-500 is ignored, so background stays red.

3. Final Answer:

   Red -> Option B

4. Quick Check:

   Default class applies on small screens [OK]

Hint: Default classes apply on all screens unless overridden [OK]

Common Mistakes:

• Thinking md: classes apply on small screens
• Ignoring default classes
• Assuming no color if md: class exists

4. What is wrong with this Tailwind code if the goal is to make text blue on small screens and red on medium and larger screens?

<p class="md:text-red-500 text-blue-500">Hello</p>

medium

A. The order of classes is reversed; it should be text-blue-500 md:text-red-500

B. The md: prefix should be on text-blue-500

C. No error; it works as intended

D. Tailwind does not support multiple text color classes

Solution

1. Step 1: Understand class application order

   Tailwind applies base classes first, then overrides with media prefixes like md:.

2. Step 2: Check if code matches goal

   text-blue-500 applies on all screens, overridden by md:text-red-500 on medium+ screens, matching the goal.

3. Final Answer:

   No error; it works as intended -> Option C

4. Quick Check:

   Base then md: override works [OK]

Hint: Base class first, then md: override for bigger screens [OK]

Common Mistakes:

• Thinking order of classes matters in Tailwind
• Believing md: prefix must be on base class
• Assuming Tailwind can't override colors

5. You want a button that is full width on small screens but only 200px wide on medium and larger screens using Tailwind. Which class combination achieves this?

hard

A. w-full w-[200px] md:w-full

B. md:w-full w-[200px]

C. w-[200px] md:w-full

D. w-full md:w-[200px]

Solution

1. Step 1: Understand mobile-first width classes

   Use w-full for full width on small screens (default). Use md:w-[200px] to set width 200px on medium+ screens.

2. Step 2: Check options for correct order and values

   w-full md:w-[200px] sets full width by default, then overrides to 200px on medium screens. Others reverse or duplicate incorrectly.

3. Final Answer:

   w-full md:w-[200px] -> Option D

4. Quick Check:

   Default full width, md override 200px [OK]

Hint: Default small screen first, then md: for bigger screens [OK]

Common Mistakes:

• Reversing order of width classes
• Using md: on full width instead of fixed width
• Duplicating conflicting width classes