Blog Post — my-first-post
Welcome to a test article for the Markdown renderer. This document includes headings, lists, tables, code blocks, images, blockquotes, and other common Markdown elements so you can verify styling and behavior.
Quick summary
- Title: Blog Post — my-first-post
- Author: Jakob
- Date: 2025-08-29
Metadata
| Field | Value |
|---|---|
| Author | Jakob |
| Date | 2025-08-29 |
| ID | my-first-post |
Key points
- Prepare content locally.
- Render Markdown through the component.
- Verify lists, tables, and code blocks appear correctly.
Detailed checklist
- Headings render
- Paragraphs and inline code render (example:
const x = 1) - Fenced code blocks render
- Tables render
- Nested lists render
Nested list example
- Item A
- Subitem A.1
- Subitem A.2
- Sub-sub 1
- Sub-sub 2
- Item B
Example code
JS example:
function greet(id) {
return `Hello from post ${id}`;
}
// call
console.log(greet('my-first-post'));
Shell example:
# build and serve
npm run build
npm run dev
Large table example
| Index | Name | Type | Description |
|---|---|---|---|
| 1 | sample.md | file | Contains Markdown content |
| 2 | index.html | file | Mount point for the app |
| 3 | assets/ | folder | Images and static files |
| 4 | really-long.md | file | Long content to test wrapping and overflow behavior |
| 5 | data.csv | file | Comma separated values for import testing |
More lists
- Primary
- Secondary A
- Tertiary A.1
- Tertiary A.2
- Secondary B
- Secondary A
- Another primary item
- Ordered step one
- Ordered step two
- substep a
- substep b
- Ordered step three
Code fence edge cases
// multiline example with template-like content
const tpl = `Post id: ${'my-first-post'}`
console.log(tpl)
# run tests
npm run test -- --watch
Image (placeholder)

Tip: Use the browser devtools to inspect the rendered HTML if something looks off.
Common issues & fixes
- If code blocks show as plain text, confirm the renderer accepts fenced code blocks.
- If tables collapse, ensure the CSS for the prose container includes table styles.
This markdown is generated reactively from the route param so server and client output match and the hydration error should be resolved.