# Table of Contents [Table of Contents](#id_p4) [Introduction](#id_p7) [Where to Get This Book](#id_p8) [How to Read This Book](#id_p8) [Beginner Resources](#id_p8) [Syntax Examples](#id_p8) [Asides](#id_p9) [Quirks](#id_p9) [Contributing](#id_p9) [Reporting Issues](#id_p10) [Acknowledgements](#id_p10) [Getting Started](#id_p11) [Why Use Markdown?](#id_p12) [Kicking the Tires](#id_p13) [How Markdown Works](#id_p14) [Flavors of Markdown](#id_p17) [Additional Resources](#id_p17) [Doing Things With Markdown](#id_p19) [Websites](#id_p19) [Documents](#id_p20) [Notes](#id_p20) [Books](#id_p21) [Presentations](#id_p21) [Email](#id_p21) [Documentation](#id_p22) [Basic Syntax](#id_p23) [Headings](#id_p23) [Alternate Syntax](#id_p23) [Paragraphs](#id_p24) [Line Breaks](#id_p24) [Emphasis](#id_p25) [Bold](#id_p25) [Italic](#id_p26) [Bold and Italic](#id_p27) [Blockquotes](#id_p27) [Blockquotes with Multiple Paragraphs](#id_p28) [Nested Blockquotes](#id_p28) [Blockquotes with Other Elements](#id_p29) [Lists](#id_p30) [Ordered Lists](#id_p30) [Unordered Lists](#id_p32) [Adding Elements in Lists](#id_p34) [Code](#id_p39) [Escaping Tick Marks](#id_p39) [Code Blocks](#id_p40) [Horizontal Rules](#id_p41) [Links](#id_p42) [Adding Titles](#id_p42) [URLs and Email Addresses](#id_p42) [Formatting Links](#id_p43) [Reference-style Links](#id_p43) [Images](#id_p46) [Escaping Characters](#id_p47) [Characters You Can Escape](#id_p48) [Extended Syntax](#id_p49) [Availability](#id_p49) [Lightweight Markup Languages](#id_p49) [Markdown Processors](#id_p50) [Tables](#id_p50) [Alignment](#id_p51) [Formatting Text in Tables](#id_p53) [Escaping Pipe Characters in Tables](#id_p53) [Fenced Code Blocks](#id_p53) [Syntax Highlighting](#id_p54) [Footnotes](#id_p55) [Heading IDs](#id_p57) [Linking to Heading IDs](#id_p58) [Definition Lists](#id_p58) [Strikethrough](#id_p59) [Task Lists](#id_p60) [Automatic URL Linking](#id_p60) [Disabling Automatic URL Linking](#id_p61) [Cheat Sheet](#id_p62) [Basic Syntax](#id_p62) [Extended Syntax](#id_p62) [About the Author](#id_p64)   The Markdown Guide Matt Cone This work is licensed under a [Creative Commons Attribution-ShareAlike 4.0](http://creativecommons.org/licenses/by-sa/4.0/deed.en_US) [International License](http://creativecommons.org/licenses/by-sa/4.0/deed.en_US) To Simon Naseem Contents [Introduction ](#id_p7). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i [Where to Get This Book ](#id_p8). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii [How to Read This Book ](#id_p8). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii [Beginner Resources ](#id_p8). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii [Syntax Examples ](#id_p8). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii [Asides ](#id_p9). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii [Quirks ](#id_p9). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii [Contributing ](#id_p9). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii [Reporting Issues ](#id_p10). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv [Acknowledgements ](#id_p10). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv [1. Getting Started ](#id_p11). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 [Why Use Markdown? ](#id_p12). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 [Kicking the Tires ](#id_p13). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 [How Markdown Works ](#id_p14). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 [Flavors of Markdown ](#id_p17). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 [Additional Resources ](#id_p17). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 [2. Doing Things With Markdown ](#id_p19). . . . . . . . . . . . . . . . . . . . . . . . . 9 [Websites ](#id_p19). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 [Documents ](#id_p20). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 [Notes ](#id_p20). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 [Books ](#id_p21). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 [Presentations ](#id_p21). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 [Email ](#id_p21). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 [Documentation ](#id_p22). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 CONTENTS [3. Basic Syntax ](#id_p23). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 [Headings ](#id_p23). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 [Alternate Syntax ](#id_p23). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 [Paragraphs ](#id_p24). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 [Line Breaks ](#id_p24). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 [Emphasis ](#id_p25). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 [Bold ](#id_p25). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 [Italic ](#id_p26). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 [Bold and Italic ](#id_p27). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 [Blockquotes ](#id_p27). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 [Blockquotes with Multiple Paragraphs ](#id_p28). . . . . . . . . . . . . . . . . . . 18 [Nested Blockquotes ](#id_p28). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 [Blockquotes with Other Elements ](#id_p29). . . . . . . . . . . . . . . . . . . . . . 19 [Lists ](#id_p30). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 [Ordered Lists ](#id_p30). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 [Unordered Lists ](#id_p32). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 [Adding Elements in Lists ](#id_p34). . . . . . . . . . . . . . . . . . . . . . . . . . . 24 [Code ](#id_p39). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 [Escaping Tick Marks ](#id_p39). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 [Code Blocks ](#id_p40). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 [Horizontal Rules ](#id_p41). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 [Links ](#id_p42). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 [Adding Titles ](#id_p42). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 [URLs and Email Addresses ](#id_p42). . . . . . . . . . . . . . . . . . . . . . . . . . 32 [Formatting Links ](#id_p43). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 [Reference-style Links ](#id_p43). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 [Images ](#id_p46). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 [Escaping Characters ](#id_p47). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 [Characters You Can Escape ](#id_p48). . . . . . . . . . . . . . . . . . . . . . . . . . 38 [4. Extended Syntax ](#id_p49). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 [Availability ](#id_p49). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 [Lightweight Markup Languages ](#id_p49). . . . . . . . . . . . . . . . . . . . . . . 39 [Markdown Processors ](#id_p50). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 [Tables ](#id_p50). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 [Alignment ](#id_p51). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 CONTENTS [Formatting Text in Tables ](#id_p53). . . . . . . . . . . . . . . . . . . . . . . . . . . 43 [Escaping Pipe Characters in Tables ](#id_p53). . . . . . . . . . . . . . . . . . . . . 43 [Fenced Code Blocks ](#id_p53). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 [Syntax Highlighting ](#id_p54). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 [Footnotes ](#id_p55). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 [Heading IDs ](#id_p57). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 [Linking to Heading IDs ](#id_p58). . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 [Definition Lists ](#id_p58). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 [Strikethrough ](#id_p59). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 [Task Lists ](#id_p60). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 [Automatic URL Linking ](#id_p60). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 [Disabling Automatic URL Linking ](#id_p61). . . . . . . . . . . . . . . . . . . . . . 51 [5. Cheat Sheet ](#id_p62). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 [Basic Syntax ](#id_p62). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 [Extended Syntax ](#id_p62). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 [About the Author ](#id_p64). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Introduction I’m a technical writer, and I’ve used a lot of writing tools over the course of my professional career. One of the most interesting tools I’ve encountered is a markup language called Markdown. My litmus test for a successful writing tool is whether using it can become second nature. Does writing with it feel natural? Or do I feel like I’m constantly fighting against it? I stop using tools that hinder me. Time is valuable, and I don’t have the luxury of indulging things that squander that precious resource. Markdown passes the test with flying colors. Writing using Markdown just feels right. Since its introduction in 2004, millions of people have starting using it to write everything from notes to documents. It’s one of the most successful markup languages of all time. Markdown has succeeded where other markup languages have failed because it strikes the right balance between power and simplicity. It’s easy to learn and simple to use. Its tremendous success means it’s ubiquitous enough to replace WYSIWYG editors on websites like Reddit and GitHub. But Markdown is also powerful enough to create documents, books, and technical documentation. Markdown is literally everywhere. I’ve been using Markdown for years now and I recommend it to everyone I know. There are lots of reasons why you should learn to write using Markdown, but one of the best reasons is that it’s better than the alternatives. Learning Markdown means you can stop using all the subpar writing tools you’ve tolerated for years. It can also further your career. Believe it or not, knowing how to write using Markdown is a requirement for many jobs. That brings us to this book. I couldn’t find a comprehensive Markdown reference guide, so I decided to create one. The Markdown Guide has humble beginnings. It started as a single webpage in 2017. After receiving positive feedback from friends and coworkers, I decided to expand the site. To my astonishment, the Markdown Guide was receiving hundreds of unique Introduction ii visitors a day by early 2018. At that point, it occurred to me that people might also appreciate the Markdown Guide in book format. I hope you enjoy reading this book as much as I’ve enjoyed writing it. Above all, I hope it helps you write using Markdown, and I hope using Markdown makes you a better writer. Where to Get This Book I want everyone to read the Markdown Guide. That’s why it’s [free to download ](https://www.markdownguide.org/book)in PDF, MOBI, and EPUB format. I hope you share it with your friends and family. The vast majority of the book is also available online at [https://www.markdownguide. ](https://www.markdownguide.org) [org. ](https://www.markdownguide.org) How to Read This Book This book is designed to be a comprehensive reference guide to the Markdown markup language. If you’re new to Markdown, start at the beginning and read to the end. If you’re an expert user, keep this book handy — you never know when you’ll need to refer back to the [cheat sheet](#id_p62). Beginner Resources The first two chapters of this book are designed exclusively for readers who are new to Markdown. [Getting Started ](#id_p11)provides a quick introduction to Markdown. It shows you how to get going quickly with the Dillinger online Markdown editor, and it sheds light on some of the stuff going on behind the scenes. [Doing Things With Markdown ](#id_p19)talks about what you can create using Markdown. It also presents some the applications you can use to write using Markdown. Syntax Examples To help you learn how to write using Markdown, I’ve provided three sections for every syntax element in the chapters on [basic ](#id_p23)and [extended syntax](#id_p49):   Introduction iii • Markdown: This is what you’ll type in your Markdown application. • HTML: This is the HTML code that’ll be generated by the Markdown processor. • Rendered Output: This is what the reader will see. To learn more about the Markdown to HTML conversion, see the section on [how](#id_p14) [Markdown works. ](#id_p14) Asides Extra bits of information are displayed with an “i” icon next to them, like this: Here’s some extra information you might find helpful. Tips are displayed with a key icon next to them, like this: Here’s a cool tip you might find useful. Quirks Some of the Markdown and HTML code samples in this book “wrap” to the next line. In the situations where that happens, you’ll see a \\ at the end of the first line of the code block. That \\ isn’t actually part of the code. It’s displayed there to indicate that the next line of the code block is actually part of the same line. Contributing This book is an open-source project, and your contributions are welcome. The [repository ](https://github.com/mattcone/markdown-guide-book)is hosted on GitHub. See the [README ](https://github.com/mattcone/markdown-guide-book/blob/master/README.md)for instructions and guidelines. Introduction iv Reporting Issues Find something wrong? [Create an issue ](https://github.com/mattcone/markdown-guide-book/issues)on GitHub and I’ll fix it as soon as possible. Thank you! Acknowledgements I’m eternally grateful to Reem and our children, Finn and Simon. This book wouldn’t exist without their love and support. I greatly appreciate the help of AK Molteni, Gaylin Walli, Juan Torrez, Diana Lynch, and my parents, Steve Cone and Kathie Lathan, who were sounding boards for the website and book. Thanks to [Josh Ellingson ](http://ellingson.cc/)for creating the amazing, jaw-dropping artwork on the cover. Last, but certainly not least, I’d like to thank you and everyone else who has read and contributed to the Markdown Guide. You’ve not only made this book possible, you’ve made it better!  1\. Getting Started Markdown is a lightweight markup language that you can use to add formatting elements to plaintext text documents. Created by John Gruber in 2004, Markdown is now one of the world’s most popular markup languages. Using Markdown is different than using a [WYSIWYG ](https://en.wikipedia.org/wiki/WYSIWYG)editor. In an application like Microsoft Word, you click buttons to format words and phrases, and the changes are visible immediately. Markdown isn’t like that. When you create a Markdown-formatted file, you add Markdown syntax to the text to indicate which words and phrases should look different. For instance, to denote a heading, you add a number sign before it (e.g., # Heading One). Or to make a phrase bold, you add two asterisks before and after it (e.g., \*\*this text is bold\*\*). It may take a while to get used to seeing Markdown syntax in your text, especially if you’re accustomed to WYSIWYG applications. The screenshot below shows a Markdown file displayed in the [Atom text editor. ](https://atom.io/) This is a Markdown file in the Atom text editor. Getting Started 2 You can add Markdown formatting elements to a plaintext file using a text editor application. Or you can use one of the many Markdown applications for macOS, Windows, Linux, iOS, and Android operating systems. There are also several web-based applications specifically designed for writing in Markdown. Depending on the application you use, you may not be able to preview the formatted document in real time. But that’s okay. [According to Gruber](http://daringfireball.net/projects/markdown/), Markdown syntax is designed to be readable and unobtrusive, so the text in Markdown files can be read even if it isn’t rendered. The overriding design goal for Markdown’s formatting syntax is to make it as readable as possible. The idea is that a Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions. Why Use Markdown? You might be wondering why people use Markdown instead of a WYSIWYG editor. Why write with Markdown when you can press buttons in an interface to format your text? As it turns out, there are a couple different reasons why people use Markdown instead of WYSIWYG editors. • Markdown can be used for everything. People use it to create websites, documents, notes, books, presentations, email messages, and technical documentation. • Markdown is portable. Files containing Markdown-formatted text can be opened using virtually any application. If you decide you don’t like the Markdown application you’re currently using, you can import your Markdown files into another Markdown application. That’s in stark contrast to word processing applications like Microsoft Word that lock your content into a proprietary file format. • Markdown is platform independent. You can create Markdown-formatted text on any device running any operating system. • Markdown is future proof. Even if the application you’re using stops working at some point in the future, you’ll still be able to read your Markdown-formatted Getting Started 3 text using a text editing application. This is an important consideration when it comes to books, university theses, and other milestone documents that need to be preserved indefinitely. • Markdown is everywhere. Websites like Reddit and GitHub support Markdown, and lots of desktop and web-based applications support it. Kicking the Tires The best way to get started with Markdown is to use it. That’s easier than ever before thanks to a variety of free tools. You don’t even need to download anything. There are several online Markdown editors that you can use to try writing in Markdown. [Dillinger ](https://dillinger.io/)is one of the best online Markdown editors. Just open the site and start typing in the left pane. A preview of the rendered document appears in the right pane.  Getting Started 4 The Dillinger Markdown editor is a free and easy way to get started with Markdown. You’ll probably want to keep the Dillinger website open as you read through this guide. That way you can try the syntax as you learn about it. After you’ve become familiar with Markdown, you may want to use a Markdown application that can be installed on your desktop computer or mobile device. How Markdown Works Dillinger makes writing in Markdown easy because it hides the stuff happening behind the scenes, but it’s worth exploring how the process works in general. When you write in Markdown, the text is stored in a plaintext file that has an  Getting Started 5 .md or .markdown extension. But then what? How is your Markdown-formatted file converted into HTML or a print-ready document? The short answer is that you need a Markdown application capable of processing the Markdown file. There are lots of applications available — everything from simple scripts to desktop applications that look like Microsoft Word. Despite their visual differences, all of the applications do the same thing. Like Dillinger, they all convert Markdown-formatted text to HTML so it can be displayed in web browsers. Markdown applications use something called a Markdown processor (also commonly referred to as a “parser” or an “implementation”) to take the Markdown-formatted text and output it to HTML format. At that point, your document can be viewed in a web browser or combined with a style sheet and printed. You can see a visual representation of this process below. The Markdown application and processor are two separate components. For the sake of brevity, I’ve combined them into one element (“Markdown App”) in the figure below.  Getting Started 6 This is a visual overview of the Markdown process. To summarize, this is a four-part process: 1\. Create a Markdown file using a text editor or a dedicated Markdown application. The file should have an .md or .markdown extension. 2\. Open the Markdown file in a Markdown application. 3\. Use the Markdown application to convert the Markdown file to an HTML document. 4\. View the HTML file in a web browser or use the Markdown application to convert it to another file format, like PDF. From your perspective, the process will vary somewhat depending on the application you use. For example, Dillinger essentially combines steps 1-3 into a single, seamless interface — all you have to do is type in the left pane and the rendered output Getting Started 7 magically appears in the right pane. But if you use other tools, like a text editor with a static website generator, you’ll find that the process is much more visible. Flavors of Markdown One of the most confusing aspects of using Markdown is that practically every Markdown application implements a slightly different version of Markdown. These variants of Markdown are commonly referred to as flavors. It’s your job to master whatever flavor of Markdown your application has implemented. To wrap your head around the concept of Markdown flavors, it might help to think of them as language dialects. People in Ciudad Juárez speak Spanish just like the people in Barcelona, but there are substantial differences between the dialects used in both cities. The same is true for people using different Markdown applications. Using [Dillinger ](https://www.markdownguide.org/tools/dillinger/)to write with Markdown is a vastly different experience than using [Ulysses. ](https://www.markdownguide.org/tools/ulysses/) Practically speaking, this means you never know exactly what a company means when they say they support “Markdown.” Are they talking about only the [basic](#id_p23) [syntax elements](#id_p23), or all of the basic and [extended syntax elements ](#id_p49)combined, or some arbitrary combination of syntax elements? You don’t know until you read the documentation or start using the application. If you’re just starting out, the best advice I can give you is to pick a Markdown application with good Markdown support. That’ll go a long way towards maintaining the portability of your Markdown files. You might want to store and use your Markdown files in other applications, and to do that you need to start with an application that provides good support. You can use the [tool directory ](https://www.markdownguide.org/tools/)to find an application that fits the bill. Additional Resources There are lots of other resources you can use to learn Markdown. Here are a few of my favorites: Getting Started 8 • [John Gruber’s Markdown documentation](https://daringfireball.net/projects/markdown/). The original guide written by the creator of Markdown. • [Markdown Tutorial. ](https://www.markdowntutorial.com/)An open source website that allows you to try Markdown in your web browser. • [Awesome Markdown. ](https://github.com/mundimark/awesome-markdown)A list of Markdown tools and learning resources. • [Typesetting Markdown](https://dave.autonoma.ca/blog/2019/05/22/typesetting-markdown-part-1). A multi-part series that describes an ecosystem for typesetting Markdown documents using [pandoc ](https://pandoc.org/)and [ConTeXt. ](https://www.contextgarden.net/)  2\. Doing Things With Markdown Now that you know what Markdown is, you’re probably wondering what you can do with it. The answer is: just about anything. Markdown is a fast and easy way to take notes, create content for a website, and produce print-ready documents. It doesn’t take long to learn the Markdown syntax, and once you know how to use it, you can write using Markdown just about everywhere. Most people use Markdown to create content for the web, but Markdown is good for formatting everything from email messages to grocery lists. Here are some examples of what you can do with Markdown. Websites Markdown was designed for the web, so it should come as no surprise that there are plenty of applications specifically designed for creating website content. If you’re looking for the simplest possible way to create a website with Markdown files, check out [blot.im ](https://blot.im/)and [smallvictori.es](https://smallvictori.es/). After you sign up for one of these services, they create a Dropbox folder on your computer. Just drag and drop your Markdown files into the folder and — poof! — they’re on your website. It couldn’t be easier. If you’re familiar with HTML, CSS, and version control, check out [Jekyll, ](https://jekyllrb.com/)a popular static site generator that takes Markdown files and builds an HTML website. One advantage to this approach is that [GitHub Pages ](https://pages.github.com/)provides free hosting for Jekyll-generated websites. If Jekyll isn’t your cup of tea, just pick one of the [many other](https://www.staticgen.com/) [static site generators available](https://www.staticgen.com/). I used Jekyll to create the [Markdown Guide ](https://www.markdownguide.org/)website. You can view the source code on [GitHub](https://github.com/mattcone/markdown-guide). If you’d like to use a content management system (CMS) to power your website, take a look at [Ghost](https://ghost.org/). It’s a free and open-source blogging platform with a nice Markdown  Doing Things With Markdown 10 editor. If you’re a WordPress user, you’ll be happy to know there’s [Markdown](https://en.support.wordpress.com/markdown/) [support ](https://en.support.wordpress.com/markdown/)for websites hosted on WordPress.com. Self-hosted WordPress sites can use the [Jetpack plugin. ](https://jetpack.com/support/markdown/) Documents Markdown doesn’t have all the bells and whistles of word processors like Microsoft Word, but it’s good enough for creating basic documents like assignments and letters. You can use a Markdown document authoring application to create and export Markdown-formatted documents to PDF or HTML file format. The PDF part is key, because once you have a PDF document, you can do anything with it — print it, email it, or upload it to a website. Here are some Markdown document authoring applications we recommend: • Mac: [MacDown, ](https://macdown.uranusjr.com/)[iA Writer](https://ia.net/writer/), or [Marked](https://marked2app.com/) • iOS / Android: [iA Writer](https://ia.net/writer/) • Windows: [ghostwriter ](https://wereturtle.github.io/ghostwriter/)or [Markdown Monster](https://markdownmonster.west-wind.com/) • Linux: [ReText ](https://github.com/retext-project/retext)or [ghostwriter](https://wereturtle.github.io/ghostwriter/) • Web: [Dillinger ](https://dillinger.io/)or [StackEdit](https://stackedit.io/) [iA Writer ](https://ia.net/writer/templates/)provides templates for previewing, printing, and exporting Markdown-formatted documents. For example, the “Academic – MLA Style” template indents paragraphs and adds double sentence spacing. Notes In nearly every way, Markdown is the ideal syntax for taking notes. Sadly, [Evernote](https://evernote.com/) and [OneNote, ](https://www.onenote.com/)two of the most popular note applications, don’t currently support Markdown. The good news is that several other note applications do support Markdown: Doing Things With Markdown 11 • [Simplenote ](https://simplenote.com/)is a free, barebones note-taking application available for every platform. • [Notable ](https://notable.md/)is a note-taking application that runs on a variety of platforms. • [Bear ](https://bear.app/)is an Evernote-like application available for Mac and iOS devices. It doesn’t exclusively use Markdown syntax by default, but you can enable [Markdown](https://bear.app/faq/Markup%20:%20Markdown/Markdown%20compatibility%20mode/) [compatibility mode](https://bear.app/faq/Markup%20:%20Markdown/Markdown%20compatibility%20mode/). • [Boostnote ](https://boostnote.io/)bills itself as an “open source note-taking app designed for program-mers.” If you can’t part with Evernote, check out [Marxico](https://marxi.co/), a subscription-based Markdown editor for Evernote, or use [Markdown Here ](https://markdown-here.com/features.html#not-just-email)with the Evernote website. Books Looking to self-publish a novel? Try [Leanpub](https://leanpub.com/), a service that takes your Markdown-formatted files and turns them into an electronic book. Leanpub outputs your book in PDF, EPUB, and MOBI file format. If you’d like to create paperback copies of your book, you can upload the PDF file to another service such as [Kindle Direct Publishing](https://kdp.amazon.com/). To learn more about writing and self-publishing a book using Markdown, read [this](https://medium.com/techspiration-ideas-making-it-happen/how-i-wrote-and-published-my-novel-using-only-open-source-tools-5cdfbd7c00ca) [blog post. ](https://medium.com/techspiration-ideas-making-it-happen/how-i-wrote-and-published-my-novel-using-only-open-source-tools-5cdfbd7c00ca) Presentations Believe it or not, you can generate presentations from Markdown-formatted files. Creating presentations in Markdown takes a little getting used to, but once you get the hang of it, it’s a lot faster and easier than using an application like PowerPoint or Keynote. [Remark ](https://remarkjs.com/)[(GitHub project) ](https://github.com/gnab/remark)is a popular browser-based Markdown slideshow tool, as is [Cleaver ](https://jdan.github.io/cleaver/)([GitHub project](https://github.com/jdan/cleaver)). If you use a Mac and would prefer to use an application, check out [Deckset ](https://www.decksetapp.com/)or [Marked. ](https://marked2app.com/) Email If you send a lot of email and you’re tired of the formatting controls available on most email provider websites, you’ll be happy to learn there’s an easy way to write Doing Things With Markdown 12 email messages using Markdown. [Markdown Here ](https://markdown-here.com/)is a free and open-source browser extension that converts Markdown-formatted text into HTML that’s ready to send. Documentation Markdown is a natural fit for technical documentation. Companies like GitHub are increasingly switching to Markdown for their documentation — check out their [blog](https://github.com/blog/1939-how-github-uses-github-to-document-github) [post ](https://github.com/blog/1939-how-github-uses-github-to-document-github)about how they migrated their Markdown-formatted documentation to [Jekyll](https://jekyllrb.com/). If you write documentation for a product or service, take a look at these handy tools: • [Read the Docs ](https://readthedocs.org/)can generate a documentation website from your open source Markdown files. Just connect your GitHub repository to their service and push — Read the Docs does the rest. They also have a [service for commercial entities](https://readthedocs.com/). • [MkDocs ](https://www.mkdocs.org/)is a fast and simple static site generator that’s geared towards building documentation. The source files are written in Markdown and organized with a single YAML configuration file. MkDocs has several [built in themes](https://www.mkdocs.org/user-guide/styling-your-docs/), including a port of the [Read the Docs ](https://readthedocs.org/)documentation theme. One of the newest themes is [MkDocs Material, ](https://squidfunk.github.io/mkdocs-material/)which incorporates elements of Google’s Material Design. • [Docusaurus ](https://docusaurus.io/)is a static site generator designed exclusively for creating documentation websites. It supports translations, search, and versioning. • [VuePress ](https://vuepress.vuejs.org/)is a static site generator powered by [Vue ](https://vuejs.org/)and optimized for writing technical documentation. • [Jekyll ](https://jekyllrb.com/)was mentioned earlier in the section on websites, but it’s also a good option for generating a documentation website from Markdown files. If you go this route, be sure to check out the [Jekyll documentation theme. ](https://idratherbewriting.com/documentation-theme-jekyll/)  3\. Basic Syntax Nearly all Markdown applications support the basic syntax outlined in John Gruber’s original design document. There are minor variations and discrepancies between Markdown processors — those are noted inline wherever possible. Using Markdown doesn’t mean that you can’t also use HTML. You can add HTML tags to any Markdown file. This is helpful if you prefer certain HTML tags to Markdown syntax. For example, some people find that it’s easier to use HTML tags for images. Headings To create a heading, add number signs (#) in front of a word or phrase. The number of number signs you use should correspond to the heading level. For example, to create a heading level three (<h3>), use three number signs (e.g., ### My Header). Markdown HTML \# Heading level 1 <h1>Heading level 1</h1> \## Heading level 2 <h2>Heading level 2</h2> \### Heading level 3 <h3>Heading level 3</h3> \#### Heading level 4 <h4>Heading level 4</h4> \##### Heading level 5 <h5>Heading level 5</h5> \###### Heading level 6 <h6>Heading level 6</h6> Alternate Syntax Alternatively, on the line below the text, add any number of == characters for heading level 1 or -- characters for heading level 2. Basic Syntax 14 Markdown HTML Heading level 1 <h1>Heading level 1</h1> =============== Heading level 2 <h2>Heading level 2</h2> \--------------- Paragraphs To create paragraphs, use a blank line to separate one or more lines of text. You should not indent paragraphs with spaces or tabs. Markdown 1 I really like using Markdown. 2 3 I think I'll use it from now on. HTML 1 < p>I really like using Markdown.</p> 2 3 < p>I think I'll use it from now on.</p> The rendered output looks like this: I really like using Markdown. I think I’ll use it from now on. Line Breaks To create a line break (<br>), end a line with two or more spaces, and then type return. Basic Syntax 15 Markdown 1 This is the first line. 2 And this is the second line. HTML 1 < p>This is the first line.< br /> 2 And this is the second line.</p> The rendered output looks like this: This is the first line. And this is the second line. Emphasis You can add emphasis by making text bold or italic. Bold To bold text, add two asterisks or underscores before and after a word or phrase. To bold the middle of a word for emphasis, add two asterisks without spaces around the letters. Markdown 1 I love \*\*bold text\*\*. 2 3 I love \_\_bold text\_\_. 4 5 Love\*\*is\*\*bold The HTML output of the first two examples is the same. Basic Syntax 16 HTML 1 I love < strong>bold text</strong>. 2 3 Love< strong>is</strong>bold The rendered output looks like this: I love bold text. Loveisbold Italic To italicize text, add one asterisk or underscore before and after a word or phrase. To italicize the middle of a word for emphasis, add one asterisk without spaces around the letters. Markdown 1 The \*cat's meow\*. 2 3 The \_cat's meow\_. 4 5 A\*cat\*meow The HTML output of the first two examples is the same. HTML 1 The < em>cat's meow</em>. 2 3 A< em>cat</em>meow The rendered output looks like this: The cat’s meow. A cat meow Basic Syntax 17 Bold and Italic To emphasize text with bold and italics at the same time, add three asterisks or underscores before and after a word or phrase. Markdown 1 \*\*\*Important\*\*\* text. 2 3 \_\_\_Important\_\_\_ text. 4 5 \_\_\*Important\*\_\_ text. 6 7 \*\*\_Important\_\*\* text. The HTML output of all four examples is the same. HTML 1 < strong>< em>Important</em></strong> text. The rendered output looks like this: Important text. Blockquotes To create a blockquote, add a > in front of a paragraph. Markdown 1 \> Dorothy followed her through many rooms. Basic Syntax 18 HTML 1 < blockquote> 2 < p>Dorothy followed her through many rooms.</p> 3 </blockquote> The rendered output looks like this: Dorothy followed her through many rooms. Blockquotes with Multiple Paragraphs Blockquotes can contain multiple paragraphs. Add a > on the blank lines between the paragraphs. Markdown 1 \> This the first paragraph. 2 \> 3 \> And this is the second paragraph. HTML 1 < blockquote> 2 < p>This the first paragraph.</p> 3 < p>And this is the second paragraph.</p> 4 </blockquote> The rendered output looks like this: This the first paragraph. And this is the second paragraph. Nested Blockquotes Blockquotes can be nested. Add a >> in front of the paragraph you want to nest. Basic Syntax 19 Markdown 1 \> This the first paragraph. 2 \> 3 \>> And this is the nested paragraph. HTML 1 < blockquote> 2 < p>This the first paragraph.</p> 3 < blockquote> 4 < p>And this is the nested paragraph.</p> 5 </blockquote> 6 </blockquote> The rendered output looks like this: This the first paragraph. And this is the nested paragraph. Blockquotes with Other Elements Blockquotes can contain other Markdown formatted elements. Not all elements can be used — you’ll need to experiment to see which ones work. Markdown 1 \> ##### The quarterly results look great! 2 \> 3 \> - Revenue was off the chart. 4 \> - Profits were higher than ever. 5 \> 6 \> \*Everything\* is going \*\*well\*\*. Basic Syntax 20 HTML 1 < blockquote> 2 < h5>The quarterly results look great!</h5> 3 < ul> 4 < li>Revenue was off the chart.</li> 5 < li>Profits were higher than ever.</li> 6 </ul> 7 < p>< em>Everything</em> is going < strong>well</strong>.</p> 8 </blockquote> The rendered output looks like this: The quarterly results look great! • Revenue was off the chart. • Profits were higher than ever. Everything is going well. Lists You can organize items into ordered and unordered lists. Ordered Lists To create an ordered list, add line items with numbers followed by periods. The numbers don’t have to be in numerical order, but the list should start with the number one. Basic Syntax 21 Markdown 1 1\. First item 2 2\. Second item 3 3\. Third item 4 4\. Fourth item 5 6 1\. First item 7 1\. Second item 8 1\. Third item 9 1\. Fourth item 10 11 1\. First item 12 8\. Second item 13 3\. Third item 14 5\. Fourth item The HTML output of all three example lists is the same. HTML 1 < ol> 2 < li>First item</li> 3 < li>Second item</li> 4 < li>Third item</li> 5 < li>Fourth item</li> 6 </ol> The rendered output looks like this: 1\. First item 2\. Second item 3\. Third item 4\. Fourth item Nesting List Items To nest line items in an ordered list, indent the items four spaces or one tab. Basic Syntax 22 Markdown 1 1\. First item 2 2\. Second item 3 3\. Third item 4 1\. Indented item 5 2\. Indented item 6 4\. Fourth item HTML 1 < ol> 2 < li>First item</li> 3 < li>Second item</li> 4 < li>Third item 5 < ol> 6 < li>Indented item</li> 7 < li>Indented item</li> 8 </ol> 9 </li> 10 < li>Fourth item</li> 11 </ol> The rendered output looks like this: 1\. First item 2\. Second item 3\. Third item 1\. Indented item 2\. Indented item 4\. Fourth item Unordered Lists To create an unordered list, add dashes (-), asterisks (\*), or plus signs (+) in front of line items. Basic Syntax 23 Markdown 1 \- First item 2 \- Second item 3 \- Third item 4 \- Fourth item 5 6 \* First item 7 \* Second item 8 \* Third item 9 \* Fourth item 10 11 \+ First item 12 \* Second item 13 \- Third item 14 \+ Fourth item The HTML output of all three example lists is the same. HTML 1 < ul> 2 < li>First item</li> 3 < li>Second item</li> 4 < li>Third item</li> 5 < li>Fourth item </li> 6 </ul> The rendered output looks like this: • First item • Second item • Third item • Fourth item Nesting List Items To nest line items in an unordered list, indent the items four spaces or one tab. Basic Syntax 24 Markdown 1 \- First item 2 \- Second item 3 \- Third item 4 \- Indented item 5 \- Indented item 6 \- Fourth item HTML 1 < ul> 2 < li>First item</li> 3 < li>Second item</li> 4 < li>Third item 5 < ul> 6 < li>Indented item</li> 7 < li>Indented item</li> 8 </ul> 9 </li> 10 < li>Fourth item</li> 11 </ul> The rendered output looks like this: • First item • Second item • Third item – Indented item – Indented item • Fourth item Adding Elements in Lists To add another element in a list while preserving the continuity of the list, indent the element four spaces or one tab, as shown in the following examples. Paragraphs Basic Syntax 25 Markdown 1 \* This is the first list item. 2 \* Here's the second list item. 3 4 I need to add another paragraph below the second list item. 5 6 \* And here's the third list item. HTML 1 < ul> 2 < li>< p>This is the first list item.</p></li> 3 < li>< p>Here's the second list item.</p> 4 < p>I need to add another paragraph below the second list item.</p> 5 </li> 6 < li>< p>And here's the third list item.</p></li> 7 </ul> The rendered output looks like this: • This is the first list item. • Here’s the second list item. I need to add another paragraph below the second list item. • And here’s the third list item. Blockquotes Basic Syntax 26 Markdown 1 \* This is the first list item. 2 \* Here's the second list item. 3 4 \> A blockquote would look great here. 5 6 \* And here's the third list item. HTML 1 < ul> 2 < li>< p>This is the first list item.</p></li> 3 < li>< p>Here's the second list item.</p> 4 < blockquote> 5 < p>A blockquote would look great here.</p> 6 </blockquote> 7 </li> 8 < li>< p>And here's the third list item.</p> 9 </li> 10 </ul> The rendered output looks like this: • This is the first list item. • Here’s the second list item. A blockquote would look great here. • And here’s the third list item. Code Blocks [Code blocks ](#id_p40)are normally indented four spaces or one tab. When they’re in a list, indent them eight spaces or two tabs. Basic Syntax 27 Markdown 1 1\. Open the file. 2 2\. Find the following code block on line 21: 3 4 <html> 5 <head> 6 <title> Test</title> 7 </head> 8 9 3\. Update the title to match the name of your website. HTML 1 < ol> 2 < li>< p>Open the file.</p></li> 3 < li>< p>Find the following code block on line 21:</p> 4 < pre>< code> &lt; html&gt; 5 &lt; head&gt; 6 &lt; title&gt; Test&lt; /title&gt; 7 &lt; /head&gt; 8 </code></pre> 9 </li> 10 < li>< p>Update the title to match the name of your website.</p></li> 11 </ol> The rendered output looks like this: 1\. Open the file. 2\. Find the following code block on line 21: Basic Syntax 28 1 <html> 2 <head> 3 <title> Test</title> 4 </head> 3\. Update the title to match the name of your website. Images Markdown 1 1\. Open the file containing Tux, the Linux mascot. 2 2\. Marvel at its beauty. 3 4 !\[Tux\](images/tux.png) 5 6 3\. Close the file. HTML 1 < ol> 2 < li>< p>Open the file containing Tux, the Linux mascot.</p></li> 3 < li> 4 < p>Marvel at its beauty.</p> 5 < p>< img src="images/tux.png" alt="Tux" /></p> 6 </li> 7 < li>< p>Close the file.</p></li> 8 </ol> The rendered output looks like this: 1\. Open the file containing Tux, the Linux mascot. 2\. Marvel at its beauty.  Basic Syntax 29 Tux 3\. Close the file. Code To denote a word or phrase as code, enclose it in tick marks (`). Markdown 1 At the command prompt, typènanò. HTML 1 At the command prompt, type < code>nano</code>. The rendered output looks like this: At the command prompt, type nano. Escaping Tick Marks If the word or phrase you want to denote as code includes one or more tick marks, you can escape it by enclosing the word or phrase in double tick marks ( “). Basic Syntax 30 Markdown 1 `Ùsècodeìn your Markdown file.`` HTML 1 < code>Usècodeìn your Markdown file.</code> The rendered output looks like this: Usècodeìn your Markdown file. Code Blocks To create code blocks, indent every line of the block by at least four spaces or one tab. Markdown 1 <html> 2 <head> 3 </head> 4 </html> HTML 1 < pre> 2 < code> 3 &lt; html&gt; 4 &lt; head&gt; 5 &lt; /head&gt; 6 &lt; /html&gt; 7 </code> 8 </pre> The rendered output looks like this:  Basic Syntax 31 1 <html> 2 <head> 3 </head> 4 </html> To create code blocks without indenting lines, use [fenced code blocks](#id_p53). Horizontal Rules To create a horizontal rule, use three or more asterisks (\*\*\*), dashes (---), or underscores (\_\_\_) on a line by themselves. Markdown 1 \*\*\* 2 3 \--- 4 5 \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ HTML 1 < hr /> 2 3 < hr /> 4 5 < hr /> The rendered output of all three looks identical: Basic Syntax 32 Links To create a link, enclose the link text in brackets (e.g., \[Duck Duck Go\]) and then follow it immediately with the URL in parentheses (e.g., (https://duckduckgo.com)). Markdown 1 Use \[Duck Duck Go\](https://duckduckgo.com). HTML 1 < p>Use < a href="https://duckduckgo.com">Duck Duck Go</a>.</p> The rendered output looks like this: Use [Duck Duck Go](https://duckduckgo.com/). Adding Titles You can optionally add a title for a link. This will appear as a tooltip when the user hovers over the link. To add a title, enclose it in parentheses after the URL. Markdown 1 Use \[Duck Duck Go\](https://duckduckgo.com "My search engine!"). HTML 1 < p>Use < a href="https://duckduckgo.com" title="My search engine!">Duck \\ 2 Duck Go</a>.</p> The rendered output looks like this: Use [Duck Duck Go](https://duckduckgo.com/). URLs and Email Addresses To quickly turn a URL or email address into a link, enclose it in angle brackets. Basic Syntax 33 Markdown 1 <https://eff.org> 2 <fake@example.com> HTML 1 < a href="https://eff.org">https://eff.org</a> 2 < a href="mailto:fake@example.com">fake@example.com</a> The rendered output looks like this: <https://eff.org> fake@example.com Formatting Links To [emphasize ](#id_p25)links, add asterisks before and after the brackets and parentheses. Markdown 1 I love supporting \*\*\[EFF\](https://eff.org)\*\*. 2 This is the \*\[EFF\](https://eff.org)\*. HTML 1 < p>I love supporting < strong>< a href="https://eff.org">EFF</a></strong>. 2 This is the < em>< a href="https://eff.org">EFF</a></em>.</p> The rendered output looks like this: I love supporting [EFF](https://eff.org/)[. ](https://eff.org/) This is the [ ](https://eff.org/)[EFF](https://eff.org/)[. ](https://eff.org/) Reference-style Links Reference-style links are a special kind of link that make URLs easier to display and read in Markdown. Reference-style links are constructed in two parts: the part you keep inline with your text and the part you store somewhere else in the file to keep the text easy to read. Basic Syntax 34 Formatting the First Part of the Link The first part of a reference-style link is formatted with two sets of brackets. The first set of brackets surrounds the text that should appear linked. The second set of brackets displays a label used to point to the link you’re storing elsewhere in your document. Although not required, you can include a space between the first and second set of brackets. Also, the label in the second set of brackets is not case sensitive and can include letters, numbers, spaces, or punctuation. This means the following example formats are all roughly equivalent for the first part of the link: • \[hobbit-hole\]\[1\] • \[hobbit-hole\] \[1\] • \[hobbit-hole\]\[a\] • \[hobbit-hole\]\[A\] Formatting the Second Part of the Link The second part of a reference-style link is formatted with the following attributes: 1. The label, in brackets, followed immediately by a colon and at least one space (e.g., \[label\]: ). 2\. The URL for the link, which you can optionally enclose in angle brackets. 3\. The optional title for the link, which you can enclose in double quotes, single quotes, or parentheses. This means the following example formats are all roughly equivalent for the second part of the link: • \[hobbit-hole\]: https://en.wikipedia.org/wiki/Hobbit#Lifestyle • \[hobbit-hole\]: https://en.wikipedia.org/wiki/Hobbit#Lifestyle "Hobbit lifestyles" • \[hobbit-hole\]: https://en.wikipedia.org/wiki/Hobbit#Lifestyle 'Hobbit lifestyles' Basic Syntax 35 • \[hobbit-hole\]: https://en.wikipedia.org/wiki/Hobbit#Lifestyle (Hobbit lifestyles) • \[hobbit-hole\]: <https://en.wikipedia.org/wiki/Hobbit#Lifestyle> "Hobbit lifestyles" • \[hobbit-hole\]: <https://en.wikipedia.org/wiki/Hobbit#Lifestyle> 'Hobbit lifestyles' • \[hobbit-hole\]: <https://en.wikipedia.org/wiki/Hobbit#Lifestyle> (Hobbit lifestyles) You can place this second part of the link anywhere in your Markdown document. Some people place them immediately after the paragraph in which they appear while other people place them at the end of the document (like endnotes or footnotes). An Example Putting the Parts Together Say you add a URL as a [standard URL link ](#id_p41)to a paragraph and it looks like this in Markdown: Markdown 1 In a hole in the ground there lived a hobbit. Not a nasty, dirty, wet h\\ 2 ole, filled with the ends of worms and an oozy smell, nor yet a dry, ba\\ 3 re, sandy hole with nothing in it to sit down on or to eat: it was a \[h\\ 4 obbit-hole\](https://en.wikipedia.org/wiki/Hobbit#Lifestyle "Hobbit life\\ 5 styles"), and that means comfort. Markdown 1 In a hole in the ground there lived a hobbit. Not a nasty, dirty, wet h\\ 2 ole, filled with the ends of worms and an oozy smell, nor yet a dry, ba\\ 3 re, sandy hole with nothing in it to sit down on or to eat: it was a \[h\\ 4 obbit-hole\]\[1\], and that means comfort. 5 6 \[1\]: <https://en.wikipedia.org/wiki/Hobbit#Lifestyle> "Hobbit lifestyle\\ 7 s" In both instances above, the HTML for the link would be identical: Basic Syntax 36 HTML 1 < a href="https://en.wikipedia.org/wiki/Hobbit#Lifestyle" title="Hobbit \\ 2 lifestyles">hobbit-hole</a> The output is also identical: In a hole in the ground there lived a hobbit. Not a nasty, dirty, wet hole, filled with the ends of worms and an oozy smell, nor yet a dry, bare, sandy hole with nothing in it to sit down on or to eat: it was a [hobbit-hole, ](https://en.wikipedia.org/wiki/Hobbit#Lifestyle)and that means comfort. Images To add an image, add an exclamation mark (!), followed by alt text in brackets, and the path or URL to the image asset in parentheses. You can optionally add a title after the URL in the parentheses. Markdown 1 !\[Philadelphia's Magic Gardens. This place was so cool!\](images/philly-\\ 2 magic-garden.png "Philadelphia's Magic Gardens") HTML 1 < img src="images/philly-magic-garden.png" alt="Philadelphia's Magic Gar\\ 2 dens. This place was so cool!" title="Philadelphia's Magic Gardens" /> The rendered output looks like this:  Basic Syntax 37 Philadelphia’s Magic Gardens. This place was so cool! Escaping Characters To display a literal character that would otherwise be used to format text in a Markdown document, add a backslash (\\) in front of the character. Markdown 1 \\\* Without the backslash, this would be a bullet in an unordered list. Basic Syntax 38 HTML 1 < p>\* Without the backslash, this would be a bullet in an unordered list\\ 2 .</p> The rendered output looks like this: \* Without the backslash, this would be a bullet in an unordered list. Characters You Can Escape You can use a backslash to escape the following characters. Character Name \\ backslash ` tick mark (see also [escaping tick marks in code)](#id_p39) \* asterisk \_ underscore {} curly braces \[\] brackets () parentheses \# pound sign + plus sign - minus sign (hyphen) . dot ! exclamation mark | pipe (see also [escaping pipe in tables](#id_p53)) 4\. Extended Syntax The [basic syntax ](#id_p23)outlined in John Gruber’s original design document added many of the elements needed on a day-to-day basis, but it wasn’t enough for some people. That’s where extended syntax comes in. Several individuals and organizations took it upon themselves to extend the basic syntax by adding additional elements like tables, code blocks, syntax highlighting, URL auto-linking, and footnotes. These elements can be enabled by using a lightweight markup language that builds upon the basic Markdown syntax, or by adding an extension to a compatible Markdown processor. Availability Not all Markdown applications support extended syntax elements. You’ll need to check whether or not the lightweight markup language your application is using supports the extended syntax elements you want to use. If it doesn’t, it may still be possible to enable extensions in your Markdown processor. Lightweight Markup Languages There are several lightweight markup languages that are supersets of Markdown. They include Gruber’s basic syntax and build upon it by adding additional elements like tables, code blocks, syntax highlighting, URL auto-linking, and footnotes. Many of the most popular Markdown applications use one of the following lightweight markup languages: • [CommonMark](http://commonmark.org/) • [GitHub Flavored Markdown (GFM)](https://github.github.com/gfm/) • [Markdown Extra](https://michelf.ca/projects/php-markdown/extra/) • [MultiMarkdown](http://fletcherpenney.net/multimarkdown/) • [R Markdown](https://rmarkdown.rstudio.com/) Extended Syntax 40 Markdown Processors There are [dozens of Markdown processors ](https://github.com/markdown/markdown.github.com/wiki/Implementations)available. Many of them allow you to add extensions that enable extended syntax elements. Check your processor’s documentation for more information. Tables To add a table, use three or more hyphens (---) to create each column’s header, and use pipes (|) to separate each column. You can optionally add pipes on either end of the table. Markdown 1 | Syntax | Description | 2 | ----------- | ----------- | 3 | Header | Title | 4 | Paragraph | Text | HTML 1 < table> 2 < thead> 3 < tr class="header"> 4 < th>Syntax</th> 5 < th>Description</th> 6 </tr> 7 </thead> 8 < tbody> 9 < tr class="odd"> 10 < td>Header</td> 11 < td>Title</td> 12 </tr> 13 < tr class="even"> 14 < td>Paragraph</td> 15 < td>Text</td>  Extended Syntax 41 16 </tr> 17 </tbody> 18 </table> The rendered output looks like this: Syntax Description Header Title Paragraph Text Cell widths can vary, as shown below. The rendered output will look the same. Markdown 1 | Syntax | Description | 2 | --- | ----------- | 3 | Header | Title | 4 | Paragraph | Text | Creating tables with hyphens and pipes can be tedious. To speed up the process, try using the [Markdown Tables Generator](http://www.tablesgenerator.com/markdown_tables). Build a table using the graphical interface, and then copy the generated Markdown-formatted text into your file. Alignment You can align text in the columns to the left, right, or center by adding a colon (:) to the left, right, or on both side of the hyphens within the header row. Extended Syntax 42 Markdown 1 | Syntax | Description | Test Text | 2 | :--- | :----: | \---: | 3 | Header | Title | Here's this | 4 | Paragraph | Text | And more | HTML 1 < table> 2 < thead> 3 < tr class="header"> 4 < th style="text-align: left;">Syntax</th> 5 < th style="text-align: center;">Description</th> 6 < th style="text-align: right;">Test Text</th> 7 </tr> 8 </thead> 9 < tbody> 10 < tr class="odd"> 11 < td style="text-align: left;">Header</td> 12 < td style="text-align: center;">Title</td> 13 < td style="text-align: right;">Here’s this</td> 14 </tr> 15 < tr class="even"> 16 < td style="text-align: left;">Paragraph</td> 17 < td style="text-align: center;">Text</td> 18 < td style="text-align: right;">And more</td> 19 </tr> 20 </tbody> 21 </table> The rendered output looks like this: Syntax Description Test Text Header Title Here’s this Paragraph Text And more Extended Syntax 43 Formatting Text in Tables You can format the text within tables. For example, you can add [links, ](#id_p41)[code ](#id_p39)(words or phrases in tick marks (`) only, not [code blocks](#id_p40)), and [emphasis. ](#id_p25) You can’t add headings, blockquotes, lists, horizontal rules, images, or HTML tags. Escaping Pipe Characters in Tables You can display a pipe (|) character in a table by using its HTML character code (&#124;). Fenced Code Blocks The basic Markdown syntax allows you to create [code blocks ](#id_p40)by indenting lines by four spaces or one tab. If you find that inconvenient, try using fenced code blocks. Depending on your Markdown processor or editor, you’ll use three tick marks (```) or three tildes ( ∼∼∼) on the lines before and after the code block. The best part? You don’t have to indent any lines! Markdown 1 ``` 2 { 3 "firstName": "John", 4 "lastName": "Smith", 5 "age": 25 6 } 7 ```  Extended Syntax 44 HTML 1 < pre> 2 < code> 3 { 4 &quot; firstName&quot; : &quot; John&quot; , 5 &quot; lastName&quot; : &quot; Smith&quot; , 6 &quot; age&quot; : 25 7 } 8 </code> 9 </pre> The rendered output looks like this: 1 { 2 "firstName": "John", 3 "lastName": "Smith", 4 "age": 25 5 } Need to display tick marks inside a code block? See [this section ](#id_p39)to learn how to escape them. Syntax Highlighting Many Markdown processors support syntax highlighting for fenced code blocks. This feature allows you to add color highlighting for whatever language your code was written in. To add syntax highlighting, specify a language next to the tick marks before the fenced code block. Extended Syntax 45 Markdown 1 ```json 2 { 3 "firstName": "John", 4 "lastName": "Smith", 5 "age": 25 6 } 7 ``` HTML 1 < pre> 2 < code class="language-json"> 3 { 4 &quot; firstName&quot; : &quot; John&quot; , 5 &quot; lastName&quot; : &quot; Smith&quot; , 6 &quot; age&quot; : 25 7 } 8 </code> 9 </pre> The rendered output looks like this: 1 { 2 "firstName" : "John", 3 "lastName" : "Smith", 4 "age" : 25 5 } Footnotes Footnotes allow you to add notes and references without cluttering the body of the document. When you create a footnote, a superscript number with a link appears Extended Syntax 46 where you added the footnote reference. Readers can click the link to jump to the content of the footnote at the bottom of the page. To create a footnote reference, add a caret and an identifier inside brackets (\[^1\]). Identifiers can be numbers or words, but they can’t contain spaces or tabs. Identifiers only correlate the footnote reference with the footnote itself — in the output, footnotes are numbered sequentially. Add the footnote using another caret and number inside brackets with a colon and text (\[^1\]: My footnote.). You don’t have to put footnotes at the end of the document. You can put them anywhere except inside other elements like lists, block quotes, and tables. Markdown 1 Here's a simple footnote,\[^1\] and here's a longer one.\[^bignote\] 2 3 \[^1\]: This is the first footnote. 4 5 \[^bignote\]: Here's one with multiple paragraphs and code. 6 7 Indent paragraphs to include them in the footnote. 8 9 `{ my code }` 10 11 Add as many paragraphs as you like. HTML 1 < p> 2 Here’s a simple footnote,< a href="#fn1" class="footnote-ref" id="fnre\\ 3 f1">< sup>1</sup></a> and here’s a longer one.< a href="#fn2" class="foot\\ 4 note-ref" id="fnref2">< sup>2</sup></a> 5 </p> 6 < section class="footnotes"> 7 < hr /> 8 < ol> 9 < li id="fn1">< p>This is the first footnote.< a href="#fnref1" class=\\ Extended Syntax 47 10 "footnote-back"> &#8617;&#xFE0E; </a></p></li> 11 < li id="fn2"> 12 < p>Here’s one with multiple paragraphs and code.</p> 13 < p>Indent paragraphs to include them in the footnote.</p> 14 < p>< code>{ my code }</code></p> 15 < p>Add as many paragraphs as you like.< a href="#fnref2" class="fo\\ 16 otnote-back"> &#8617;&#xFE0E; </a></p> 17 </li> 18 </ol> 19 </section> The rendered output looks like this: Here’s a simple footnote[,¹ ](#id_p57)and here’s a longer one[.²](#id_p57) Heading IDs Many Markdown processors support custom IDs for [headings ](#id_p23)— some Markdown processors automatically add them. Adding custom IDs allows you to link directly to headings and modify them with CSS. To add a custom heading ID, enclose the custom ID in curly braces on the same line as the heading. Markdown 1 \### My Great Heading {#custom-id} HTML 1 < h3 id="custom-id">My Great Heading</h3> ¹This is the first footnote. ²Here’s one with multiple paragraphs and code. Indent paragraphs to include them in the footnote. { my code } Add as many paragraphs as you like. Extended Syntax 48 Linking to Heading IDs You can link to headings with custom IDs in the file by creating a [standard link ](#id_p41)with a number sign (#) followed by the custom heading ID. Markdown 1 \[Heading IDs\](#heading-ids) HTML 1 < a href="#heading-ids">Heading IDs</a> Other websites can link to the heading by adding the custom heading ID to the full URL of the webpage (e.g, \[Heading IDs\](https://www.eff.org/page#heading-ids)). Definition Lists Some Markdown processors allow you to create definition lists of terms and their corresponding definitions. To create a definition list, type the term on the first line. On the next line, type a colon followed by a space and the definition. Markdown 1 First Term 2 : This is the definition of the first term. 3 4 Second Term 5 : This is one definition of the second term. 6 : This is another definition of the second term. Extended Syntax 49 HTML 1 < dl> 2 < dt>First Term</dt> 3 < dd>This is the definition of the first term.</dd> 4 < dt>Second Term</dt> 5 < dd>This is one definition of the second term. </dd> 6 < dd>This is another definition of the second term.</dd> 7 </dl> The rendered output looks like this: First Term This is the definition of the first term. Second Term This is one definition of the second term. This is another definition of the second term. Strikethrough You can “strikethrough” words by putting a horizontal line through the center of them. This feature allows you to indicate that certain words are a mistake not meant for inclusion in the document. To strikethrough words, use two tilde symbols ( ∼∼) before and after the words. Markdown 1 The world is ~~flat~~ round. HTML 1 < p>The world is < del>flat</del> round.</p> The rendered output looks like this: The world is flat round.  Extended Syntax 50 Task Lists Task lists allow you to create a list of items with checkboxes. In Markdown applications that support task lists, checkboxes will be displayed next to the content. To create a task list, add dashes (-) and brackets with a space (\[ \]) in front of task list items. To select a checkbox, add an x in between the brackets (\[x\]). Markdown 1 \- \[x\] Write the press release 2 \- \[ \] Update the website 3 \- \[ \] Contact the media The rendered output looks like this: Task list Automatic URL Linking Many Markdown processors automatically turn URLs into links. That means if you type http://www.example.com, your Markdown processor will automatically turn it into a link even though you haven’t [used brackets. ](#id_p41) Markdown 1 http://example.com Extended Syntax 51 HTML 1 < a href="http://example.com">http://example.com</a> The rendered output looks like this: <http://example.com> Disabling Automatic URL Linking If you don’t want a URL to be automatically linked, you can remove the link by [denoting the URL as code ](#id_p39)with tick marks. Markdown 1 `http://www.example.com` HTML 1 < code>http://www.example.com</code> The rendered output looks like this: http://www.example.com 5\. Cheat Sheet This cheat sheet provides a quick overview of all the Markdown syntax elements. It can’t cover every edge case! If you need more information about any of these elements, refer back to the chapters on [basic ](#id_p23)and [extended syntax](#id_p49). Basic Syntax These are the elements outlined in John Gruber’s original design document. All Markdown applications support these elements. Element Markdown Syntax [Heading](#id_p23) \# H1 \## H2 \### H3 [Bold](#id_p25) \*\*bold text\*\* [Italic](#id_p26) \*italicized text\* [Blockquote](#id_p27) \> blockquote [Ordered List](#id_p30) 1\. First item 2\. Second item 3\. Third item [Unordered List](#id_p32) \- First item \- Second item \- Third item [Code](#id_p39) `codè [Horizontal Rule](#id_p41) \--- [Link](#id_p41) \[title\](https://www.example.com) [Image](#id_p46) !\[alt text\](image.jpg) Cheat Sheet 53 Extended Syntax These elements extend the basic syntax by adding additional features. Not all Markdown applications support these elements. Element Markdown Syntax [Table](#id_p50) | Syntax | Description | | ------ | ----------- | | Header | Title | | Paragraph | Text | [Fenced Code Block](#id_p53) ``` { "firstName": "John", "lastName": "Smith", "age": 25 } ``` [Footnote](#id_p55) Here's a sentence with a footnote. \[^1\] \[^1\]: This is the footnote. [Heading ID](#id_p57) \### My Great Heading {#custom-id} [Definition List](#id_p58) term : definition [Strikethrough](#id_p59) ∼∼ The world is flat. ∼∼ [Task List](#id_p59) \- \[x\] Write the press release \- \[ \] Update the website \- \[ \] Contact the media About the Author Matt Cone is a technical writer at [Fastly. ](https://www.fastly.com/)He has experience creating documentation for organizations like Linode and the U.S. Department of Health and Human Services. Matt’s first book, [ ](https://www.amazon.com/Master-Your-Mac-Simple-Customize/dp/1593274068/)[Master Your Mac](https://www.amazon.com/Master-Your-Mac-Simple-Customize/dp/1593274068/)[, ](https://www.amazon.com/Master-Your-Mac-Simple-Customize/dp/1593274068/)was published by No Starch Press. To get in touch with Matt, visit [http://mattcone.com. ](http://mattcone.com) # Document Outline - [Table of Contents](#id_p4) - [Introduction](#id_p7) - [Where to Get This Book](#id_p8) - [How to Read This Book](#id_p8) - [Beginner Resources](#id_p8) - [Syntax Examples](#id_p8) - [Asides](#id_p9) - [Quirks](#id_p9) - [Contributing](#id_p9) - [Reporting Issues](#id_p10) - [Acknowledgements](#id_p10) - [Getting Started](#id_p11) - [Why Use Markdown? ](#id_p12) - [Kicking the Tires](#id_p13) - [How Markdown Works](#id_p14) - [Flavors of Markdown](#id_p17) - [Additional Resources](#id_p17) - [Doing Things With Markdown](#id_p19) - [Websites](#id_p19) - [Documents](#id_p20) - [Notes](#id_p20) - [Books](#id_p21) - [Presentations](#id_p21) - [Email](#id_p21) - [Documentation](#id_p22) - [Basic Syntax](#id_p23) - [Headings](#id_p23) - [Alternate Syntax](#id_p23) - [Paragraphs](#id_p24) - [Line Breaks](#id_p24) - [Emphasis](#id_p25) - [Bold](#id_p25) - [Italic](#id_p26) - [Bold and Italic](#id_p27) - [Blockquotes](#id_p27) - [Blockquotes with Multiple Paragraphs](#id_p28) - [Nested Blockquotes](#id_p28) - [Blockquotes with Other Elements](#id_p29) - [Lists](#id_p30) - [Ordered Lists](#id_p30) - [Unordered Lists](#id_p32) - [Adding Elements in Lists](#id_p34) - [Code](#id_p39) - [Escaping Tick Marks](#id_p39) - [Code Blocks](#id_p40) - [Horizontal Rules](#id_p41) - [Links](#id_p42) - [Adding Titles](#id_p42) - [URLs and Email Addresses](#id_p42) - [Formatting Links](#id_p43) - [Reference-style Links](#id_p43) - [Images](#id_p46) - [Escaping Characters](#id_p47) - [Characters You Can Escape](#id_p48) - [Extended Syntax](#id_p49) - [Availability](#id_p49) - [Lightweight Markup Languages](#id_p49) - [Markdown Processors](#id_p50) - [Tables](#id_p50) - [Alignment](#id_p51) - [Formatting Text in Tables](#id_p53) - [Escaping Pipe Characters in Tables](#id_p53) - [Fenced Code Blocks](#id_p53) - [Syntax Highlighting](#id_p54) - [Footnotes](#id_p55) - [Heading IDs](#id_p57) - [Linking to Heading IDs](#id_p58) - [Definition Lists](#id_p58) - [Strikethrough](#id_p59) - [Task Lists](#id_p60) - [Automatic URL Linking](#id_p60) - [Disabling Automatic URL Linking](#id_p61) - [Cheat Sheet](#id_p62) - [Basic Syntax](#id_p62) - [Extended Syntax](#id_p62) - [About the Author](#id_p64)