Loaded Markdown

Markdown Format Coverage

docs/markdown-format-coverage.md

Markdown viewer modes

Markdown Format Coverage

This fixture exercises the Markdown shapes the viewer should render cleanly. It is intentionally compact so visual regressions are easy to spot.

Inline Text

Plain text can include bold, italic, bold italic, inline code, deleted text, named links, and autolinks like https://planpack.localhost.

A blockquote should feel distinct without becoming a giant callout.

It can contain multiple paragraphs and inline formatting.

Lists

  • Planning
    • collect constraints
    • surface blockers
  • Build
    1. write validation first
    2. implement second
    3. verify independently
  1. Ordered item
  2. Ordered item with nested bullets
    • child note
    • another child note

Task List

  • Render GFM task items
  • Keep unchecked tasks readable
  • Avoid page-level clutter

Table

AreaStatusNotes
Human viewreadyProgressive disclosure preferred
Raw viewreadyNeeds line numbers and collapsible sections
Pipeline viewplannedMermaid-backed diagram

Code

{
  "plan": {
    "id": "2026-06-04-markdown-format-coverage",
    "featureName": "Markdown Format Coverage"
  }
}

export function summarize(items: string[]) {
  return items.map((item) => item.trim()).filter(Boolean);
}

Raw HTML

Expandable detail

This raw HTML block should render only after sanitization.

Footnote

Markdown footnotes should collect neatly near the bottom.1

Final paragraph after a horizontal rule.

Footnotes

  1. This is a compact footnote used to check GFM rendering. ↩

Markdown Source75 lines
1# Markdown Format Coverage2 3This fixture exercises the Markdown shapes the viewer should render cleanly. It is intentionally compact so visual regressions are easy to spot.4 5## Inline Text6 7Plain text can include **bold**, _italic_, ***bold italic***, `inline code`, ~~deleted text~~, [named links](https://example.com), and autolinks like https://planpack.localhost.8 9> A blockquote should feel distinct without becoming a giant callout.10>11> It can contain multiple paragraphs and **inline formatting**.12 13## Lists14 15- Planning16  - collect constraints17  - surface blockers18- Build19  1. write validation first20  2. implement second21  3. verify independently22 231. Ordered item242. Ordered item with nested bullets25   - child note26   - another child note27 28## Task List29 30- [x] Render GFM task items31- [ ] Keep unchecked tasks readable32- [ ] Avoid page-level clutter33 34## Table35 36| Area | Status | Notes |37| --- | --- | --- |38| Human view | ready | Progressive disclosure preferred |39| Raw view | ready | Needs line numbers and collapsible sections |40| Pipeline view | planned | Mermaid-backed diagram |41 42## Code43 44```json45{46  "plan": {47    "id": "2026-06-04-markdown-format-coverage",48    "featureName": "Markdown Format Coverage"49  }50}51```52 53```ts54export function summarize(items: string[]) {55  return items.map((item) => item.trim()).filter(Boolean);56}57```58 59## Raw HTML60 61<details>62  <summary>Expandable detail</summary>63  <p>This raw HTML block should render only after sanitization.</p>64</details>65 66## Footnote67 68Markdown footnotes should collect neatly near the bottom.[^source]69 70[^source]: This is a compact footnote used to check GFM rendering.71 72---73 74Final paragraph after a horizontal rule.75