Style Rendering Test


Edit this page on GitHub

This post marks a new chapter for oodavid.com; alongside a more article-centric design, I’ve migrated away from Jekyll running on GitHub pages to Hugo running on Netlify.

The migration has encouraged me to add a simple taskrunner (npm scripts that run Hugo and SASS) and to play with a more modern style. The design is heavily based on the Stellar theme by HTML5Up, although my source code has been written from the ground-up. What can I say, I like to learn by doing.

This short article demonstrates various Markdown elements and syntax. The purpose is to give me somewhere to test my CSS.

h2 Heading

h3 Heading

h4 Heading

h5 Heading
h6 Heading

Horizontal Rules




Typographic replacements

© © ® ® ™ ™

test.. test… test….. test?….. test!….

!!!!!! ???? ,, – —

“Smartypants, double quotes” and ‘single quotes’

Emphasis

This is bold text

This is bold text

This is italic text

This is italic text

Strikethrough

Blockquotes

Blockquotes can also be nested…

…by using additional greater-than signs right next to each other…

…or with spaces between arrows.

Lists

Unordered

Ordered

  1. Lorem ipsum dolor sit amet
  2. Consectetur adipiscing elit
  3. Integer molestie lorem at massa
  4. You can use sequential numbers…
  5. …or keep all the numbers as 1.

Tasks

Code

Inline code

Syntax highlighting

var foo = function (bar) {
  return bar++;
};
console.log(foo(5));

Tables

Option Description
data path to data files to supply the data that will be passed into templates.
engine engine to be used for processing templates. Handlebars is the default.
ext extension to be used for dest files.

Right aligned columns

Option Description
data path to data files to supply the data that will be passed into templates.
engine engine to be used for processing templates. Handlebars is the default.
ext extension to be used for dest files.

link text

link with title

Autoconverted link https://github.com/oodavid/oodavid.com

Images

Minion Stormtroopocat

Like links, Images also have a footnote style syntax

Alt text

With a reference later in the document defining the URL location:

Footnotes

Footnote 1 link1.

Footnote 2 link2.

Inline footnote3 definition.

Duplicated footnote reference4.

Definition lists

Term 1

Definition 1 with lazy continuation.

Term 2 with inline markup

Definition 2

{ some code, part of Definition 2 }

Third paragraph of definition 2.


  1. Footnote can have markup

    and multiple paragraphs.

    [return]
  2. Footnote text. [return]
  3. Text of inline footnote [return]
  4. Footnote text. [return]