Custom font integration in Tailwind - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the custom font in Tailwind CSS.

Tailwind

@font-face { font-family: 'MyFont'; src: url('[1]'); }

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

A./fonts/MyFont.woff2

BMyFont.woff2

C/fonts/MyFont.ttf

Dfonts/MyFont.otf

Attempts:

3 left

💡 Hint

Common Mistakes

Using just the filename without path

Using wrong file extension

Missing the relative path prefix

The src property needs the correct relative path to the font file. Using ./fonts/MyFont.woff2 correctly points to the font file in the fonts folder.

2fill in blank

medium

Complete the Tailwind config to add the custom font family.

Tailwind

module.exports = { theme: { extend: { fontFamily: { custom: ['[1]', 'sans-serif'] } } } }

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

AMyFont

Bmyfont

C'MyFont'

DmyFont

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase or different casing

Including quotes inside the array

Mismatching the font-family name

The font family name should match exactly the name used in @font-face. Here, 'MyFont' is correct without quotes inside the array.

3fill in blank

hard

Fix the error in the Tailwind class to apply the custom font.

Tailwind

<p class="font-[1]">Hello World</p>

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

AfontCustom

Bmyfont

Ccustom

DMyFont

Attempts:

3 left

💡 Hint

Common Mistakes

Using the font-family name instead of the config key

Using camelCase instead of kebab-case

Adding extra prefixes

The Tailwind class uses the key defined in fontFamily in the config. Since the key is custom, the class is font-custom.

4fill in blank

hard

Fill both blanks to complete the Tailwind config for custom font and enable JIT mode.

Tailwind

module.exports = { mode: '[1]', theme: { extend: { fontFamily: { custom: ['[2]', 'sans-serif'] } } } }

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

Ajit

BMyFont

CMyfont

Dclassic

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'classic' instead of 'jit' for mode

Incorrect casing in font family name

Missing quotes around mode value

JIT mode is enabled by setting mode to 'jit'. The font family name must match the font-face name exactly, which is 'MyFont'.

5fill in blank

hard

Fill all three blanks to complete the CSS @font-face rule with font-family, font-weight, and src.

Tailwind

@font-face { font-family: '[1]'; font-weight: [2]; src: url('[3]'); }

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

AMyFont

B400

C./fonts/MyFont-Regular.woff2

Dbold

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'bold' instead of numeric weight

Incorrect font-family name

Wrong path or missing relative prefix in src

The font-family must match the custom font name. The font-weight is numeric for normal weight, and the src is the relative path to the font file.

Practice

1. What is the main purpose of using @font-face in Tailwind CSS when integrating a custom font?

easy

A. To load and define a custom font so it can be used in your styles

B. To create animations for text using the font

C. To automatically download fonts from Google Fonts

D. To change the font size of text elements

Solution

1. Step 1: Understand the role of @font-face

   @font-face is a CSS rule that lets you load a custom font file into your website.

2. Step 2: Connect @font-face to Tailwind usage

   After loading the font with @font-face, you extend Tailwind's fontFamily to use that font in your classes.

3. Final Answer:

   To load and define a custom font so it can be used in your styles -> Option A

4. Quick Check:

   @font-face loads fonts = D [OK]

Hint: Remember: @font-face loads fonts, not styles [OK]

Common Mistakes:

• Thinking @font-face changes font size
• Confusing font loading with animations
• Assuming it downloads fonts automatically

2. Which of the following is the correct way to extend Tailwind's fontFamily in tailwind.config.js to add a custom font named 'MyFont'?

easy

A. fontFamily: { myfont: 'MyFont' }

B. fontFamily: { 'MyFont': ['custom', 'sans-serif'] }

C. fontFamily: { custom: ['MyFont', 'sans-serif'] }

D. fontFamily: { custom: 'MyFont', fallback: 'sans-serif' }

Solution

1. Step 1: Recall Tailwind fontFamily syntax

   Tailwind expects font families as arrays with font names and fallbacks, e.g., fontFamily: { key: ['FontName', 'fallback'] }.

2. Step 2: Match correct syntax

   fontFamily: { custom: ['MyFont', 'sans-serif'] } correctly uses custom as key and an array with 'MyFont' and 'sans-serif'. Others misuse keys or values.

3. Final Answer:

   fontFamily: { custom: ['MyFont', 'sans-serif'] } -> Option C

4. Quick Check:

   fontFamily uses arrays for fonts = C [OK]

Hint: Use arrays for font names and fallbacks in config [OK]

Common Mistakes:

• Using strings instead of arrays for fontFamily
• Swapping keys and values
• Missing fallback fonts

3. Given this Tailwind config extension:

fontFamily: { custom: ['MyFont', 'sans-serif'] }

and this HTML:

<p class="font-custom">Hello</p>

What font will the paragraph use if 'MyFont' is loaded correctly?

medium

A. No font, text will be invisible

B. The browser default font

C. 'sans-serif' fallback font only

D. 'MyFont' custom font

Solution

1. Step 1: Understand class usage

   The class font-custom applies the font family named 'custom' from Tailwind config.

2. Step 2: Check font loading

   If 'MyFont' is loaded correctly via @font-face, it will be used first, with 'sans-serif' as fallback.

3. Final Answer:

   'MyFont' custom font -> Option D

4. Quick Check:

   font-custom uses 'MyFont' if loaded = A [OK]

Hint: font-custom uses your custom font if loaded properly [OK]

Common Mistakes:

• Assuming fallback font is always used
• Confusing class name with default fonts
• Thinking text disappears without font

4. You added this to your CSS:

@font-face { font-family: 'MyFont'; src: url('/fonts/MyFont.woff2'); }

But your text with font-custom class still shows default font. What is the likely mistake?

medium

A. You used the wrong font file format

B. You forgot to extend fontFamily in tailwind.config.js

C. You applied the wrong Tailwind class name

D. You did not include the font file in your HTML

Solution

1. Step 1: Check font-face usage

   The font is loaded with @font-face, so the font file is available.

2. Step 2: Verify Tailwind config

   Without extending fontFamily in tailwind.config.js, the class font-custom won't apply the new font.

3. Final Answer:

   You forgot to extend fontFamily in tailwind.config.js -> Option B

4. Quick Check:

   fontFamily extension missing = B [OK]

Hint: Always extend fontFamily to use custom fonts in Tailwind [OK]

Common Mistakes:

• Not extending fontFamily in config
• Using wrong class names
• Forgetting to rebuild Tailwind after config change

5. You want to use two custom fonts, 'MyFontBold' and 'MyFontLight', in Tailwind. How should you configure tailwind.config.js and your CSS to use font-boldcustom and font-lightcustom classes for them?

hard

A. Define two @font-face rules with different font-family names and extend fontFamily with keys 'boldcustom' and 'lightcustom' pointing to those fonts

B. Use one @font-face with both fonts and extend fontFamily with a single key

C. Only extend fontFamily once and use CSS font-weight to switch fonts

D. Add both fonts in one @font-face and use font-custom class for both

Solution

1. Step 1: Define separate @font-face rules

   Each font variant needs its own @font-face with unique font-family names like 'MyFontBold' and 'MyFontLight'.

2. Step 2: Extend Tailwind's fontFamily

   In tailwind.config.js, add keys 'boldcustom' and 'lightcustom' pointing to these font-family names so you can use font-boldcustom and font-lightcustom classes.

3. Final Answer:

   Define two @font-face rules and extend fontFamily with 'boldcustom' and 'lightcustom' -> Option A

4. Quick Check:

   Separate font-faces + fontFamily keys = A [OK]

Hint: Use separate font-family names and keys for each font variant [OK]

Common Mistakes:

• Trying to combine fonts in one @font-face
• Using CSS font-weight instead of separate font-family
• Not extending fontFamily for each font variant