Technical MDX Test

This article is a deliberately plain but wide-ranging markdown sample. It is meant to check how the post styles handle real-world content, not to tell a story.

Overview

MDX should support the usual building blocks:

• headings
• paragraphs
• emphasis and strong emphasis
• links and inline code
• ordered and unordered lists
• nested quotes
• code blocks
• tables
• horizontal rules

Inline Formatting

You can mix inline code, italic text, bold text, and even combined emphasis inside a paragraph.

The purpose is to make sure the article layout does not break when a sentence becomes a little more technical, such as referencing next/navigation, useEffect, or generateStaticParams.

Lists

Unordered

• First item
• Second item with a link to Next.js
• Third item with const example = true

Ordered

1. Parse the MDX
2. Render the article shell
3. Verify spacing and typography

Nested Content

Markdown blockquotes should remain readable.

Nested quotes should still feel distinct.

Code Samples

type Config = {
  title: string
  enabled: boolean
}

const config: Config = {
  title: "MDX Test",
  enabled: true,
}

export function getSummary(input: string) {
  return input.trim().toLowerCase()
}

Table

Final Notes

The goal here is simple: if the post style can handle this document, it should be fine for most blog entries.

You can also verify that long paragraphs wrap naturally and that links, code, and emphasis remain visually distinct.