Markdown and MDX pages in Astro - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import a Markdown file in an Astro component.

Astro

import Content from './post[1]';

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

A.md

B.astro

C.jsx

D.html

Attempts:

3 left

💡 Hint

Common Mistakes

Using .astro or .jsx extensions instead of .md

Forgetting the dot before the extension

The correct file extension for Markdown files is .md. This import allows Astro to load the Markdown content.

2fill in blank

medium

Complete the code to render Markdown content inside an Astro component.

Astro

<Content [1] />

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

Adefault

Bis:raw

Csrc

DContent

Attempts:

3 left

💡 Hint

Common Mistakes

Using default which is not a valid prop here

Trying to render without specifying is:raw

Using is:raw renders the imported Markdown content as raw HTML inside an Astro component.

3fill in blank

hard

Fix the error in this MDX import statement to correctly import an MDX file.

Astro

import Article from './article[1]';

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

A.jsx

B.astro

C.mdx

D.md

Attempts:

3 left

💡 Hint

Common Mistakes

Using .md extension for MDX files

Using .astro or .jsx extensions incorrectly

MDX files use the .mdx extension, so the import must specify this to work correctly.

4fill in blank

hard

Fill both blanks to create a frontmatter export and use it in an Astro Markdown page.

Astro

---
export const [1] = {
  title: 'My Post',
};
---

<h1>{frontmatter.[2]</h1>

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

Afrontmatter

Bcontent

Ctitle

Dmetadata

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong export name like metadata

Accessing frontmatter properties with incorrect keys

The frontmatter object is exported as frontmatter and the title is accessed as frontmatter.title.

5fill in blank

hard

Fill all three blanks to create a dynamic import and render an MDX page with frontmatter.

Astro

import [1] from './blog/[2].mdx';

---
const { [3] } = Post.frontmatter;
---

<h1>{title}</h1>
<Post />

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

APost

Bpost-1

Ctitle

DContent

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong import variable names

Incorrect filename or missing extension

Not destructuring frontmatter correctly

The MDX file is imported as Post, the filename is post-1, and the frontmatter property title is extracted for display.

Practice

1. What is the main difference between Markdown and MDX in Astro?

easy

A. Markdown supports JavaScript code, but MDX does not.

B. Markdown files can run server code, MDX files cannot.

C. MDX is only for styling, Markdown is for content.

D. MDX allows embedding components inside Markdown content, while Markdown does not.

Solution

1. Step 1: Understand Markdown basics

   Markdown is a simple way to write formatted text like headings, lists, and links.

2. Step 2: Understand MDX extension

   MDX extends Markdown by allowing you to include interactive components inside the text.

3. Final Answer:

   MDX allows embedding components inside Markdown content, while Markdown does not. -> Option D

4. Quick Check:

   MDX = Markdown + components [OK]

Hint: Remember: MDX = Markdown + components [OK]

Common Mistakes:

• Thinking Markdown supports components
• Confusing MDX with styling only
• Believing Markdown runs server code

2. Which file extension should you use for a page that includes React components inside Markdown in Astro?

easy

A. .mdx

B. .astro

C. .md

D. .jsx

Solution

1. Step 1: Identify file types for Markdown and MDX

   Markdown files use .md extension, MDX files use .mdx extension to support components.

2. Step 2: Match file extension to React components inside Markdown

   To include React components inside Markdown, use .mdx files.

3. Final Answer:

   .mdx -> Option A

4. Quick Check:

   React components in Markdown = .mdx [OK]

Hint: Use .mdx for Markdown with components [OK]

Common Mistakes:

• Using .md for MDX content
• Confusing .astro with Markdown files
• Choosing .jsx which is for pure React files

3. Given this Astro MDX page snippet, what will be rendered?

---
import Button from '../components/Button.jsx';
---
# Welcome
Click me

medium

A. A syntax error because components can't be imported in MDX.

B. Only the heading 'Welcome' without the button.

C. A heading 'Welcome' and a clickable button labeled 'Click me'.

D. The button renders but the heading does not.

Solution

1. Step 1: Understand MDX import and usage

   MDX allows importing components at the top and using them inline in the Markdown content.

2. Step 2: Analyze the snippet output

   The heading '# Welcome' renders as a heading, and the <Button> component renders as a clickable button with text 'Click me'.

3. Final Answer:

   A heading 'Welcome' and a clickable button labeled 'Click me'. -> Option C

4. Quick Check:

   MDX imports + components = rendered output [OK]

Hint: MDX imports components, renders both text and UI [OK]

Common Mistakes:

• Thinking imports cause syntax errors in MDX
• Assuming components won't render inside MDX
• Ignoring Markdown headings when components are present

4. What is wrong with this Astro MDX page snippet?

---
import Alert from '../components/Alert.jsx'
---
# Notice
This is important

medium

A. No error; this code is correct.

B. Incorrect import path syntax.

C. Missing semicolon after import statement.

D. Missing closing quote in import statement.

Solution

1. Step 1: Check import syntax in MDX frontmatter

   In MDX frontmatter, semicolons are optional and import paths use quotes correctly.

2. Step 2: Verify component usage

   The Alert component is imported and used correctly inside the MDX content.

3. Final Answer:

   No error; this code is correct. -> Option A

4. Quick Check:

   MDX import syntax is flexible = correct [OK]

Hint: Semicolons optional in MDX imports [OK]

Common Mistakes:

• Expecting semicolons after imports
• Thinking import paths need special syntax
• Assuming missing semicolon causes error

5. You want to create a blog post in Astro that uses Markdown for text and includes a custom interactive component for comments. Which approach is best?

hard

A. Write the entire post in .md and import the component inside it.

B. Use .mdx for the post so you can embed the comment component directly.

C. Create a .astro page and write Markdown inside it manually.

D. Use .md and add the component via client-side JavaScript after page load.

Solution

1. Step 1: Understand Markdown limitations

   Plain .md files cannot embed components directly; they are static content.

2. Step 2: Consider MDX advantages

   .mdx files allow mixing Markdown with components, perfect for interactive elements like comments.

3. Step 3: Evaluate other options

   .astro pages can include Markdown but require more setup; client-side JS injection is less clean and less integrated.

4. Final Answer:

   Use .mdx for the post so you can embed the comment component directly. -> Option B

5. Quick Check:

   Interactive + Markdown = MDX [OK]

Hint: Embed components directly by using .mdx files [OK]

Common Mistakes:

• Trying to import components in plain .md files
• Ignoring MDX for interactive content
• Overcomplicating with client-side JS injection