![\"example](\"https://www.getpostman.com/img/v2/logo-big.svg\"){kind=logo}
This collection is intended to test markdown styling inside Postman or within other services that render Markdown. The descriptions in this collection contain markdown syntax and some of them have links to HTML pages of their rendered version.
\nIf you want to test Markdown, use http://markdownlivepreview.com/
\nAlso, developers love Github Markdown Styling: https://github.com/sindresorhus/github-markdown-css
\nParagraphs are separated by a blank line.
\n2nd paragraph. Italic, bold, and monospace. Itemized lists\nlook like:
Note that --- not considering the asterisk --- the actual text\ncontent starts at 4-columns in.
\n\n\nBlock quotes are\nwritten like so.
\nThey can span multiple paragraphs,\nif you like.
\n
Use 3 dashes for an em-dash. Use 2 dashes for ranges (ex., \"it's all\nin chapters 12--14\"). Three dots ... will be converted to an ellipsis.\nUnicode is supported. ☺
\nHere's a numbered list:
\nNote again how the actual text starts at 4 columns in (4 characters\nfrom the left side). Here's a code sample:
\n# Let me re-iterate ...\nfor i in 1 .. 10 { do-something(i) }\nAs you probably guessed, indented 4 spaces. By the way, instead of\nindenting the block, you can use delimited blocks, if you like:
\ndefine foobar() {\n print \"Welcome to flavor country!\";\n}\n(which makes copying & pasting easier). You can optionally mark the\ndelimited block for Pandoc to syntax highlight it:
\nimport time\n# Quick, count to ten!\nfor i in range(10):\n # (but not *too* quick)\n time.sleep(0.5)\n print i\nNow a nested list:
\nFirst, get these ingredients:
\nBoil some water.
\nDump everything in the pot and follow\nthis algorithm:
\nfind wooden spoon\nuncover pot\nstir\ncover pot\nbalance wooden spoon precariously on pot handle\nwait 10 minutes\ngoto first step (or shut off burner when done)\nDo not bump wooden spoon or it will fall.
\nNotice again how text always lines up on 4-space indents (including\nthat last line which continues item 3 above).
\nHere's a link to a website, to a local\ndoc, and to a section heading in the current\ndoc. Here's a footnote [^1].
\n[^1]: Footnote text goes here.
\nTables can look like this:
\nsize material color
\n9 leather brown\n10 hemp canvas natural\n11 glass transparent
\nTable: Shoes, their sizes, and what they're made of
\n(The above is the caption for the table.) Pandoc also supports\nmulti-line tables:
\nkeyword text
\nred Sunsets, apples, and\n other red or reddish\n things.
\ngreen Leaves, grass, frogs\n and other things it's\n not easy being.
\nA horizontal rule follows.
\nHere's a definition list:
\napples\n : Good for making applesauce.\noranges\n : Citrus!\ntomatoes\n : There's no \"e\" in tomatoe.
\nAgain, text is indented 4 spaces. (Put a blank line between each\nterm/definition pair to spread things out more.)
\nHere's a \"line block\":
\n| Line one\n| Line too\n| Line tree
\nand images can be specified like so:
\n
Inline math equations go in like so: $\\omega = d\\phi / dt$. Display\nmath should get its own line and be put in in double-dollarsigns:
\n$$I = \\int \\rho R^{2} dV$$
\nAnd note that you can backslash-escape any punctuation characters\nwhich you wish to be displayed literally, ex.: `foo`, *bar*, etc.
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[{"content":"An h1 header","slug":"an-h1-header"}],"owner":"33232","collectionId":"8e60b36b-8125-cd42-61e3-5a0253ca558f","publishedId":"JsGc","public":true,"customColor":null,"publishDate":"2016-05-25T10:05:59.000Z"},"item":[{"name":"Basic Markdown Elements","item":[],"id":"1e3733d8-5f20-ae03-b175-6e25a2b8595d","description":"Any bar stool can graduate from a skinny Rolling Rock, but it takes a real Hommel Bier to wastedly caricature a surly polar bear beer. A Red Stripe, the Jamaica Red Ale, and the incinerated burglar ale are what made America great!
\nThis section has an inline code followed by a multiline code block which should look similar to the inline code, except that it is a panel-like block.
The funny Brewers Reserve self-flagellates, and the green pit viper wakes up; however, an Avery IPA makes love to a soggy Honey Brown.\nSometimes a salty black velvet takes a coffee break, but a dirt-encrusted Luna Sea ESB always caricatures the bud light! A Heineken inside some Jamaica Red Ale sanitizes the flatulent Pilsner.
\n\n\nThis is a Block Quote. Should look like a panel. When another bottle of beer for another Ellis Island IPA is whacked, a freight train bestows great honor upon some fat lager. The pin ball machine from some Dos Equis eats the precise coors light.
\n
A blood clot is raspy. A satellite brewery about the Brewers Reserve starts reminiscing about a lost buzz, and the polka-dotted Busch bestows great honor upon the Hops Alligator Ale from the lager. The dorky pool table secretly admires a tooled miller. The gratifying keg hesitantly pees on a bud light from a Guiness.
\nWhen the crank case from a Dixie Beer daydreams, a college-educated Fosters wakes up. A Miller beyond the satellite brewery reads a magazine, but a so-called satellite brewery borrows money from a tanked burglar ale. Most people believe that the Hefeweizen from some Sierra Nevada throws a seldom financial scooby snack at the pompous Christmas Ale, but they need to remember how hardly a Heineken behind the bar tab ruminates. If the PBR inside another Busch cooks cheese grits for the miserly air hocky table, then the college-educated Brewers Reserve starts reminiscing about a lost buzz. A Sierra Nevada Pale Ale inside a Busch is hairy.
\nA Rolling Rock for a bull ice operates a small bar with the bud dry about a change. Any Keystone can make a pact with the Mango Beer around a blue moon, but it takes a real PBR to pee on the treacherous Keystone. A miller toward the IPA secretly admires an Octoberfest. A Bridgeport ESB beyond another burglar ale eats the Sierra Nevada Pale Ale related to a Pilsner.
\n\n\nSingle line block quote
\n
\n\n","event":[{"listen":"prerequest","script":{"id":"1e547121-fdbf-41c3-b395-c9d6678fa7ac","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"e62bd284-cb4d-4791-a086-d1005b328fe4","type":"text/javascript","exec":[""]}}],"_postman_id":"1e3733d8-5f20-ae03-b175-6e25a2b8595d"},{"name":"Daring Fireball Basic Syntax","item":[],"id":"ec6be041-62f8-9442-db96-873d069f7787","description":"Multi line\nblock quote
\n
This generates the HTML: http://daringfireball.net/projects/markdown/basics
\nThis page offers a brief overview of what it's like to use Markdown.\nThe [syntax page] s provides complete, detailed documentation for\nevery feature, but Markdown should be very easy to pick up simply by\nlooking at a few examples of it in action. The examples on this page\nare written in a before/after style, showing example syntax and the\nHTML output produced by Markdown.
\nIt's also helpful to simply try Markdown out; the [Dingus] d is a\nweb application that allows you type your own Markdown-formatted text\nand translate it to XHTML.
\nNote: This document is itself written using Markdown; you\ncan [see the source for it by adding '.text' to the URL] src.
\nA paragraph is simply one or more consecutive lines of text, separated\nby one or more blank lines. (A blank line is any line that looks like\na blank line -- a line containing nothing but spaces or tabs is\nconsidered blank.) Normal paragraphs should not be indented with\nspaces or tabs.
\nMarkdown offers two styles of headers: Setext and atx.\nSetext-style headers for <h1> and <h2> are created by\n\"underlining\" with equal signs (=) and hyphens (-), respectively.\nTo create an atx-style header, you put 1-6 hash marks (#) at the\nbeginning of the line -- the number of hashes equals the resulting\nHTML header level.
Blockquotes are indicated using email-style '>' angle brackets.
Markdown:
\nA First Level Header\n====================\n\nA Second Level Header\n---------------------\n\nNow is the time for all good men to come to\nthe aid of their country. This is just a\nregular paragraph.\n\nThe quick brown fox jumped over the lazy\ndog's back.\n\n### Header 3\n\n> This is a blockquote.\n> \n> This is the second paragraph in the blockquote.\n>\n> ## This is an H2 in a blockquote\nOutput:
\n<h1>A First Level Header</h1>\n\n<h2>A Second Level Header</h2>\n\n<p>Now is the time for all good men to come to\nthe aid of their country. This is just a\nregular paragraph.</p>\n\n<p>The quick brown fox jumped over the lazy\ndog's back.</p>\n\n<h3>Header 3</h3>\n\n<blockquote>\n <p>This is a blockquote.</p>\n \n <p>This is the second paragraph in the blockquote.</p>\n \n <h2>This is an H2 in a blockquote</h2>\n</blockquote>\nMarkdown uses asterisks and underscores to indicate spans of emphasis.
\nMarkdown:
\nSome of these words *are emphasized*.\nSome of these words _are emphasized also_.\n\nUse two asterisks for **strong emphasis**.\nOr, if you prefer, __use two underscores instead__.\nOutput:
\n<p>Some of these words <em>are emphasized</em>.\nSome of these words <em>are emphasized also</em>.</p>\n\n<p>Use two asterisks for <strong>strong emphasis</strong>.\nOr, if you prefer, <strong>use two underscores instead</strong>.</p>\nUnordered (bulleted) lists use asterisks, pluses, and hyphens (*,\n+, and -) as list markers. These three markers are\ninterchangable; this:
* Candy.\n* Gum.\n* Booze.\nthis:
\n+ Candy.\n+ Gum.\n+ Booze.\nand this:
\n- Candy.\n- Gum.\n- Booze.\nall produce the same output:
\n<ul>\n<li>Candy.</li>\n<li>Gum.</li>\n<li>Booze.</li>\n</ul>\nOrdered (numbered) lists use regular numbers, followed by periods, as\nlist markers:
\n1. Red\n2. Green\n3. Blue\nOutput:
\n<ol>\n<li>Red</li>\n<li>Green</li>\n<li>Blue</li>\n</ol>\nIf you put blank lines between items, you'll get <p> tags for the\nlist item text. You can create multi-paragraph list items by indenting\nthe paragraphs by 4 spaces or 1 tab:
* A list item.\n\n With multiple paragraphs.\n\n* Another item in the list.\nOutput:
\n<ul>\n<li><p>A list item.</p>\n<p>With multiple paragraphs.</p></li>\n<li><p>Another item in the list.</p></li>\n</ul>\nMarkdown supports two styles for creating links: inline and\nreference. With both styles, you use square brackets to delimit the\ntext you want to turn into a link.
\nInline-style links use parentheses immediately after the link text.\nFor example:
\nThis is an [example link](http://example.com/).\nOutput:
\n<p>This is an <a href=\"http://example.com/\">\nexample link</a>.</p>\nOptionally, you may include a title attribute in the parentheses:
\nThis is an [example link](http://example.com/ \"With a Title\").\nOutput:
\n<p>This is an <a href=\"http://example.com/\" title=\"With a Title\">\nexample link</a>.</p>\nReference-style links allow you to refer to your links by names, which\nyou define elsewhere in your document:
\nI get 10 times more traffic from [Google][1] than from\n[Yahoo][2] or [MSN][3].\n\n[1]: http://google.com/ \"Google\"\n[2]: http://search.yahoo.com/ \"Yahoo Search\"\n[3]: http://search.msn.com/ \"MSN Search\"\nOutput:
\n<p>I get 10 times more traffic from <a href=\"http://google.com/\"\ntitle=\"Google\">Google</a> than from <a href=\"http://search.yahoo.com/\"\ntitle=\"Yahoo Search\">Yahoo</a> or <a href=\"http://search.msn.com/\"\ntitle=\"MSN Search\">MSN</a>.</p>\nThe title attribute is optional. Link names may contain letters,\nnumbers and spaces, but are not case sensitive:
\nI start my morning with a cup of coffee and\n[The New York Times][NY Times].\n\n[ny times]: http://www.nytimes.com/\nOutput:
\n<p>I start my morning with a cup of coffee and\n<a href=\"http://www.nytimes.com/\">The New York Times</a>.</p>\nImage syntax is very much like link syntax.
\nInline (titles are optional):
\n![alt text](/path/to/img.jpg \"Title\")\nReference-style:
\n![alt text][id]\n\n[id]: /path/to/img.jpg \"Title\"\nBoth of the above examples produce the same output:
\n<img src=\"/path/to/img.jpg\" alt=\"alt text\" title=\"Title\" />\nIn a regular paragraph, you can create code span by wrapping text in\nbacktick quotes. Any ampersands (&) and angle brackets (< or\n>) will automatically be translated into HTML entities. This makes\nit easy to use Markdown to write about HTML example code:
I strongly recommend against using any `<blink>` tags.\n\nI wish SmartyPants used named entities like `—`\ninstead of decimal-encoded entites like `—`.\nOutput:
\n<p>I strongly recommend against using any\n<code><blink></code> tags.</p>\n\n<p>I wish SmartyPants used named entities like\n<code>&mdash;</code> instead of decimal-encoded\nentites like <code>&#8212;</code>.</p>\nTo specify an entire block of pre-formatted code, indent every line of\nthe block by 4 spaces or 1 tab. Just like with code spans, &, <,\nand > characters will be escaped automatically.
Markdown:
\nIf you want your page to validate under XHTML 1.0 Strict,\nyou've got to put paragraph tags in your blockquotes:\n\n <blockquote>\n <p>For example.</p>\n </blockquote>\nOutput:
\n<p>If you want your page to validate under XHTML 1.0 Strict,\nyou've got to put paragraph tags in your blockquotes:</p>\n\n<pre><code><blockquote>\n <p>For example.</p>\n</blockquote>\n</code></pre>\nThis is the source of the page:\nhttp://daringfireball.net/projects/markdown/syntax
\nNote: This document is itself written using Markdown; you\ncan see the source for it by adding '.text' to the URL.
\nMarkdown is intended to be as easy-to-read and easy-to-write as is feasible.
\nReadability, however, is emphasized above all else. A Markdown-formatted\ndocument should be publishable as-is, as plain text, without looking\nlike it's been marked up with tags or formatting instructions. While\nMarkdown's syntax has been influenced by several existing text-to-HTML\nfilters -- including [Setext] 1, [atx] 2, [Textile] 3, [reStructuredText] 4,\n[Grutatext] 5, and [EtText] 6 -- the single biggest source of\ninspiration for Markdown's syntax is the format of plain text email.
\nTo this end, Markdown's syntax is comprised entirely of punctuation\ncharacters, which punctuation characters have been carefully chosen so\nas to look like what they mean. E.g., asterisks around a word actually\nlook like *emphasis*. Markdown lists look like, well, lists. Even\nblockquotes look like quoted passages of text, assuming you've ever\nused email.
\nMarkdown's syntax is intended for one purpose: to be used as a\nformat for writing for the web.
\nMarkdown is not a replacement for HTML, or even close to it. Its\nsyntax is very small, corresponding only to a very small subset of\nHTML tags. The idea is not to create a syntax that makes it easier\nto insert HTML tags. In my opinion, HTML tags are already easy to\ninsert. The idea for Markdown is to make it easy to read, write, and\nedit prose. HTML is a publishing format; Markdown is a writing\nformat. Thus, Markdown's formatting syntax only addresses issues that\ncan be conveyed in plain text.
\nFor any markup that is not covered by Markdown's syntax, you simply\nuse HTML itself. There's no need to preface it or delimit it to\nindicate that you're switching from Markdown to HTML; you just use\nthe tags.
\nThe only restrictions are that block-level HTML elements -- e.g. <div>,\n<table>, <pre>, <p>, etc. -- must be separated from surrounding\ncontent by blank lines, and the start and end tags of the block should\nnot be indented with tabs or spaces. Markdown is smart enough not\nto add extra (unwanted) <p> tags around HTML block-level tags.
For example, to add an HTML table to a Markdown article:
\nThis is a regular paragraph.\n\n<table>\n <tr>\n <td>Foo</td>\n </tr>\n</table>\n\nThis is another regular paragraph.\nNote that Markdown formatting syntax is not processed within block-level\nHTML tags. E.g., you can't use Markdown-style *emphasis* inside an\nHTML block.
Span-level HTML tags -- e.g. <span>, <cite>, or <del> -- can be\nused anywhere in a Markdown paragraph, list item, or header. If you\nwant, you can even use HTML tags instead of Markdown formatting; e.g. if\nyou'd prefer to use HTML <a> or <img> tags instead of Markdown's\nlink or image syntax, go right ahead.
Unlike block-level HTML tags, Markdown syntax is processed within\nspan-level tags.
\nIn HTML, there are two characters that demand special treatment: <\nand &. Left angle brackets are used to start tags; ampersands are\nused to denote HTML entities. If you want to use them as literal\ncharacters, you must escape them as entities, e.g. <, and\n&.
Ampersands in particular are bedeviling for web writers. If you want to\nwrite about 'AT&T', you need to write 'AT&T'. You even need to\nescape ampersands within URLs. Thus, if you want to link to:
http://images.google.com/images?num=30&q=larry+bird\nyou need to encode the URL as:
\nhttp://images.google.com/images?num=30&q=larry+bird\nin your anchor tag href attribute. Needless to say, this is easy to\nforget, and is probably the single most common source of HTML validation\nerrors in otherwise well-marked-up web sites.
Markdown allows you to use these characters naturally, taking care of\nall the necessary escaping for you. If you use an ampersand as part of\nan HTML entity, it remains unchanged; otherwise it will be translated\ninto &.
So, if you want to include a copyright symbol in your article, you can write:
\n©\nand Markdown will leave it alone. But if you write:
\nAT&T\nMarkdown will translate it to:
\nAT&T\nSimilarly, because Markdown supports inline HTML, if you use\nangle brackets as delimiters for HTML tags, Markdown will treat them as\nsuch. But if you write:
\n4 < 5\nMarkdown will translate it to:
\n4 < 5\nHowever, inside Markdown code spans and blocks, angle brackets and\nampersands are always encoded automatically. This makes it easy to use\nMarkdown to write about HTML code. (As opposed to raw HTML, which is a\nterrible format for writing about HTML syntax, because every single <\nand & in your example code needs to be escaped.)
A paragraph is simply one or more consecutive lines of text, separated\nby one or more blank lines. (A blank line is any line that looks like a\nblank line -- a line containing nothing but spaces or tabs is considered\nblank.) Normal paragraphs should not be indented with spaces or tabs.
\nThe implication of the \"one or more consecutive lines of text\" rule is\nthat Markdown supports \"hard-wrapped\" text paragraphs. This differs\nsignificantly from most other text-to-HTML formatters (including Movable\nType's \"Convert Line Breaks\" option) which translate every line break\ncharacter in a paragraph into a <br /> tag.
When you do want to insert a <br /> break tag using Markdown, you\nend a line with two or more spaces, then type return.
Yes, this takes a tad more effort to create a <br />, but a simplistic\n\"every line break is a <br />\" rule wouldn't work for Markdown.\nMarkdown's email-style blockquoting and multi-paragraph list items\nwork best -- and look better -- when you format them with hard breaks.
Markdown supports two styles of headers, [Setext] 1 and [atx] 2.
\nSetext-style headers are \"underlined\" using equal signs (for first-level\nheaders) and dashes (for second-level headers). For example:
\nThis is an H1\n=============\n\nThis is an H2\n-------------\nAny number of underlining ='s or -'s will work.
Atx-style headers use 1-6 hash characters at the start of the line,\ncorresponding to header levels 1-6. For example:
\n# This is an H1\n\n## This is an H2\n\n###### This is an H6\nOptionally, you may \"close\" atx-style headers. This is purely\ncosmetic -- you can use this if you think it looks better. The\nclosing hashes don't even need to match the number of hashes\nused to open the header. (The number of opening hashes\ndetermines the header level.) :
\n# This is an H1 #\n\n## This is an H2 ##\n\n### This is an H3 ######\nMarkdown uses email-style > characters for blockquoting. If you're\nfamiliar with quoting passages of text in an email message, then you\nknow how to create a blockquote in Markdown. It looks best if you hard\nwrap the text and put a > before every line:
> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,\n> consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.\n> Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.\n> \n> Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse\n> id sem consectetuer libero luctus adipiscing.\nMarkdown allows you to be lazy and only put the > before the first\nline of a hard-wrapped paragraph:
> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,\nconsectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.\nVestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.\n\n> Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse\nid sem consectetuer libero luctus adipiscing.\nBlockquotes can be nested (i.e. a blockquote-in-a-blockquote) by\nadding additional levels of >:
> This is the first level of quoting.\n>\n> > This is nested blockquote.\n>\n> Back to the first level.\nBlockquotes can contain other Markdown elements, including headers, lists,\nand code blocks:
\n> ## This is a header.\n> \n> 1. This is the first list item.\n> 2. This is the second list item.\n> \n> Here's some example code:\n> \n> return shell_exec(\"echo $input | $markdown_script\");\nAny decent text editor should make email-style quoting easy. For\nexample, with BBEdit, you can make a selection and choose Increase\nQuote Level from the Text menu.
\nMarkdown supports ordered (numbered) and unordered (bulleted) lists.
\nUnordered lists use asterisks, pluses, and hyphens -- interchangably\n-- as list markers:
\n* Red\n* Green\n* Blue\nis equivalent to:
\n+ Red\n+ Green\n+ Blue\nand:
\n- Red\n- Green\n- Blue\nOrdered lists use numbers followed by periods:
\n1. Bird\n2. McHale\n3. Parish\nIt's important to note that the actual numbers you use to mark the\nlist have no effect on the HTML output Markdown produces. The HTML\nMarkdown produces from the above list is:
\n<ol>\n<li>Bird</li>\n<li>McHale</li>\n<li>Parish</li>\n</ol>\nIf you instead wrote the list in Markdown like this:
\n1. Bird\n1. McHale\n1. Parish\nor even:
\n3. Bird\n1. McHale\n8. Parish\nyou'd get the exact same HTML output. The point is, if you want to,\nyou can use ordinal numbers in your ordered Markdown lists, so that\nthe numbers in your source match the numbers in your published HTML.\nBut if you want to be lazy, you don't have to.
\nIf you do use lazy list numbering, however, you should still start the\nlist with the number 1. At some point in the future, Markdown may support\nstarting ordered lists at an arbitrary number.
\nList markers typically start at the left margin, but may be indented by\nup to three spaces. List markers must be followed by one or more spaces\nor a tab.
\nTo make lists look nice, you can wrap items with hanging indents:
\n* Lorem ipsum dolor sit amet, consectetuer adipiscing elit.\n Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,\n viverra nec, fringilla in, laoreet vitae, risus.\n* Donec sit amet nisl. Aliquam semper ipsum sit amet velit.\n Suspendisse id sem consectetuer libero luctus adipiscing.\nBut if you want to be lazy, you don't have to:
\n* Lorem ipsum dolor sit amet, consectetuer adipiscing elit.\nAliquam hendrerit mi posuere lectus. Vestibulum enim wisi,\nviverra nec, fringilla in, laoreet vitae, risus.\n* Donec sit amet nisl. Aliquam semper ipsum sit amet velit.\nSuspendisse id sem consectetuer libero luctus adipiscing.\nIf list items are separated by blank lines, Markdown will wrap the\nitems in <p> tags in the HTML output. For example, this input:
* Bird\n* Magic\nwill turn into:
\n<ul>\n<li>Bird</li>\n<li>Magic</li>\n</ul>\nBut this:
\n* Bird\n\n* Magic\nwill turn into:
\n<ul>\n<li><p>Bird</p></li>\n<li><p>Magic</p></li>\n</ul>\nList items may consist of multiple paragraphs. Each subsequent\nparagraph in a list item must be indented by either 4 spaces\nor one tab:
\n1. This is a list item with two paragraphs. Lorem ipsum dolor\n sit amet, consectetuer adipiscing elit. Aliquam hendrerit\n mi posuere lectus.\n\n Vestibulum enim wisi, viverra nec, fringilla in, laoreet\n vitae, risus. Donec sit amet nisl. Aliquam semper ipsum\n sit amet velit.\n\n2. Suspendisse id sem consectetuer libero luctus adipiscing.\nIt looks nice if you indent every line of the subsequent\nparagraphs, but here again, Markdown will allow you to be\nlazy:
\n* This is a list item with two paragraphs.\n\n This is the second paragraph in the list item. You're\nonly required to indent the first line. Lorem ipsum dolor\nsit amet, consectetuer adipiscing elit.\n\n* Another item in the same list.\nTo put a blockquote within a list item, the blockquote's >\ndelimiters need to be indented:
* A list item with a blockquote:\n\n > This is a blockquote\n > inside a list item.\nTo put a code block within a list item, the code block needs\nto be indented twice -- 8 spaces or two tabs:
\n* A list item with a code block:\n\n <code goes here>\nIt's worth noting that it's possible to trigger an ordered list by\naccident, by writing something like this:
\n1986. What a great season.\nIn other words, a number-period-space sequence at the beginning of a\nline. To avoid this, you can backslash-escape the period:
\n1986\\. What a great season.\nPre-formatted code blocks are used for writing about programming or\nmarkup source code. Rather than forming normal paragraphs, the lines\nof a code block are interpreted literally. Markdown wraps a code block\nin both <pre> and <code> tags.
To produce a code block in Markdown, simply indent every line of the\nblock by at least 4 spaces or 1 tab. For example, given this input:
\nThis is a normal paragraph:\n\n This is a code block.\nMarkdown will generate:
\n<p>This is a normal paragraph:</p>\n\n<pre><code>This is a code block.\n</code></pre>\nOne level of indentation -- 4 spaces or 1 tab -- is removed from each\nline of the code block. For example, this:
\nHere is an example of AppleScript:\n\n tell application \"Foo\"\n beep\n end tell\nwill turn into:
\n<p>Here is an example of AppleScript:</p>\n\n<pre><code>tell application \"Foo\"\n beep\nend tell\n</code></pre>\nA code block continues until it reaches a line that is not indented\n(or the end of the article).
\nWithin a code block, ampersands (&) and angle brackets (< and >)\nare automatically converted into HTML entities. This makes it very\neasy to include example HTML source code using Markdown -- just paste\nit and indent it, and Markdown will handle the hassle of encoding the\nampersands and angle brackets. For example, this:
<div class=\"footer\">\n © 2004 Foo Corporation\n </div>\nwill turn into:
\n<pre><code><div class=\"footer\">\n &copy; 2004 Foo Corporation\n</div>\n</code></pre>\nRegular Markdown syntax is not processed within code blocks. E.g.,\nasterisks are just literal asterisks within a code block. This means\nit's also easy to use Markdown to write about Markdown's own syntax.
\nYou can produce a horizontal rule tag (<hr />) by placing three or\nmore hyphens, asterisks, or underscores on a line by themselves. If you\nwish, you may use spaces between the hyphens or asterisks. Each of the\nfollowing lines will produce a horizontal rule:
* * *\n\n***\n\n*****\n\n- - -\n\n---------------------------------------\nMarkdown supports two style of links: inline and reference.
\nIn both styles, the link text is delimited by [square brackets].
\nTo create an inline link, use a set of regular parentheses immediately\nafter the link text's closing square bracket. Inside the parentheses,\nput the URL where you want the link to point, along with an optional\ntitle for the link, surrounded in quotes. For example:
\nThis is [an example](http://example.com/ \"Title\") inline link.\n\n[This link](http://example.net/) has no title attribute.\nWill produce:
\n<p>This is <a href=\"http://example.com/\" title=\"Title\">\nan example</a> inline link.</p>\n\n<p><a href=\"http://example.net/\">This link</a> has no\ntitle attribute.</p>\nIf you're referring to a local resource on the same server, you can\nuse relative paths:
\nSee my [About](/about/) page for details. \nReference-style links use a second set of square brackets, inside\nwhich you place a label of your choosing to identify the link:
\nThis is [an example][id] reference-style link.\nYou can optionally use a space to separate the sets of brackets:
\nThis is [an example] [id] reference-style link.\nThen, anywhere in the document, you define your link label like this,\non a line by itself:
\n[id]: http://example.com/ \"Optional Title Here\"\nThat is:
\nThe following three link definitions are equivalent:
\n[foo]: http://example.com/ \"Optional Title Here\"\n[foo]: http://example.com/ 'Optional Title Here'\n[foo]: http://example.com/ (Optional Title Here)\nNote: There is a known bug in Markdown.pl 1.0.1 which prevents\nsingle quotes from being used to delimit link titles.
\nThe link URL may, optionally, be surrounded by angle brackets:
\n[id]: <http://example.com/> \"Optional Title Here\"\nYou can put the title attribute on the next line and use extra spaces\nor tabs for padding, which tends to look better with longer URLs:
\n[id]: http://example.com/longish/path/to/resource/here\n \"Optional Title Here\"\nLink definitions are only used for creating links during Markdown\nprocessing, and are stripped from your document in the HTML output.
\nLink definition names may consist of letters, numbers, spaces, and\npunctuation -- but they are not case sensitive. E.g. these two\nlinks:
\n[link text][a]\n[link text][A]\nare equivalent.
\nThe implicit link name shortcut allows you to omit the name of the\nlink, in which case the link text itself is used as the name.\nJust use an empty set of square brackets -- e.g., to link the word\n\"Google\" to the google.com web site, you could simply write:
\n[Google][]\nAnd then define the link:
\n[Google]: http://google.com/\nBecause link names may contain spaces, this shortcut even works for\nmultiple words in the link text:
\nVisit [Daring Fireball][] for more information.\nAnd then define the link:
\n[Daring Fireball]: http://daringfireball.net/\nLink definitions can be placed anywhere in your Markdown document. I\ntend to put them immediately after each paragraph in which they're\nused, but if you want, you can put them all at the end of your\ndocument, sort of like footnotes.
\nHere's an example of reference links in action:
\nI get 10 times more traffic from [Google] [1] than from\n[Yahoo] [2] or [MSN] [3].\n\n [1]: http://google.com/ \"Google\"\n [2]: http://search.yahoo.com/ \"Yahoo Search\"\n [3]: http://search.msn.com/ \"MSN Search\"\nUsing the implicit link name shortcut, you could instead write:
\nI get 10 times more traffic from [Google][] than from\n[Yahoo][] or [MSN][].\n\n [google]: http://google.com/ \"Google\"\n [yahoo]: http://search.yahoo.com/ \"Yahoo Search\"\n [msn]: http://search.msn.com/ \"MSN Search\"\nBoth of the above examples will produce the following HTML output:
\n<p>I get 10 times more traffic from <a href=\"http://google.com/\"\ntitle=\"Google\">Google</a> than from\n<a href=\"http://search.yahoo.com/\" title=\"Yahoo Search\">Yahoo</a>\nor <a href=\"http://search.msn.com/\" title=\"MSN Search\">MSN</a>.</p>\nFor comparison, here is the same paragraph written using\nMarkdown's inline link style:
\nI get 10 times more traffic from [Google](http://google.com/ \"Google\")\nthan from [Yahoo](http://search.yahoo.com/ \"Yahoo Search\") or\n[MSN](http://search.msn.com/ \"MSN Search\").\nThe point of reference-style links is not that they're easier to\nwrite. The point is that with reference-style links, your document\nsource is vastly more readable. Compare the above examples: using\nreference-style links, the paragraph itself is only 81 characters\nlong; with inline-style links, it's 176 characters; and as raw HTML,\nit's 234 characters. In the raw HTML, there's more markup than there\nis text.
\nWith Markdown's reference-style links, a source document much more\nclosely resembles the final output, as rendered in a browser. By\nallowing you to move the markup-related metadata out of the paragraph,\nyou can add links without interrupting the narrative flow of your\nprose.
\nMarkdown treats asterisks (*) and underscores (_) as indicators of\nemphasis. Text wrapped with one * or _ will be wrapped with an\nHTML <em> tag; double *'s or _'s will be wrapped with an HTML\n<strong> tag. E.g., this input:
*single asterisks*\n\n_single underscores_\n\n**double asterisks**\n\n__double underscores__\nwill produce:
\n<em>single asterisks</em>\n\n<em>single underscores</em>\n\n<strong>double asterisks</strong>\n\n<strong>double underscores</strong>\nYou can use whichever style you prefer; the lone restriction is that\nthe same character must be used to open and close an emphasis span.
\nEmphasis can be used in the middle of a word:
\nun*frigging*believable\nBut if you surround an * or _ with spaces, it'll be treated as a\nliteral asterisk or underscore.
To produce a literal asterisk or underscore at a position where it\nwould otherwise be used as an emphasis delimiter, you can backslash\nescape it:
\n\\*this text is surrounded by literal asterisks\\*\nTo indicate a span of code, wrap it with backtick quotes (`).\nUnlike a pre-formatted code block, a code span indicates code within a\nnormal paragraph. For example:
Use the `printf()` function.\nwill produce:
\n<p>Use the <code>printf()</code> function.</p>\nTo include a literal backtick character within a code span, you can use\nmultiple backticks as the opening and closing delimiters:
\n``There is a literal backtick (`) here.``\nwhich will produce this:
\n<p><code>There is a literal backtick (`) here.</code></p>\nThe backtick delimiters surrounding a code span may include spaces --\none after the opening, one before the closing. This allows you to place\nliteral backtick characters at the beginning or end of a code span:
\nA single backtick in a code span: `` ` ``\n\nA backtick-delimited string in a code span: `` `foo` ``\nwill produce:
\n<p>A single backtick in a code span: <code>`</code></p>\n\n<p>A backtick-delimited string in a code span: <code>`foo`</code></p>\nWith a code span, ampersands and angle brackets are encoded as HTML\nentities automatically, which makes it easy to include example HTML\ntags. Markdown will turn this:
\nPlease don't use any `<blink>` tags.\ninto:
\n<p>Please don't use any <code><blink></code> tags.</p>\nYou can write this:
\n`—` is the decimal-encoded equivalent of `—`.\nto produce:
\n<p><code>&#8212;</code> is the decimal-encoded\nequivalent of <code>&mdash;</code>.</p>\nAdmittedly, it's fairly difficult to devise a \"natural\" syntax for\nplacing images into a plain text document format.
\nMarkdown uses an image syntax that is intended to resemble the syntax\nfor links, allowing for two styles: inline and reference.
\nInline image syntax looks like this:
\n\n\n![Alt text](/path/to/img.jpg \"Optional title\")\nThat is:
\n!;alt\nattribute text for the image;title attribute enclosed in double\nor single quotes.Reference-style image syntax looks like this:
\n![Alt text][id]\nWhere \"id\" is the name of a defined image reference. Image references\nare defined using syntax identical to link references:
\n[id]: url/to/image \"Optional title attribute\"\nAs of this writing, Markdown has no syntax for specifying the\ndimensions of an image; if this is important to you, you can simply\nuse regular HTML <img> tags.
Markdown supports a shortcut style for creating \"automatic\" links for URLs and email addresses: simply surround the URL or email address with angle brackets. What this means is that if you want to show the actual text of a URL or email address, and also have it be a clickable link, you can do this:
\n<http://example.com/>\nMarkdown will turn this into:
\n<a href=\"http://example.com/\">http://example.com/</a>\nAutomatic links for email addresses work similarly, except that\nMarkdown will also perform a bit of randomized decimal and hex\nentity-encoding to help obscure your address from address-harvesting\nspambots. For example, Markdown will turn this:
\n<address@example.com>\ninto something like this:
\n<a href=\"mailto:addre\nss@example.co\nm\">address@exa\nmple.com</a>\nwhich will render in a browser as a clickable link to \"address@example.com\".
\n(This sort of entity-encoding trick will indeed fool many, if not\nmost, address-harvesting bots, but it definitely won't fool all of\nthem. It's better than nothing, but an address published in this way\nwill probably eventually start receiving spam.)
\nMarkdown allows you to use backslash escapes to generate literal\ncharacters which would otherwise have special meaning in Markdown's\nformatting syntax. For example, if you wanted to surround a word\nwith literal asterisks (instead of an HTML <em> tag), you can use\nbackslashes before the asterisks, like this:
\\*literal asterisks\\*\nMarkdown provides backslash escapes for the following characters:
\n\\ backslash\n` backtick\n* asterisk\n_ underscore\n{} curly braces\n[] square brackets\n() parentheses\n# hash mark\n+ plus sign\n- minus sign (hyphen)\n. dot\n! exclamation mark\n