Imaginary documentation page. Here would be some introduction text.
The table of contents that Markdeep produces is stuffed on the right side, if the browser window is wide enough. Otherwise it is hidden.
Regular styling like bold, italics, strikethrough, inline code
, etc. Lists as:
- A
- Bullet
- List
And:
- A
- Numbered
- List!
Symbol substitutions: a 45-degree turn; som x -> y arrows; some whoa ==> fancy <==> arrows.
Is this a definition list? : Looks like one to me Is that right? : Possibly!
And a code listing:
int main()
{
return 1;
}
Thing Name | Description | Notes |
---|---|---|
Yes | Yup! | |
No | Nope :( | |
FileNotFound | Doesn't find files | Pass -sFIND_FILE=maybe to maybe find them |
******************************************* Here's a text to the right of the diagram,
- +-----------------+ .-. * ain't that fancy. Pretty fancy indeed, I
- |\ | .-+ | * must say! Markdeep diagrams are generally
- | \ A-B *---+--> .--+ '--. * enclosed into a rectangle full made of
*
- | \ | | Cloud! | * symbols; and are "drawn" using ASCII-art
- +---+-------------+ '-------------' * style, with
- | + / \ * o
etc. ******************************************* Suh-weet!
Another random diagram, just because:
- +-+-+-+-*-o *
- / / ^ / *
- / v / / *
- +-+-+-+ *
!!! Note Hey I'm a note. Don't mind me, I'm just sitting here.
!!! WARNING I'm a warning, perhaps. Something might happen!
!!! Error: Never Pass nullptr
to a Shader
Invoking a shader with a null argument can seg fault.
This is a multi-line admonition.
Seriously, don't call shaders like that.
This is an embedded html node by the way!
- API doc style created by Aras Pranckevičius
- Markdeep by Morgan McGuire.