
Geek
[email protected] · npub1m2jphmdkskgnvwl5gplksl9e0zwv2sldqf9mwlpz6tyymz84g9fsqr3wgu
Markdown render test document
Everything below should look right in the reader. If a section doesn't render the way this list promises, the parser or the renderer dropped it.
Headings and emphasis
This paragraph has bold, italic, struck text, inline code, a bare URL https://njump.me and a named link. It even spans a second line to prove the word flow rejoins cleanly.
Blockquotes should sit as a quiet inset panel. A second line keeps the same voice as the first — no orphaned text.
Lists
Ordered:
- one
- two
- three
Unordered:
- alpha
- beta
Task List
- write the test article
- publish it from the composer
- read it in the reader
- fix whatever looks broken
Table
| feature | markdown | check |
|---|---|---|
| headings | ## |
left |
| task lists | - [x] |
center |
| alignment | ---: |
right |
Code
fn main() {
println!("fenced blocks hold their shape");
}
This is the end...my only friend, the end.