First, take a look at the overall structure of the document. At the very
beginning is metadata, including a title, author, keywords, copyright
information, etc. Where possible, this metadata is put to appropriate use,
otherwise it is stored in a format designed to be easily read and minimally
distracting:
In plain text and XHTML snippets1, it is located at the top of the
document.
In a full XHTML document, is located in the <head> section, and the title
and CSS metadata, if present, are used appropriately.
In a PDF generated from my XSLT files, metadata is used to generate the
appropriate fields (title, author, keywords) in the PDF itself. Some PDF
readers will let you examine this data. Additionally, the title, subtitle,
author, and copyright are placed at the beginning of the document.
In a Scrivener document, you can put the metadata in the first File in the
Binder, but the preferred location is in the "MultiMarkdown Settings..."
pane (in the File Menu.)
There are a lot of standard metadata keys that can be used, or you can create
your own and use them as you see fit. Definitely a powerful feature.
Structure
The next thing to look at is the overall structure of the document. You can
visualize a Markdown document as an outline, with different sections and
different levels within those sections. Based on your output format, these can
be used to generate headers, or sections, or even chapters. It's all based on
what tools you use to process the XHTML output.
Even within the XHTML document, however, you can make use of this structure to
allow easy navigation within the document. You can link directly to the
Introduction (and to when using LaTeX), for instance. And
if you are creating a PDF, it will contain a hierarchy of section names that
you can use to allow easy navigation, if your PDF reader supports this
function.
Footnotes
Footnotes are very easy to implement in MultiMarkdown, as described in the
MultiMarkdown Syntax Guide.2
Tables
Tables can be quite useful for showing data in a meaningful way. As an
example, here is a table comparing MultiMarkdown vs. Crayons.
Pomaceous fruit of plants of the genus Malus in
the family Rosaceae.
Also the makers of really great products.
Banana
Yellow fruit
A delicious fruit that can be hazardous
if left on the ground.
A fruit that comes with it's own packaging
Orange
The fruit of an evergreen tree of the genus Citrus.
Critic Markup
This is is a test.
This is a test.
This isn'tis a test.
This is a test.
This is a testWhat is it a test of?.
Typographical conventions
By incorporating John Gruber's SmartyPants program into your workflow, you
can generate more "correct" typographic punction in your XHTML pages, and in
your LaTeX source if you are generating PDF's---this includes en and em
dashes, and ellipses....
Very nice when you want to focus on writing, not grammar.
Image Support
If you choose to incorporate images in your documents, this can be easily done
as well. MultiMarkdown makes it easier to link to images and include various
attributes.
As an example, here is an image from my website --- Nautilus
Star. If you have a local copy of the image, you can include
the image in a pdf.
This is a bolded caption
Fenced Code Blocks
Normal code block with some data
as this.
This is a fenced
code block. Tildes **doesn't work**
# Demonstrate Syntax Highlighting if you link to highlight.js #
# http://softwaremaniacs.org/soft/highlight/en/
print "Hello, world!\n";
$a = 0;
while ($a < 10) {
print "$a...\n";
$a++;
}
Bibliography Support
MultiMarkdown offers several mechanisms for managing bibliographies. It has
built-in support for basic citation and bibliography management and
formatting, or you can rely on external tools to handle this for you. There
aren't many citations in this document, but I think it gets the point
across.(p. 42, 2)
Glossary Support
MultiMarkdown has a special format for footnotes that should represent
glossary terms. This doesn't make much difference in XHTML (because there is
no such thing as a glossary in XHTML), but can be used to generate a glossary
within LaTeX documents.
For example, let's have an entry for glossary.4 And what about
ampersands?5
Since we want the ampersand entry to be sorted with the a's, and not with
symbols, we put in the optional sort key ampersand to control sorting.
[^glossary]: glossary: Glossary
A section at the end ...
[^amp]: glossary: & (ampersand)
A punctuation mark ...
Math Support
It's pretty easy to include mathematical equations:
