Responsive typography scaling in Tailwind - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is responsive typography scaling?

Responsive typography scaling means adjusting text size smoothly across different screen sizes so it looks good and is easy to read everywhere.

beginner

How does Tailwind CSS help with responsive typography?

Tailwind uses utility classes with breakpoints like sm:, md:, lg: to change font sizes at different screen widths easily.

intermediate

What CSS unit is recommended for smooth scaling of text size?

Using rem or em units is recommended because they scale relative to the root or parent font size, helping text adjust nicely on different devices.

intermediate

Explain the use of the clamp() function in responsive typography.

clamp() lets you set a minimum, preferred, and maximum font size so text scales smoothly between screen sizes without getting too small or too big.

beginner

Why is accessibility important in responsive typography?

Accessible typography ensures text is readable for everyone, including people with vision difficulties, by using sufficient size, contrast, and spacing across all devices.

Which Tailwind class changes font size on medium screens and larger?

A md:text-lg

B sm:text-lg

C lg:text-lg

D text-lg

The prefix md: applies styles starting at the medium breakpoint and up.

What does the CSS function clamp(1rem, 2vw, 2rem) do?

A Sets font size between 1rem and 2rem, scaling with viewport width

B Fixes font size at 2vw

C Sets font size to 1rem only

D Ignores viewport size and uses 2rem

clamp() sets a minimum (1rem), preferred (2vw), and maximum (2rem) font size.

Why use rem units for font sizes?

A They are fixed pixel sizes

B They scale relative to the root font size, helping consistency

C They only work on small screens

D They are deprecated units

rem units help text scale consistently across devices by referencing the root font size.

Which Tailwind utility is NOT related to responsive typography?

A text-xl

B md:text-2xl

C bg-blue-500

D sm:text-base

bg-blue-500 controls background color, not typography.

What is a key benefit of responsive typography?

A Text becomes bold on mobile

B Text color changes automatically

C Text size stays fixed

D Text remains readable on all screen sizes

Responsive typography ensures text adjusts so it is easy to read on any device.

Describe how you would use Tailwind CSS to make a heading's font size change on small, medium, and large screens.

Think about how Tailwind applies styles at different screen widths.

Explain why using CSS clamp() is helpful for responsive typography and give a simple example.

Clamp helps avoid text being too small or too large.

Practice

1. What does the Tailwind class text-lg md:text-xl do in terms of font size?

easy

A. Sets the font size to large on small screens and extra large on medium and bigger screens.

B. Sets the font size to extra large on all screen sizes.

C. Sets the font size to large only on medium screens.

D. Sets the font size to extra large only on small screens.

Solution

1. Step 1: Understand Tailwind responsive prefixes

   The prefix md: applies styles starting from medium screen sizes (768px and up).

2. Step 2: Interpret the class text-lg md:text-xl

   It sets font size to large by default, then changes to extra large on medium and larger screens.

3. Final Answer:

   Sets the font size to large on small screens and extra large on medium and bigger screens. -> Option A

4. Quick Check:

   Responsive prefix changes font size at medium breakpoint [OK]

Hint: Look for prefixes like md: to spot screen size changes [OK]

Common Mistakes:

• Thinking md: applies to small screens
• Assuming no change in font size
• Confusing default and prefixed classes

2. Which of the following is the correct Tailwind syntax to make text size small on mobile and medium on large screens?

easy

A. text-md lg:text-sm

B. text-sm lg:text-md

C. text-sm lg:text-lg

D. text-lg md:text-sm

Solution

1. Step 1: Identify correct font size classes

   Tailwind uses text-sm for small, text-md is not a valid class, text-lg is medium-large.

2. Step 2: Check responsive prefix usage

   lg: applies styles at large screens (1024px+). So text-sm lg:text-lg means small text on mobile, larger text on large screens.

3. Final Answer:

   text-sm lg:text-lg -> Option C

4. Quick Check:

   Use valid classes and correct prefixes [OK]

Hint: Remember text-md is invalid; use text-sm, text-base, text-lg [OK]

Common Mistakes:

• Using invalid class text-md
• Reversing screen size prefixes
• Mixing up font size names

3. What font size will the text have on a 1200px wide screen with this class: text-base sm:text-lg md:text-xl lg:text-2xl?

medium

A. text-base

B. text-xl

C. text-lg

D. text-2xl

Solution

1. Step 1: Identify screen size breakpoints

   1200px width is larger than lg breakpoint (1024px), so lg: classes apply.

2. Step 2: Determine which font size applies

   Since lg:text-2xl applies at 1024px+, the font size will be 2xl on 1200px screen.

3. Final Answer:

   text-2xl -> Option D

4. Quick Check:

   Largest breakpoint prefix applies at wide screens [OK]

Hint: Pick the largest breakpoint prefix less than screen width [OK]

Common Mistakes:

• Choosing smaller breakpoint sizes
• Ignoring lg: prefix effect
• Confusing breakpoint order

4. You wrote text-base md:text-lg sm:text-xl but the font size is not increasing on medium screens. What is the problem?

medium

A. Tailwind does not support multiple responsive prefixes on one element

B. The order of responsive prefixes is incorrect; sm: should come before md:

C. You must use lg: instead of md: for medium screens

D. The base font size must be larger than responsive sizes

Solution

1. Step 1: Understand responsive prefix order

   Tailwind applies styles in order of screen size: base, sm, md, lg, xl.

2. Step 2: Check class order impact

   Classes are applied left to right, so md:text-lg is overridden by sm:text-xl because sm: is smaller breakpoint but comes later.

3. Final Answer:

   The order of responsive prefixes is incorrect; sm: should come before md: -> Option B

4. Quick Check:

   Order responsive classes from smallest to largest breakpoint [OK]

Hint: Write responsive classes from smallest to largest breakpoint [OK]

Common Mistakes:

• Placing larger breakpoint classes before smaller ones
• Assuming Tailwind ignores class order
• Confusing breakpoint sizes

5. You want text to be text-sm on mobile, text-base on tablets (640px+), and text-lg on desktops (1024px+). Which Tailwind class combination achieves this?

hard

A. text-sm md:text-base lg:text-lg

B. text-sm sm:text-lg md:text-base

C. text-sm sm:text-base md:text-lg

D. text-base sm:text-sm lg:text-lg

Solution

1. Step 1: Match breakpoints to screen sizes

   Mobile is default (no prefix), tablets start at sm (640px), desktops at lg (1024px). For 1024px+, lg: is correct for desktops.

2. Step 2: Check class correctness

   text-sm default for mobile, md:text-base applies at 768px+, and lg:text-lg applies at 1024px+. This combination ensures text-base on tablets (md breakpoint) and text-lg on desktops (lg breakpoint).

3. Final Answer:

   text-sm md:text-base lg:text-lg -> Option A

4. Quick Check:

   Use default, then md:, then lg: for ascending screen sizes [OK]

Hint: Use default, then md:, then lg: for ascending screen sizes [OK]

Common Mistakes:

• Mixing breakpoint order
• Using lg: instead of md: for tablets
• Setting smaller sizes on larger screens