A prose stylesheet is only finished when it has met a table, a nested list, a code block and a blockquote in the same document. Pick the elements you want and this produces one that contains all of them.
What you can control
- Nine element types, each toggled independently, so you can isolate the one that is misbehaving.
- Tables come with a configurable row count for testing horizontal overflow.
- Task lists and blockquotes cover the two GitHub-flavoured elements renderers most often skip.
- An optional table of contents with working anchor links, for checking heading-slug generation.
What this is not
Headings are generated per section, so a document with the table of contents enabled will have anchor links matching its own headings but no meaningful hierarchy.
Questions
Is this GitHub-flavoured Markdown?
Yes. Tables, task lists and fenced code blocks are all GFM extensions, so test your renderer supports them before enabling those elements.
Can I use this to test my prose CSS?
That is the main use. Turn on every element, paste the result into your renderer, and you will find the elements you never styled.
Why do the anchor links use slugified headings?
Because that is what most Markdown renderers generate. If your links break, your slug function differs from the convention — which is worth knowing.