Testing the markdown pipeline
This post exists to test one thing: what HTML Ghost actually produces when content arrives as markdown through the Admin API, rather than being typed into the editor.
Why the authoring route matters
Markdown is the most accessible way to write. It is plain text, so it works with any assistive technology, needs no drag and drop, and can be diffed and version controlled.
What this post deliberately includes
Every element below is here because it is one an audit would check:
- A list, to test whether it comes out as a real
ul - A link, to check it is a plain anchor
- A heading order that never skips a level
- A blockquote and a table
A quote, to check whether Ghost wraps it in a blockquote element or fakes it with styling.
| Element | What an audit checks |
|---|---|
| Headings | order, no skipped levels |
| Lists | real list markup, not styled paragraphs |
| Tables | header cells marked as th |
What it deliberately leaves out
No images, because alt text deserves its own test rather than being buried in this one.
What happens next
If the markup below is clean, the pipeline works and guides can live as markdown in git, exactly as the plan already says.
