Join us Chargen.one Login

bughoundgang.com: Home About Markdown test

Steve Lord

is working on making this an open source massively multiplayer fediverse content system.

Markdown Stress Test

Chargen.One Logo

This page just shows off different markdown elements and is a stress test page for SSG and the blog engine.

About Markdown

Markdown is a plain text formatting syntax created by John Gruber, designed to be an easy-to-read markup language. The original Markdown syntax specification can be found here.

Much of this content has been taken from the excellent MacDown help page.

Stress Tests

Line Breaks

To force a line break, put two spaces and a newline (return) at the end of the line.

Here is the code:

* This two-line bullet 
won't break

* This two-line bullet  
will break

Strong and Emphasize

Strong: **Strong** or __Strong__ (Command-B)
Emphasize: *Emphasize* or _Emphasize_[^emphasize] (Command-I)

Headers (like this one!)

Header 1
========

Header 2
--------

or

# Header 1
## Header 2
### Header 3
#### Header 4
##### Header 5
###### Header 6

Links and Email

Inline

Just put angle brackets around an email and it becomes clickable: uranusjr@gmail.com
<uranusjr@gmail.com>

Same thing with urls: http://macdown.uranusjr.com
<http://macdown.uranusjr.com>

Perhaps you want to some link text like this: Macdown Website
[Macdown Website](http://macdown.uranusjr.com "Title") (The title is optional)

Reference style

Sometimes it looks too messy to include big long urls inline, or you want to keep all your urls together.

Make a link [a link][arbitrary_id] then on it's own line anywhere else in the file:
[arbitrary_id]: http://macdown.uranusjr.com "Title"

If the link text itself would make a good id, you can link like this [like this][], then on it's own line anywhere else in the file:
[like this]: http://macdown.uranusjr.com

Images

Inline

![Alt Image Text](path/or/url/to.jpg "Optional Title")

Reference style

![Alt Image Text][image-id]
on it's own line elsewhere:
[image-id]: path/or/url/to.jpg "Optional Title"

Lists

Here is the code:

* Lists must be preceded by a blank line (or block element)
* Unordered lists start each item with a `*`
- `-` works too
    * Indent a level to make a nested list
        1. Ordered lists are supported.
        2. Start each item (number-period-space) like `1. `
        42. It doesn't matter what number you use, I will render them sequentially
        1. So you might want to start each line with `1.` and let me sort it out

Block Quote

Angle brackets > are used for block quotes.
Technically not every line needs to start with a > as long as there are no empty lines between paragraphs.
Looks kinda ugly though.

Block quotes can be nested.

Multiple Levels

Most markdown syntaxes work inside block quotes.

Here is the code:

> Angle brackets `>` are used for block quotes.  
Technically not every line needs to start with a `>` as long as
there are no empty lines between paragraphs.  
> Looks kinda ugly though.
> > Block quotes can be nested.  
> > > Multiple Levels
>
> Most markdown syntaxes work inside block quotes.
>
> * Lists
> * [Links][arbitrary_id]
> * Etc.

Inline Code

Inline code is indicated by surrounding it with backticks:
`Inline code`

If your code has `backticks` that need to be displayed, you can use double backticks:
``Code with `backticks` `` (mind the spaces preceding the final set of backticks)

Block Code

If you indent at least four spaces or one tab, I'll display a code block.

print('This is a code block')
print('The block must be preceded by a blank line')
print('Then indent at least 4 spaces or 1 tab')
    print('Nesting does nothing. Your code is displayed Literally')

I also know how to do something called Fenced Code Blocks which I will tell you about later.

Horizontal Rules

If you type three asterisks *** or three dashes --- on a line, I'll display a horizontal rule:


Document Formatting

The Smartypants extension automatically transforms straight quotes (" and ') in your text into typographer’s quotes (, , , and ) according to the context. Very useful if you’re a typography freak like I am. Quote and Smartypants are syntactically incompatible. If both are enabled, Quote takes precedence.

Block Formatting

Table

This is a table:

First Header Second Header
Content Cell Content Cell
Content Cell Content Cell

You can align cell contents with syntax like this:

Left Aligned Center Aligned Right Aligned
col 3 is some wordy text $1600
col 2 is centered $12
zebra stripes are neat $1

The left- and right-most pipes (|) are only aesthetic, and can be omitted. The spaces don’t matter, either. Alignment depends solely on : marks.

Fenced Code Block

This is a fenced code block:

print('Hello world!')

You can also use waves (~) instead of back ticks (`):

~~ print('Hello world!') ~~

I support many popular languages as well as some generic syntax descriptions that can be used if your language of choice is not supported. See relevant sections on the official site for a full list of supported syntaxes.

Inline Formatting

The following is a list of optional inline markups supported:

Option name Markup Result if enabled
Intra-word emphasis So A*maz*ing So Amazing
Strikethrough ~~Much wow~~ Much wow
Underline [^under] _So doge_ So doge
Quote [^quote] "Such editor" Such editor
Highlight ==So good== So good
Superscript hoge^(fuga) hogefuga
Autolink http://t.co http://t.co
Footnotes [^4] and [^4]: 1 and footnote 4

Task List Syntax

  1. [x] I can render checkbox list syntax
  2. [ ] I don't support clicking checkboxes directly in the html window

Programming Syntax

Some markdown interpretations support language highlighting. We can use 3 tilde symbols ("~") to specify an interpreter. For example:

def index
  puts "hello world"
end

Should highlight as ruby, while this:

private void index(){
  MessageBox.Show("hello world");
}

Should highlight as C Sharp.


  1. You don't have to use a number. Arbitrary things like [^footy note4] and [^footy note4]: will also work. But they will render as numbered footnotes. Also, no need to keep your footnotes in order, I will sort out the order for you so they appear in the same order they were referenced in the text body. You can even keep some footnotes near where you referenced them, and collect others at the bottom of the file in the traditional place for footnotes.  

2018 Bughoundgang.com