Test Post 2025-12-20 Markdown

Test Post 2025-01-18 from Ulysses — Comprehensive Markdown XL Sandbox

This is a test post from Ulysses using Markdown XL. The goal is to validate how the browser UI renders:

• Typography (headings, paragraphs, line-height, hyphenation)
• Links (inline, reference-style, autolinks, mailto, title attributes)
• Lists (nested, mixed markers, task lists)
• Quotes (single + nested, with headings/lists/code inside)
• Tables (alignment, long content, inline code, escaping pipes)
• Code (inline + fenced with language tags; wrapping/scrolling)
• Media (local images vs remote images; alt text, captions, titles)
• Footnotes + maths (if supported)
• HTML passthrough/sanitisation (what gets stripped?)

Site sandbox: stillsofartogo.com

A First Level Header (Setext)

=============================

A Second Level Header (Setext)

Header 3 (ATX)

Header 4

Header 5

Header 6

Paragraphs, line breaks, and spacing

This is a regular paragraph with bold, italics, bold+italics, bold, italics, and .

Hard line break test (two spaces at end of line):
This line should appear directly beneath the previous line (not as a new paragraph).

Soft wrap test:

Now is the time for all good men to come to the aid of their country. This paragraph includes a deliberately long line to see how the editor and front-end handle wrapping and readability at different viewport widths.

Escaping test: *not italic* and _not italic_ and `not code` and \ backslash.

Punctuation test: quotes “like this”, apostrophes ’like this’, an em dash — like this, an en dash – like this, and ellipsis … like this.

Inline code tests

Inline code: stillsofartogo.com

Inline code with punctuation: --dry-run, --force, --verbose

Inline code with backticks (should render sensibly): code containing a `backtick` inside

Inline code with HTML: <blink>should not blink</blink>

Named entity vs numeric entity: — vs —

Links (inline, titles, reference-style, autolinks)

Inline link: Markdown

Inline link with title: example link

Autolink: https://help.ulysses.app/en_US/dive-into-editing/markdown-xl

Mailto: test@example.com

Reference-style links:

This is Ulysses and this is Ghost and this is Google.

Blockquotes (single + nested + mixed content)

This is a blockquote.
This is a second paragraph in the same blockquote.
Inline formatting inside a quote: italics, inline code, .
– A list inside a quote– Nested list itemprint("Code fence inside a blockquote")
for i in range(3):
print(i)This is a nested blockquote.
An H2 inside a nested blockquote
Another paragraph to test spacing inside nested quotes.

Lists (unordered, ordered, nested, mixed, task lists)

Unordered list (asterisks):

• Candy
• Gum
• Booze

Unordered list (pluses):

• Candy
• Gum
• Booze

Unordered list (dashes) + nesting:

• Dashed
• List
• How
  – Do– You
• Feel
• About
• This
• List
• Right
• Here?

Ordered list:

1. Red
2. Green
3. Blue

Ordered list with nesting:

1. Numbered
2. List
3. How
   1. Do2. You
4. Feel
5. About
6. This
7. List
8. Right
9. Here
10. Now?

Mixed list markers + paragraphs + code:

• A list item with multiple paragraphs.

Second paragraph in the same list item, with inline code.

echo "A fenced code block inside a list item"
ls -la

• Another list item.

Task list test (renderer-dependent):

• [ ] Unticked task
• [x] Ticked task
• [ ] Task with bold and inline code

Horizontal rules / dividers

---

Divider label (plain text between rules)

Images (local, remote, titles, captions)

Local image (filename only; publish pipeline-dependent):

Remote image (absolute URL):

Another local image (no alt text):

Panorama local image:

Tables (alignment, long text, inline code, escaping)

Table with deliberate long unbroken string (overflow test):

Footnotes (renderer-dependent)

Here is a footnote reference, and here is a second reference. Re-using the first reference again.

Maths (LaTeX) (renderer-dependent)

Inline maths: $1/2 = 0.5$

Display maths:

$$ 1 / 2 = 0.5 $$

Multiline display maths:

$$ \begin{aligned} (1 + 2)^2 &= 1^2 + 2\cdot1\cdot2 + 2^2 \\ &= 9 \end{aligned} $$

Code blocks (fenced; language tags; nested fence test)

Fenced code block (plain):

This is a plain code fence.
It should be monospaced.
It should preserve spacing.

Fenced code block (bash):

set -euo pipefail
echo "Hello from bash"
printf "Current directory: %s\n" "$PWD"

Fenced code block (json):

{
  "title": "Test Post",
  "year": 2025,
  "features": ["headings", "lists", "tables", "code", "images", "footnotes"],
  "safe": true
}

Fenced code block (diff):

- This line was removed
+ This line was added
@@ section @@
  Context line

Fenced code block (html) — to see if HTML is rendered or escaped:

<section>
  <h2>HTML inside a code block</h2>
  <p>If this renders as HTML, something is wrong — it should remain code.</p>
</section>

Nested fence test: the inner triple backticks should display as text below (not terminate this section).

````markdown

print("This is a code fence shown inside another fence")