From b5ab99baf2f2f1e2418640070fda397003ff3dd5 Mon Sep 17 00:00:00 2001 From: Bradley Taunt Date: Sun, 21 Jul 2024 12:18:17 -0400 Subject: Update README, add directories, image, LICENSE, and build config --- build/posts/markdown-examples/index.html | 227 +++++++++++++++++++++++++++++++ 1 file changed, 227 insertions(+) create mode 100644 build/posts/markdown-examples/index.html (limited to 'build/posts/markdown-examples') diff --git a/build/posts/markdown-examples/index.html b/build/posts/markdown-examples/index.html new file mode 100644 index 0000000..f6c0a03 --- /dev/null +++ b/build/posts/markdown-examples/index.html @@ -0,0 +1,227 @@ + + + + + + + + Markdown Examples in wruby + + + + + + + +
+ +

Markdown Examples in wruby

+ +

2024-07-20

+ +

An h2 header

+ +

Paragraphs are separated by a blank line.

+ +

2nd paragraph. Italic, bold, and monospace. Itemized lists +look like:

+ + + +

Note that — not considering the asterisk — the actual text +content starts at 4-columns in.

+ +
+

Block quotes are +written like so.

+ +

They can span multiple paragraphs, +if you like.

+
+ +

Use 3 dashes for an em-dash. Use 2 dashes for ranges (ex., “it’s all +in chapters 12–14”). Three dots … will be converted to an ellipsis. +Unicode is supported. ☺

+ +

An h3 header

+ +

Here’s a numbered list:

+ +
    +
  1. first item
    2. +
  2. second item
    3. +
  3. third item
    4. +
+ +

Note again how the actual text starts at 4 columns in (4 characters +from the left side). Here’s a code sample:

+ +
# Let me re-iterate ...
+for i in 1 .. 10 { do-something(i) }
+
+ +

As you probably guessed, indented 4 spaces. By the way, instead of +indenting the block, you can use delimited blocks, if you like:

+ +
define foobar() {
+    print "Welcome to flavor country!";
+}
+
+ +

(which makes copying & pasting easier). You can optionally mark the +delimited block for Pandoc to syntax highlight it:

+ +
import time
+# Quick, count to ten!
+for i in range(10):
+    # (but not *too* quick)
+    time.sleep(0.5)
+    print i
+
+ +

An h4 header

+ +

Now a nested list:

+ +
    +
  1. +

    First, get these ingredients:

    + +
      +
    • carrots
      • +
    • celery
      • +
    • lentils
      • +
    +
    2. +
  2. +

    Boil some water.

    +
    3. +
  3. +

    Dump everything in the pot and follow +this algorithm:

    + + 
    find wooden spoon
+uncover pot
+stir
+cover pot
+balance wooden spoon precariously on pot handle
+wait 10 minutes
+goto first step (or shut off burner when done)
+
    + +

    Do not bump wooden spoon or it will fall.

    +
    4. +
+ +

Notice again how text always lines up on 4-space indents (including +that last line which continues item 3 above).

+ +

Here’s a link to a website, to a local +doc, and to a section heading in the current +doc. Here’s a footnote 1.

+ +

Tables can look like this:

+ + + + + + + + + + + + + + + + + + + + + + + + + + +
sizematerialcolor
9leatherbrown
10hempnatural
11glasstransparent
+ +

Table: Shoes, their sizes, and what they’re made of.

+ +

A horizontal rule follows.

+ +
+ +

Here’s a definition list:

+ +
+
apples
+
Good for making applesauce. +oranges
+
Citrus! +tomatoes
+
There’s no “e” in tomatoe.
+
+ +

Again, text is indented 4 spaces. (Put a blank line between each +term/definition pair to spread things out more.)

+ +

Here’s a “line block”:

+ + + + + + + + + + + + + +
Line one
Line too
Line tree
+ +

and images can be specified like so:

+ +

example image

+ +

And note that you can backslash-escape any punctuation characters +which you wish to be displayed literally, ex.: `foo`, *bar*, etc.

+
+
    +
  1. +

    Footnote text goes here. ↩

    +
    2. +
+
+
+
+ -- cgit v1.2.3-54-g00ecf