Full Markdown stress test

This post exists to test how the theme behaves with typical technical blog content.

Basic text

A regular paragraph with bold, italic, both, inline code, strikethrough, and a link to Hugo.

It is also useful to test long technical terms such as std::vector<BookPage>, ReaderController::OnAppletSuspended(), and paths like sdmc:/3ds/3dslibris/cache/covers/.

Lists

Unordered list:

• First item.
• Second item with a bit more text to check wrapping.
• Third item:
  • Nested item A.
  • Nested item B.
    • Deeply nested item.

Ordered list:

1. Prepare the content.
2. Build the demo.
3. Check the page on mobile.
4. Fix odd spacing.

Task list:

• Create the theme.
• Add a demo.
• Review accessibility.
• Publish a release.

Quote

Design does not break when everything is perfect. Design is tested when content is irregular, long, and slightly uncomfortable.

Table

Code

Short code block:

hugo server --source exampleSite

Longer code block:

struct ViewportState {
    int zoom_index = 0;
    int max_zoom_index = 0;
    int center_x = 0;
    int center_y = 0;
    bool interaction_active = false;
};

void ClampViewport(ViewportState& viewport, int width, int height) {
    if (viewport.center_x < 0) {
        viewport.center_x = 0;
    }

    if (viewport.center_y < 0) {
        viewport.center_y = 0;
    }
}

Separators

Text before the separator.

Text after the separator.

Footnote

This sentence has a footnote.¹

Basic HTML

This content is inside a details block. It helps check whether the theme styles it nicely or at least does not break.