Just like many other apps, Zettlr makes use of
Markdown, originally invented by John Gruber. Of course, over such a long period of time, a huge amount of developments have taken place, that have created the possibilities of modern Markdown applications. In this document the following topics are covered:
- A brief history of Markdown
- Dialects of Markdown
- How Zettlr implements Markdown
- Markdown 101: Headings, block elements, inline elements, links, images and footnotes
- Further resources
A brief history¶
Since the personal computer became widely available in the 1990s, there were two groups of formats existing side-by-side: word processor documents, such as
.odt and code documents, such as
For a long time, both these groups of documents stayed as distinct as would their users. Most office-workers only know how to use Microsoft Word or Excel, maybe also LibreOffice-implementations, while close to nobody coming from a STEM-background would voluntarily use Word or similar software. Those scientists have chosen a different path: they developed a programming language called LaTeX, which allows them to create neatly formatted PDF-files from a bunch of code---they follow the same workflow as researchers from the arts and humanities or regular administrative officers, but use different documents for that.
When Markdown was inaugurated by John Gruber in 2004, it was basically like saying: "Why not both?" Markdown combines both the clear reading experience from word processor documents with the benefits of software code documents, which is both versatile and easy to use---even for people that only know how to operate Word or Writer. One small example: While in word processors you would create a heading by typing "some text" and then selecting the
Heading 1 format from some menu, in Markdown you would simply type
# some text, where the hashtag-symbol tells you immediately: "This is a first level heading!"
At first, Markdown was basically a small script John Gruber wrote for himself to yield these benefits, and it contained a lot of inconsistencies and didn't support many different elements. But over the years, progress was made. Two dates are notable:
- 2004: John Gruber initially launches Markdown
- 2012: A group of developers form CommonMark to standardise Markdown into an internationally accepted norm.
Today, several implementations of the Markdown syntax coexist. The most noteworthy are:
- MultiMarkdown: Extends the initial syntax with footnotes, tables and some metadata.
- Markdown Extra: Again some additions to the initial syntax.
- GitHub Flavoured Markdown: This is a variety of Markdown invented by the hosting platform GitHub (which Zettlr is also hosted on!) and is today one of the most common dialects.
- Pandoc Markdown: Pandoc Markdown is a superset of GitHub flavoured Markdown and adds support for even more elements.
- CommonMark: Tries to implement all possible elements, while being unambiguous. Notably, CommonMark not yet includes a specification for footnotes.
Zettlr and Markdown¶
Zettlr itself implements a mixture of different dialects. The editor itself highlights only GitHub flavoured Markdown (plus some extra-elements, which extends Markdown syntax with Zettelkasten elements. Those are described in the respective chapter on the Zettelkasten method). If you export your documents to HTML and don't have Pandoc installed, Zettlr will convert your documents using the GitHub flavoured Markdown syntax. If available, Zettlr uses Pandoc for exports, which itself reads your Markdown documents using its Pandoc Markdown syntax.
But Zettlr doesn't confine you to writing Markdown. If you wish, you can also add
LaTeX-commands. These commands are correctly interpreted when you convert to PDF. These are omitted when you convert to DOCX or ODT. And they are retained when you convert to HTML. Of course, you can at any position use plain HTML-code as well.
Markdown 101: The most important codes¶
Although Markdown can do a lot of things, in this section I want to describe to you the most important elements that you will use the most, and how you can use them in Zettlr.
Headings are straightforward. They must be put on their own line and have to be indicated using a hashtag symbol. There are six levels of headings at your disposal:
# Heading text— yields a heading of first order
## Heading text— yields a heading of second order
### Heading text— yields a heading of third order
#### Heading text— yields a heading of fourth order
##### Heading text— yields a heading of fifth order
###### Heading text— yields a heading of sixth order
Of course, just as in word processors you can use inline-formatting, such as bold or italic text, or
monospaced (code) text.
**your text**— yields bold text
_your text_— yields italic text
- `your text` — yields monospaced text
Sometimes, you may want to emphasise a whole block of text (such as a longer quote), or create lists. This is also possible and extremely simple using Markdown.
- Create item lists by prepending each line with a
+character. If you would like to, you can mix these symbols!
- Sorted lists need numbers in the format
1.in front of them.
Note: The numbers do not have to be in order. On each export, the converter will automatically correctly number them ascending, so a list containing the list numbers 1, 6, 14, 2 will be rendered as a list using the numbers 1, 2, 3, 4!
Links and images¶
Links are inline-elements and images are block elements, so they follow the same semantics as the elements discussed above. Yet they deserve a little bit more attention, because they offer you more options.
Links are set using the following syntax:
[This text will appear in your final document](http://this-is-your-actual-link.tld) Zettlr will automatically convert this syntax to a clickable link (follow the link target by clicking on it while holding down the
Ctrl-key) for the ease of access (and to shorten those rather long links).
Images work exactly like links, except they start with an exclamation mark (!). Images of course also need a path, because you won't store them in a plain text document. Therefore you can use three different approaches to linking images in your document:
- Use an absolute web-URL, such as https://upload.wikimedia.org/wikipedia/commons/thumb/4/48/Markdown-mark.svg/1000px-Markdown-mark.svg.pngMarkdown.
- Use an absolute path to a file on your own computer, such as
- Use a relative path to a file on your own computer, such as
Tip: You can provide a default image path in the "Editor" tab in the preferences, which Zettlr will always use when you paste an image into the editor.
The relative path is always relative to the document in which you place it. The directory
.. tells Zettlr to look for the image in the parent directory (i.e. to traverse up one directory). If you store your documents in a cloud and access them on different devices, you would naturally use relative image paths, because the absolute paths will definitely differ (especially if you work with two different operating systems).
Tip: Try to insert images and links always using their shortcuts,
Cmd/Ctrl+Kfor links and
Cmd/Ctrl+Shift+Ifor images. If you have a valid path in your clipboard, it will even automatically insert it for you, making your life easy. The best way to insert a link, for instance, would therefore be to first copy the link to your clipboard, then select the text you want to link and third press
Cmd/Ctrl+K. Then the selected text will become the displayed link text and the link from your clipboard will be used as the link target.
Footnotes are what most researchers in arts and humanities are of course interested in. So here some general rules for inserting footnotes and how Zettlr interacts with them. According to standard Markdown syntax, footnotes require two elements: First the reference somewhere in the text in the format
x stands for a unique identifier. Basically, you can use anything you want, as long as this identifier is not used by a second footnote as well. But normally, you will want to stick with ascending numbers. (Also: These numbers don't have to be in order—as long as you export your Markdown document, Pandoc will automatically re-number the footnotes correctly. So if you decide to delete a footnote later on, don't worry that the numbers won't neatly match up in your document anymore.)
The second element footnotes require is a block element, the footnote reference text. It is always in the following format:
[^x]: Your reference text. As you can see, the identifier is a replica of your reference that appears in the text, only now it is followed by a colon. It is common sense that you put your references in a list at the very end of your document. Yet, this jumping back and forth between the reference text and your footnote reference is cumbersome, and therefore Zettlr tries to ease your life. Move your mouse over a footnote reference to see the footnote text. Click it while holding down
Ctrl to edit the footnote. Press
Shift+Return to save your changes.
Fenced code blocks¶
Zettlr also supports so-called "fenced code blocks." These are the block-version of the inline code element. To start a code block, type three backticks "`" in a row on an empty line. Close the code block again with three back ticks on an empty line. Everything in between those two "fences" will be rendered using monospace font to indicate that this is indeed code.
Currently, the following languages are supported by the engine (the names in braces are the identifiers you would need to use in Zettlr, as they do not contain special characters, which might upset an engine):
- C (c)
- C# (csharp)
- C++ (cpp)
- CSS (css)
- Go (go)
- Java (java)
- Kotlin (kotlin)
- LESS (less)
- Objective C (objectivec)
- PHP (php)
- Python (python)
- R (r)
- Ruby (ruby)
- SQL (sql)
- Swift (swift)
- YAML (yaml)
More languages can be implemented on your request. If you need a specific language, please refer to the available ones and open up an issue on GitHub, so that we know which one we should add!
Resources on Markdown¶
Do you want to learn all about Markdown? That is great! A good resource that covers all elements is to be found on Learn X in Y minutes. If you want to get used to writing clean and unambiguous Markdown, view the specifications by CommonMark. Also, there's a "book" on the GitHub flavoured Markdown syntax. View it here.