Markdown: Difference between revisions
Nearinfinity (talk | contribs) m more precisely: "unmaintained" |
Safavid 930 (talk | contribs) Undid revision 1267303797 by 2405:3800:886:8020:0:0:0:1 (talk) |
||
(372 intermediate revisions by more than 100 users not shown) | |||
Line 1: | Line 1: | ||
{{Short description|Plain text markup language}} |
|||
{{for|the marketing term|Price markdown}}{{Infobox file format |
|||
{{For|the marketing term|Price markdown}} |
|||
| child = |
|||
{{Infobox file format |
|||
| name = Markdown |
|||
| name = Markdown |
|||
| logo = Markdown-mark.svg |
|||
| logo = Markdown-mark.svg{{!}}class=skin-invert |
|||
| icon_size = |
|||
| |
| icon_size = 175px |
||
| extensions = <code>.md</code>, <code>.markdown</code><ref name="df-2022">{{cite web | url=https://daringfireball.net/linked/2014/01/08/markdown-extension | title=The Markdown File Extension | publisher=The Daring Fireball Company, LLC | date=8 January 2014 | accessdate=27 March 2022 | author=Gruber, John | quote=Too late now, I suppose, but the only file extension I would endorse is ".markdown", for the same reason offered by Hilton Lipschitz: ''We no longer live in a 8.3 world, so we should be using the most descriptive file extensions. It's sad that all our operating systems rely on this stupid convention instead of the better creator code or a metadata model, but great that they now support longer file extensions.'' | archive-date=12 July 2020 | archive-url=https://web.archive.org/web/20200712120733/https://daringfireball.net/linked/2014/01/08/markdown-extension | url-status=live }}</ref><ref name="rfc7763" /> |
|||
| screenshot = |
|||
| |
| _nomimecode = on |
||
| mime = <code>text/markdown</code><ref name="rfc7763">{{cite journal | url=https://datatracker.ietf.org/doc/html/rfc7763 | title=The text/markdown Media Type | publisher=Internet Engineering Task Force | journal=Request for Comments: 7763 | date=March 2016 | accessdate=27 March 2022 | author=Leonard, Sean | quote=This document registers the text/markdown media type for use with Markdown, a family of plain-text formatting syntaxes that optionally can be converted to formal markup languages such as HTML. | archive-date=22 March 2022 | archive-url=https://web.archive.org/web/20220322001232/https://datatracker.ietf.org/doc/html/rfc7763 | url-status=live }}</ref> |
|||
| caption = |
|||
| uniform type = <code>net.daringfireball.markdown</code> |
|||
| _noextcode = on |
|||
| owner = {{plainlist| |
|||
| extension = |
|||
* [[John Gruber]] |
|||
| extensions = <code>.md</code>, <code>.markdown</code><ref>[[Daring Fireball]] [http://daringfireball.net/linked/2014/01/08/markdown-extension statement] by creator [[John Gruber]]</ref><ref name="rfc7763"/> |
|||
}} |
|||
| _nomimecode = on |
|||
| released = {{start date and age|2004|03|09|paren=yes}}<ref name="markdown-swartz">{{cite web|url=http://www.aaronsw.com/weblog/001189|title=Markdown|date=2004-03-19|work=Aaron Swartz: The Weblog|first=Aaron|last=Swartz|author-link=Aaron Swartz|access-date=2013-09-01|archive-date=2017-12-24|archive-url=https://web.archive.org/web/20171224200232/http://www.aaronsw.com/weblog/001189|url-status=live}}</ref><ref name="gruber-2004-release">{{cite web |url=http://daringfireball.net/projects/markdown/index.text |archive-url=https://web.archive.org/web/20040311230924/https://daringfireball.net/projects/markdown/index.text |archive-date=2004-03-11 |title=Markdown|work=[[Daring Fireball]]|first=John|last=Gruber|author-link=John Gruber |access-date=2022-08-20}}</ref> |
|||
| mime = <code>text/markdown</code><ref name="rfc7763">[https://tools.ietf.org/html/rfc7763 RFC 7763] - The text/markdown Media Type</ref> |
|||
| type code = |
|||
| uniform type = <code>net.daringfireball.markdown</code> |
|||
| conforms to = |
|||
| magic = |
|||
| owner = [[John Gruber]] (in collaboration with [[Aaron Swartz]] on the syntax) |
|||
| released = {{start date and age|2004|03|19|paren=yes}}<ref name="markdown-swartz">{{cite web |url=http://www.aaronsw.com/weblog/001189 |title=Markdown |date=2004-03-19 |work=Aaron Swartz: The Weblog|first=Aaron|last=Swartz|authorlink=Aaron Swartz}}</ref><ref name="gruber-2004-release">{{cite web |url=http://daringfireball.net/projects/markdown/ |archiveurl=https://web.archive.org/web/20040402182332/http://daringfireball.net/projects/markdown/ |archivedate=2004-04-02 |title=Daring Fireball: Markdown|work=[[Daring Fireball]]|first=John|last=Gruber|authorlink=John Gruber |accessdate=2014-04-25}}</ref> |
|||
| latest release version = 1.0.1 |
| latest release version = 1.0.1 |
||
| latest release date = {{start date and age|2004|12|17|paren=yes}}<ref name="md" /> |
| latest release date = {{start date and age|2004|12|17|paren=yes}}<ref name="md" /> |
||
| genre = [[Markup language]] |
| genre = [[Markup language]] |
||
| extended to = [[pandoc]], [[MultiMarkdown]], [[Markdown Extra]], [[#Standardization|CommonMark]],<ref name="rfc7764">{{cite journal | url=https://datatracker.ietf.org/doc/html/rfc7764 | title=Guidance on Markdown: Design Philosophies, Stability Strategies, and Select Registrations | publisher=Internet Engineering Task Force | journal=Request for Comments: 7764 | date=March 2016 | accessdate=27 March 2022 | author=Leonard, Sean | quote=This document elaborates upon the text/markdown media type for use with Markdown, a family of plain-text formatting syntaxes that optionally can be converted to formal markup languages such as HTML. Background information, local storage strategies, and additional syntax registrations are supplied. | archive-date=17 April 2022 | archive-url=https://web.archive.org/web/20220417115136/https://datatracker.ietf.org/doc/html/rfc7764 | url-status=live }}</ref> [[RMarkdown]]<ref name="RMarkdown">{{cite web|url=https://rmarkdown.rstudio.com/|title=RMarkdown Reference site|access-date=2019-11-21|archive-date=2020-03-03|archive-url=https://web.archive.org/web/20200303054734/https://rmarkdown.rstudio.com/|url-status=live}}</ref> |
|||
| container for = |
|||
| |
| standard = |
||
| |
| standards = |
||
| type = [[Open file format]]<ref name="license">{{cite web |url=http://daringfireball.net/projects/markdown/license |title=Markdown: License |publisher=Daring Fireball |access-date=2014-04-25 |archive-date=2020-02-18 |archive-url=https://web.archive.org/web/20200218183533/https://daringfireball.net/projects/markdown/license |url-status=live }}</ref> |
|||
| extended to = [[MultiMarkdown]], [[Markdown Extra]], [[CommonMark]],<ref name="rfc7764">[https://tools.ietf.org/html/rfc7764 RFC7764] – Guidance on Markdown: Design Philosophies, Stability Strategies, and Select Registrations</ref> [[RMarkdown]]<ref name="RMarkdown">[https://rmarkdown.rstudio.com/ RMarkdown Reference site] - RMarkdown Reference site</ref> |
|||
| url = {{URL|https://daringfireball.net/projects/markdown/}} |
|||
| standard = |
|||
| standards = |
|||
| free = Yes<ref name="license">{{cite web|url=http://daringfireball.net/projects/markdown/license |title=Markdown: License |publisher=Daring Fireball |date= |accessdate=2014-04-25}}</ref> |
|||
| url = {{URL|https://daringfireball.net/projects/markdown/}} |
|||
}} |
}} |
||
'''Markdown'''<ref name="philosophy" /> is a [[lightweight markup language]] for creating [[formatted text]] using a [[text editor|plain-text editor]]. [[John Gruber]] created Markdown in 2004 as an easy-to-read [[markup language]].<ref name="philosophy" /> Markdown is widely used for [[blog]]ging and [[instant messaging]], and also used elsewhere in [[online forums]], [[collaborative software]], [[documentation]] pages, and [[README|readme files]]. |
|||
'''Markdown''' is a [[lightweight markup language]] with plain-text-formatting syntax. Its design allows it to be converted to many output formats, but the original tool by the same name only supports [[HTML]].<ref>{{cite web|url=http://daringfireball.net/projects/markdown/ |title=Markdown |date=2013-12-04 |url-status=live|archiveurl=https://web.archive.org/web/20040402182332/http://daringfireball.net/projects/markdown/ |archivedate=2004-04-02 }}</ref> Markdown is often used to format [[README|readme file]]s, for writing messages in online discussion forums, and to create [[formatted text|rich text]] using a [[plain text]] [[text editor|editor]]. |
|||
The initial description of Markdown<ref>{{Cite web|title=Daring Fireball: Introducing Markdown|url=https://daringfireball.net/2004/03/introducing_markdown|access-date=2020-09-23|website=daringfireball.net|archive-date=2020-09-20|archive-url=https://web.archive.org/web/20200920182442/https://daringfireball.net/2004/03/introducing_markdown|url-status=live}}</ref> contained ambiguities and raised unanswered questions, causing implementations to both intentionally and accidentally diverge from the original version. This was addressed in 2014 when long-standing Markdown contributors released [[#Standardization|CommonMark]], an unambiguous specification and test suite for Markdown.<ref name="FutureOfMarkdown" /> |
|||
Since the initial description of Markdown contained ambiguities and unanswered questions, the implementations that appeared over the years have subtle differences and many come with syntax extensions. |
|||
==History== |
== History == |
||
Markdown was inspired by pre-existing [[Convention (norm)|conventions]] for marking up [[plain text]] in [[email]] and [[usenet]] posts,<ref name="ArsTechnica2014"/> such as the earlier markup languages [[setext]] ({{Circa|1992}}), [[Textile (markup language)|Textile]] (c. 2002), and [[reStructuredText]] (c. 2002).<ref name="philosophy" /> |
|||
[[John Gruber]] created the Markdown language in 2004 in collaboration with [[Aaron Swartz]] on the syntax,<ref name="markdown-swartz"/><ref name="gruber-2004-release"/> with the goal of enabling people "to write using an easy-to-read and easy-to-write plain text format, optionally convert it to structurally valid [[XHTML]] (or [[HTML]])".<ref name="md">Markdown 1.0.1 readme source code {{cite web|url=http://daringfireball.net/projects/markdown/ |title=Daring Fireball – Markdown |date=2004-12-17 |url-status=dead |archiveurl=https://web.archive.org/web/20040402182332/http://daringfireball.net/projects/markdown/ |archivedate=2004-04-02 }}</ref> |
|||
In 2002 [[Aaron Swartz]] created [[atx (markup language)|atx]] and referred to it as "the true structured text format". Gruber created the Markdown language in 2004 with Swartz as his "sounding board".<ref name="Gruber">{{Cite tweet |user=gruber |number=741989829173510145 |title=I should write about it, but it's painful. More or less: Aaron was my sounding board, my muse.}}</ref> The goal of the language was to enable people "to write using an easy-to-read and easy-to-write plain text format, optionally convert it to structurally valid [[XHTML]] (or [[HTML]])".<ref name="md">Markdown 1.0.1 readme source code {{cite web|url=http://daringfireball.net/projects/markdown/ |title=Daring Fireball – Markdown |date=2004-12-17 |url-status=dead |archive-url=https://web.archive.org/web/20040402182332/http://daringfireball.net/projects/markdown/ |archive-date=2004-04-02 }}</ref> |
|||
Its key design goal is ''readability'' – that the language be readable as-is, without looking like it has been marked up with tags or formatting instructions,<ref name="philosophy">Markdown Syntax {{cite web|url=http://daringfireball.net/projects/markdown/syntax#philosophy|title=Daring Fireball – Markdown – Syntax|date=2013-06-13|quote="Readability, however, is emphasized above all else. 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. While Markdown’s syntax has been influenced by several existing text-to-HTML filters — including Setext, atx, Textile, reStructuredText, Grutatext, and EtText — the single biggest source of inspiration for Markdown’s syntax is the format of plain text email."}}</ref> unlike text formatted with a [[markup language]], such as [[Rich Text Format]] (RTF) or HTML, which have obvious tags and formatting instructions. To this end, its main inspiration is the existing [[Convention (norm)|conventions]] for marking up [[plain text]] in [[email]], though it also draws from earlier markup languages, notably [[setext]], [[Textile (markup language)|Textile]], and [[reStructuredText]].<ref name="philosophy" /> |
|||
Another key design goal was ''readability'', that the language be readable as-is, without looking like it has been marked up with tags or formatting instructions,{{r|name="philosophy"|reference=Markdown Syntax {{cite web|url=http://daringfireball.net/projects/markdown/syntax#philosophy|title=Daring Fireball – Markdown – Syntax|date=2013-06-13 }} "Readability, however, is emphasized above all else. 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. While Markdown's syntax has been influenced by several existing text-to-HTML filters — including Setext, atx, Textile, reStructuredText, Grutatext{{r |name="grutatext" |reference={{Cite web |title=Un naufragio personal: The Grutatxt markup |url=https://triptico.com/docs/grutatxt_markup.html |access-date=2022-06-30 |website=triptico.com }} }}, and EtText{{r |name="ettext" |reference={{Cite web |title=EtText: Documentation: Using EtText |url=http://ettext.taint.org/doc/ettext.html |access-date=2022-06-30 |website=ettext.taint.org}} }} — the single biggest source of inspiration for Markdown's syntax is the format of plain text email." }} unlike text formatted with "heavier" [[markup language]]s, such as [[Rich Text Format]] (RTF), HTML, or even [[wikitext]] (each of which have obvious in-line tags and formatting instructions which can make the text more difficult for humans to read). |
|||
Gruber wrote a [[Perl]] script, {{code|Markdown.pl}}, which converts marked-up text input to valid, [[XML#Well-formedness and error-handling|well-formed]] XHTML or HTML and replaces angle brackets '{{code|<}}' '{{code|>}}' and [[ampersand]]s '{{code|&}}' with their corresponding [[character entity references]]. It can be used as a standalone script, as a plugin for [[Blosxom]] or [[Movable Type]], or as a text filter for [[BBEdit]].<ref name="md" /> |
|||
Gruber wrote a [[Perl]] script, {{code|Markdown.pl}}, which converts marked-up text input to valid, [[XML#Well-formedness and error-handling|well-formed]] XHTML or HTML and replaces angle brackets ({{code|<}}, {{code|>}}) and [[ampersand]]s ({{code|&}}) with their corresponding [[character entity references]]. It can take the role of a standalone script, a plugin for [[Blosxom]] or a [[Movable Type]], or of a text filter for [[BBEdit]].<ref name="md" /> |
|||
Markdown has since been re-implemented by others e.g. in a Perl [[modular programming|module]] available on [[CPAN]] ({{code|Text::Markdown}}), and in a variety of other programming languages.<ref>{{cite web|url=https://pypi.python.org/pypi/Markdown|title=Markdown 2.6.6|publisher=[[Python Software Foundation]]|date=2016-03-21|accessdate=2016-07-06}}</ref> It is distributed under a [[BSD license|BSD-style license]] and is included with, or available as a plugin for, several [[content management system|content-management systems]].<ref name="license" /><ref>{{cite web| title = MarsEdit 2.3 ties the knot with Tumblr support – Ars Technica| accessdate = 2009-08-11| url = https://arstechnica.com/apple/news/2009/03/marsedit-23-ties-the-knot-with-tumblr-support.ars}}</ref><ref>{{cite web| title = Review: Practical Django Projects – Ars Technica| accessdate = 2009-08-11| url = https://arstechnica.com/open-source/news/2008/07/review-practical-django-projects.ars}}</ref> |
|||
== Rise and divergence == |
|||
Sites like [[GitHub]], [[Bitbucket]], [[Reddit]], [[Diaspora (social network)|Diaspora]], [[Stack Exchange]], [[OpenStreetMap]], and [[SourceForge]] use variants of Markdown to facilitate discussion between users.<ref name="gfm_on_github">{{cite web |title=GitHub Flavored Markdown |url=https://help.github.com/articles/github-flavored-markdown |publisher=GitHub |accessdate=2013-03-29}}</ref><ref>{{cite web |title=Reddit markdown primer. Or, how do you do all that fancy formatting in your comments, anyway?|url=https://www.reddit.com/r/reddit.com/comments/6ewgt/reddit_markdown_primer_or_how_do_you_do_all_that/ |publisher=Reddit.com |accessdate=2013-03-29}}</ref><ref>{{cite web |title=Markdown Editing Help |url=https://stackoverflow.com/editing-help |publisher=StackOverflow.com |accessdate=2014-04-11}}</ref><ref>{{cite web |title=SourceForge: Markdown Syntax Guide |url=http://sourceforge.net/p/forge/documentation/markdown_syntax/ |publisher=SourceForge.net |accessdate=2013-05-10}}</ref> |
|||
As Markdown's popularity grew rapidly, many Markdown [[Implementation|implementations]] appeared, driven mostly by the need for additional features such as [[Table (information)|tables]], [[Note (typography)|footnotes]], definition lists,<ref group="note">Technically HTML description lists</ref> and Markdown inside HTML blocks. |
|||
=== Standardization === |
|||
The behavior of some of these diverged from the reference implementation, as Markdown was only characterised by an informal [[Specification (technical standard)|specification]]<ref>{{cite web|url=https://daringfireball.net/projects/markdown/syntax|title=Markdown Syntax Documentation|publisher=Daring Fireball|access-date=2018-03-09|archive-date=2019-09-09|archive-url=https://web.archive.org/web/20190909051956/https://daringfireball.net/projects/markdown/syntax|url-status=live}}</ref> and a [[Perl]] implementation for conversion to HTML. |
|||
Markdown has been characterised by an informal specification<ref>https://daringfireball.net/projects/markdown/syntax</ref> and a reference implementation for conversion to HTML. Over time, many Markdown implementations have appeared. People developed these mostly driven by the need for additional features on top of the base syntax—such as tables, footnotes, definition lists (technically HTML description lists), and Markdown inside HTML blocks. The behavior of some of these diverges from the reference implementation. At the same time, a number of ambiguities in the informal specification have attracted attention.<ref>{{cite web|url=https://github.github.com/gfm/#why-is-a-spec-needed-|title=GitHub Flavored Markdown Spec|website=github.github.com}}</ref> These issues spurred the creation of tools such as Babelmark{{nnbsp}}<ref name="babelmark-2">{{cite web|url=http://johnmacfarlane.net/babelmark2/ |title=Babelmark 2 - Compare markdown implementations |publisher=Johnmacfarlane.net |accessdate=2014-04-25}}</ref><ref name="babelmark-3"> |
|||
{{cite web|url=https://babelmark.github.io |title=Babelmark 3 - Compare Markdown Implementations |publisher=github.io |accessdate=2017-12-10}}</ref> is to compare the output of various implementations,"<ref>{{cite web|url=http://johnmacfarlane.net/babelmark2/faq.html |title=Babelmark 2 - FAQ |publisher=Johnmacfarlane.net |accessdate=2014-04-25}}</ref> and an effort by some developers of Markdown parsers for standardisation. However Gruber has argued that complete standardization would be mistaken: "Different sites (and people) have different needs. No one syntax would make all happy."<ref>{{cite tweet|user=gruber|authorlink=John Gruber|first=John|last=Gruber|number=507670720886091776|date=4 September 2014|title=@tobie @espadrine @comex @wycats Because different sites (and people) have different needs. No one syntax would make all happy.}}</ref> |
|||
At the same time, a number of ambiguities in the informal specification had attracted attention.<ref name="gfm_on_github-why_spec">{{cite web|url=https://github.github.com/gfm/#why-is-a-spec-needed-|title=GitHub Flavored Markdown Spec – Why is a spec needed?|website=github.github.com|access-date=2018-05-17|archive-date=2020-02-03|archive-url=https://web.archive.org/web/20200203204734/https://github.github.com/gfm/#why-is-a-spec-needed-|url-status=live}}</ref> These issues spurred the creation of tools such as Babelmark<ref name="babelmark-2">{{cite web |url=http://johnmacfarlane.net/babelmark2/ |title=Babelmark 2 – Compare markdown implementations |publisher=Johnmacfarlane.net |access-date=2014-04-25 |archive-date=2017-07-18 |archive-url=https://web.archive.org/web/20170718113552/http://johnmacfarlane.net/babelmark2/ |url-status=live }}</ref><ref name="babelmark-3">{{cite web |url=https://babelmark.github.io/ |title=Babelmark 3 – Compare Markdown Implementations |publisher=github.io |access-date=2017-12-10 |archive-date=2020-11-12 |archive-url=https://web.archive.org/web/20201112043521/https://babelmark.github.io/ |url-status=live }}</ref> to compare the output of various implementations,<ref>{{cite web |url=http://johnmacfarlane.net/babelmark2/faq.html |title=Babelmark 2 – FAQ |publisher=Johnmacfarlane.net |access-date=2014-04-25 |archive-date=2017-07-28 |archive-url=https://web.archive.org/web/20170728115918/http://johnmacfarlane.net/babelmark2/faq.html |url-status=live }}</ref> and an effort by some developers of Markdown [[Parsing|parsers]] for standardisation. However, Gruber has argued that complete standardization would be a mistake: "Different sites (and people) have different needs. No one syntax would make all happy."<ref>{{cite tweet|user=gruber|author-link=John Gruber|first=John|last=Gruber|number=507670720886091776|date=4 September 2014|title=@tobie @espadrine @comex @wycats Because different sites (and people) have different needs. No one syntax would make all happy.}}</ref> |
|||
Gruber avoided using curly braces in Markdown to unofficially reserve them for implementation-specific extensions.<ref name="curlyBraces">{{cite web |url=https://daringfireball.net/linked/2022/05/19/markdoc |title=Markdoc |last=Gruber |first=John |date=19 May 2022 |website=Daring Fireball |access-date=May 19, 2022 |quote=I love their syntax extensions — very true to the spirit of Markdown. They use curly braces for their extensions; I'm not sure I ever made this clear, publicly, but I avoided using curly braces in Markdown itself — even though they are very tempting characters — to unofficially reserve them for implementation-specific extensions. Markdoc's extensive use of curly braces for its syntax is exactly the sort of thing I was thinking about. |archive-date=19 May 2022 |archive-url=https://web.archive.org/web/20220519202920/https://daringfireball.net/linked/2022/05/19/markdoc |url-status=live }}</ref> |
|||
In March 2016 two relevant informational Internet [[Request for Comments|RFCs]] were published: |
|||
* RFC 7763 introduced [[MIME]] type <small>{{code|text/markdown}}</small> with the original variant. |
|||
* RFC 7764 discusses and registered the variants [[MultiMarkdown]], GitHub Flavored Markdown (GFM), [[Pandoc]], [[#CommonMark|CommonMark]], and Markdown Extra among others.<ref name="IANA">{{cite web|url=https://www.iana.org/assignments/markdown-variants/markdown-variants.xhtml|title=Markdown Variants|publisher=[[Internet Assigned Numbers Authority|IANA]]|date=2016-03-28|accessdate=2016-07-06}}</ref> |
|||
== Standardization == |
|||
{{Infobox file format |
{{Infobox file format |
||
| name |
| name = CommonMark |
||
| logo |
| logo = Markdown-mark.svg{{!}}class=skin-invert |
||
| |
| _noextcode = on |
||
| extensions = <code>.md</code>, <code>.markdown</code><ref name="rfc7763" /> |
|||
| caption = |
|||
| |
| _nomimecode = on |
||
| |
| mime = <code>text/markdown; variant=CommonMark</code><ref name="rfc7764" /> |
||
| uniform type = ''uncertain''<ref name="cm-uti">{{cite web|url= https://talk.commonmark.org/t/uti-of-a-commonmark-document/2406|title= UTI of a CommonMark document|date= 12 April 2017|access-date= 29 September 2017|archive-date= 22 November 2018|archive-url= https://web.archive.org/web/20181122140119/https://talk.commonmark.org/t/uti-of-a-commonmark-document/2406|url-status= live}}</ref> |
|||
|_nomimecode = on |
|||
| conforms to = public.plain-text |
|||
| mime = <code>text/markdown; variant=CommonMark</code><ref name="rfc7764"/> |
|||
| |
| owner = [[John MacFarlane (philosopher)|John MacFarlane]], open source |
||
| released = {{start date and age|2014|10|25|paren=yes}} |
|||
| uniform type = ''uncertain''<ref name="cm-uti">{{cite web |url= https://talk.commonmark.org/t/uti-of-a-commonmark-document/2406 |title= UTI of a CommonMark document}}</ref> |
|||
| latest release version = 0.31.2 |
|||
| conforms to = public.plain-text |
|||
| latest release date = {{start date and age|2024|01|28|paren=yes}}<ref name="cm-spec">{{cite web |url= http://spec.commonmark.org/ |title= CommonMark specification |access-date= 2017-07-26 |archive-date= 2017-08-07 |archive-url= https://web.archive.org/web/20170807052756/http://spec.commonmark.org/ |url-status= live }}</ref> |
|||
| magic = |
|||
| genre = [[Markup language]] |
|||
| owner = [[John MacFarlane (philosopher)|John MacFarlane]], open source |
|||
| extended from = Markdown |
|||
| released = {{start date and age|2014|10|25|paren=yes}} |
|||
| extended to = GitHub Flavored Markdown |
|||
| latest release version = 0.29 |
|||
| type = [[Open file format]] |
|||
| latest release date = {{start date and age|2019|04|06|paren=yes}}<ref name="cm-spec">{{cite web |url= http://spec.commonmark.org/ |title= CommonMark specification }}</ref> |
|||
| |
| url = {{URL|https://commonmark.org/}} |
||
{{URL|http://spec.commonmark.org/}} |
|||
| container for = |
|||
| contained by = |
|||
| extended from = Markdown |
|||
| extended to = GitHub Flavored Markdown |
|||
| standard = |
|||
| free = yes |
|||
| url = {{URL|http://spec.commonmark.org/}} |
|||
}} |
}} |
||
From 2012, a group of people including [[Jeff Atwood]] and [[John MacFarlane (philosopher) |
From 2012, a group of people, including [[Jeff Atwood]] and [[John MacFarlane (philosopher)|John MacFarlane]], launched what Atwood characterised as a standardisation effort.<ref name="FutureOfMarkdown">{{cite web |last=Atwood |first=Jeff |url=http://www.codinghorror.com/blog/2012/10/the-future-of-markdown.html |title=The Future of Markdown |publisher=CodingHorror.com |date=2012-10-25 |access-date=2014-04-25 |archive-date=2014-02-11 |archive-url=https://web.archive.org/web/20140211233513/http://www.codinghorror.com/blog/2012/10/the-future-of-markdown.html |url-status=dead }}</ref> |
||
A community website now aims to "document various tools and resources available to document authors and developers, as well as implementors of the various Markdown implementations".<ref>{{cite web |url=https://markdown.github.io/ |title=Markdown Community Page |publisher=GitHub |access-date=2014-04-25 |archive-date=2020-10-26 |archive-url=https://web.archive.org/web/20201026161924/http://markdown.github.io/ |url-status=live }}</ref> |
|||
=== GitHub Flavored Markdown (GFM) === |
|||
In 2017, GitHub released a formal specification of their GitHub Flavored Markdown (GFM) that is based on CommonMark.<ref>{{Cite web| url= https://github.github.com/gfm/ | title= GitHub Flavored Markdown Spec }}</ref> It follows the CommonMark specification exactly except for ''tables, strikethrough, autolinks and task lists,'' which the GitHub spec has added as extensions.<ref>{{Cite web|url=https://githubengineering.com/a-formal-spec-for-github-markdown/|title=A formal spec for GitHub Flavored Markdown|last=|first=|date=|website=GitHub Engineering|access-date=16 Mar 2017}}</ref> GitHub also changed the parser used on their sites accordingly, which required that some documents be changed. For instance, GFM now requires that the [[number sign|hash symbol]] that creates a heading be separated from the heading text by a space character. |
|||
In September 2014, Gruber objected to the usage of "Markdown" in the name of this effort and it was rebranded as CommonMark.<ref name="ArsTechnica2014" /><ref>{{cite web |url=http://blog.codinghorror.com/standard-markdown-is-now-common-markdown/ |title=Standard Markdown is now Common Markdown |date=4 September 2014 |publisher=Jeff Atwood |access-date=2014-10-07 |archive-date=2014-10-09 |archive-url=https://web.archive.org/web/20141009181014/http://blog.codinghorror.com/standard-markdown-is-now-common-markdown/ |url-status=live }}</ref><ref>{{cite web |url=http://www.infoq.com/news/2014/09/markdown-commonmark |title=Standard Markdown Becomes Common Markdown then CommonMark |work=InfoQ |access-date=2014-10-07 |archive-date=2020-09-30 |archive-url=https://web.archive.org/web/20200930150521/https://www.infoq.com/news/2014/09/markdown-commonmark/ |url-status=live }}</ref> CommonMark.org published several versions of a specification, reference implementation, test suite, and "[plans] to announce a finalized 1.0 spec and test suite in 2019".<ref name="commonmark.org">{{cite web |url=http://commonmark.org/ |title=CommonMark |language=en |access-date=20 Jun 2018 |quote=The current version of the CommonMark spec is complete, and quite robust after a year of public feedback … but not quite final. With your help, we plan to announce a finalized 1.0 spec and test suite in 2019. |archive-date=12 April 2016 |archive-url=https://web.archive.org/web/20160412211434/http://commonmark.org/ |url-status=live}}</ref> |
|||
No 1.0 spec has since been released, as major issues still remain unsolved.<ref>{{Cite web |date=2015-07-26 |title=Issues we MUST resolve before 1.0 release [6 remaining] |url=https://talk.commonmark.org/t/issues-we-must-resolve-before-1-0-release-6-remaining/1287 |access-date=2020-10-02 |website=CommonMark Discussion |language=en-US |archive-date=2021-04-14 |archive-url=https://web.archive.org/web/20210414032229/https://talk.commonmark.org/t/issues-we-must-resolve-before-1-0-release-6-remaining/1287 |url-status=live}}</ref> |
|||
Nonetheless, the following websites and projects have adopted CommonMark: [[Discourse (software)|Discourse]], [[GitHub]], [[GitLab]], [[Reddit]], [[Qt (software)|Qt]], [[Stack Exchange]] ([[Stack Overflow]]), and [[Swift (programming language)|Swift]]. |
|||
In March 2016, two relevant informational Internet [[Request for Comments|RFCs]] were published: |
|||
* {{IETF RFC|7763|link=no}} introduced [[MIME]] type <small>{{code|text/markdown}}</small>. |
|||
* {{IETF RFC|7764|link=no}} discussed and registered the variants [[MultiMarkdown]], GitHub Flavored Markdown (GFM), [[Pandoc]], and Markdown Extra among others.<ref name="IANA">{{cite web |url=https://www.iana.org/assignments/markdown-variants/markdown-variants.xhtml |title=Markdown Variants |publisher=[[Internet Assigned Numbers Authority|IANA]] |date=2016-03-28 |access-date=2016-07-06 |archive-date=2020-10-27 |archive-url=https://web.archive.org/web/20201027005128/https://www.iana.org/assignments/markdown-variants/markdown-variants.xhtml |url-status=live}}</ref> |
|||
== Variants == |
|||
Websites like [[Bitbucket]], [[Diaspora (social network)|Diaspora]], [[GitHub]],<ref name="gfm_on_github">{{cite web|title=GitHub Flavored Markdown Spec|url=https://github.github.com/gfm/|access-date=2020-06-11|publisher=GitHub|archive-date=2020-02-03|archive-url=https://web.archive.org/web/20200203204734/https://github.github.com/gfm/|url-status=live}}</ref> [[OpenStreetMap]], [[Reddit]],<ref>{{cite web|title=Reddit markdown primer. Or, how do you do all that fancy formatting in your comments, anyway?|url=https://www.reddit.com/r/reddit.com/comments/6ewgt/reddit_markdown_primer_or_how_do_you_do_all_that/|access-date=2013-03-29|publisher=Reddit|archive-date=2019-06-11|archive-url=https://web.archive.org/web/20190611185827/https://www.reddit.com/r/reddit.com/comments/6ewgt/reddit_markdown_primer_or_how_do_you_do_all_that/|url-status=live}}</ref> [[SourceForge]]<ref>{{cite web|title=SourceForge: Markdown Syntax Guide|url=http://sourceforge.net/p/forge/documentation/markdown_syntax/|access-date=2013-05-10|publisher=[[SourceForge]]|archive-date=2019-06-13|archive-url=https://web.archive.org/web/20190613130356/https://sourceforge.net/p/forge/documentation/markdown_syntax/|url-status=live}}</ref> and [[Stack Exchange]]<ref>{{cite web|title=Markdown Editing Help|url=https://stackoverflow.com/editing-help|access-date=2014-04-11|publisher=StackOverflow.com|archive-date=2014-03-28|archive-url=https://web.archive.org/web/20140328061854/http://stackoverflow.com/editing-help|url-status=live}}</ref> use variants of Markdown to make discussions between users easier. |
|||
Depending on implementation, basic inline [[HTML tag]]s may be supported.<ref>{{cite web |title=Markdown Syntax Documentation |url=https://daringfireball.net/projects/markdown/syntax#html |website=daringfireball.net |access-date=2021-03-01 |archive-date=2019-09-09 |archive-url=https://web.archive.org/web/20190909051956/https://daringfireball.net/projects/markdown/syntax#html |url-status=live }}</ref> |
|||
Italic text may be implemented by <code>_underscores_</code> or <code>*single-asterisks*</code>.<ref name="italic">{{cite web | url=https://www.markdownguide.org/basic-syntax/#italic | title=Basic Syntax: Italic | publisher=Matt Cone | work=The Markdown Guide | accessdate=27 March 2022 | quote=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. | archive-date=26 March 2022 | archive-url=https://web.archive.org/web/20220326234942/https://www.markdownguide.org/basic-syntax/#italic | url-status=live }}</ref> |
|||
=== GitHub Flavored Markdown === |
|||
GitHub had been using its own variant of Markdown since as early as 2009,<ref>{{cite web |title = GitHub Flavored Markdown Examples |author = [[Tom Preston-Werner]] |url = https://github.com/mojombo/github-flavored-markdown/issues/1 |website = GitHub |accessdate = 2021-04-02 |archive-date = 2021-05-13 |archive-url = https://web.archive.org/web/20210513154115/https://github.com/mojombo/github-flavored-markdown/issues/1 |url-status = live }}</ref> which added support for additional formatting such as tables and nesting [[HTML element#Block elements|block content]] inside list elements, as well as GitHub-specific features such as auto-linking references to commits, issues, usernames, etc. |
|||
In 2017, GitHub released a formal specification of its GitHub Flavored Markdown (GFM) that is based on CommonMark.<ref name="gfm_on_github" /> It is a [[Superset|strict superset]] of CommonMark, following its specification exactly except for tables, [[strikethrough]], [[Automatic hyperlinking|autolinks]] and task lists, which GFM adds as extensions.<ref>{{Cite web |url = https://githubengineering.com/a-formal-spec-for-github-markdown/ |title = A formal spec for GitHub Flavored Markdown |website = GitHub Engineering |date = 14 March 2017 |access-date = 16 Mar 2017 |archive-date = 3 February 2020 |archive-url = https://web.archive.org/web/20200203205138/https://githubengineering.com/a-formal-spec-for-github-markdown/ |url-status = live }}</ref> |
|||
Accordingly, GitHub also changed the parser used on their sites, which required that some documents be changed. For instance, GFM now requires that the [[number sign|hash symbol]] that creates a heading be separated from the heading text by a space character. |
|||
=== Markdown Extra === |
=== Markdown Extra === |
||
Markdown Extra is a [[lightweight markup language]] based on Markdown implemented in [[PHP]] (originally), [[Python (programming language)|Python]] and [[Ruby (programming language)|Ruby]].<ref name="fortin-2018"> |
Markdown Extra is a [[lightweight markup language]] based on Markdown implemented in [[PHP]] (originally), [[Python (programming language)|Python]] and [[Ruby (programming language)|Ruby]].<ref name="fortin-2018">{{cite web |
||
| last1 = Fortin |
|||
{{cite web |
|||
| first1 = Michel |
|||
| title = PHP Markdown Extra |
| title = PHP Markdown Extra |
||
| date = 2018 |
| date = 2018 |
||
Line 97: | Line 104: | ||
| url = https://michelf.ca/projects/php-markdown/extra |
| url = https://michelf.ca/projects/php-markdown/extra |
||
| access-date = 2018-12-26 |
| access-date = 2018-12-26 |
||
| archive-date = 2021-01-17 |
|||
}} |
|||
| archive-url = https://web.archive.org/web/20210117015819/https://michelf.ca/projects/php-markdown/extra/ |
|||
</ref> It adds features not available with plain Markdown syntax. Markdown Extra is supported in some [[content management system]]s such as, for example, [[Drupal]]<ref>{{cite web|url=https://drupal.org/project/markdowneditor|title=Markdown editor for BUEditor|date=4 December 2008|publisher=}}</ref> and [[TYPO3]].<ref>{{cite web|url=https://extensions.typo3.org/extension/markdown_content/|title=Markdown for TYPO3 (markdown_content)|website=extensions.typo3.org}}</ref> |
|||
| url-status = live |
|||
}}</ref> It adds the following features that are not available with regular Markdown: |
|||
In [[MediaWiki]], it is implemented in the currently unmaintained [[mw:Extension:MarkdownExtraParser|MarkdownExtraParser]] [[MediaWiki#Text manipulation|parser function extension]] |
|||
* Markdown markup inside [[HTML]] blocks |
|||
Markdown Extra adds the following features to Markdown: |
|||
* Elements with id/class attribute |
|||
* "Fenced code blocks" that span multiple lines of code |
|||
* Tables<ref>{{cite web|url=https://michelf.ca/projects/php-markdown/extra|title=PHP Markdown Extra|website=Michel Fortin|access-date=2018-12-26|archive-date=2021-01-17|archive-url=https://web.archive.org/web/20210117015819/https://michelf.ca/projects/php-markdown/extra/|url-status=live}}</ref> |
|||
* Definition lists |
|||
* Footnotes |
|||
* Abbreviations |
|||
Markdown Extra is supported in some [[content management system]]s such as [[Drupal]],<ref>{{cite web|url=https://drupal.org/project/markdowneditor|title=Markdown editor for BUEditor|date=4 December 2008|access-date=15 January 2017|archive-date=17 September 2020|archive-url=https://web.archive.org/web/20200917172201/https://www.drupal.org/project/markdowneditor|url-status=live}}</ref> [[Grav (CMS)]] and [[TYPO3]].<ref>{{cite web|url=https://extensions.typo3.org/extension/markdown_content/|title=Markdown for TYPO3 (markdown_content)|website=extensions.typo3.org|access-date=2019-02-06|archive-date=2021-02-01|archive-url=https://web.archive.org/web/20210201205749/https://extensions.typo3.org/extension/markdown_content/|url-status=live}}</ref> |
|||
* markdown markup inside [[HTML]] blocks |
|||
* elements with id/class attribute |
|||
* "fenced code blocks" that span multiple lines of code |
|||
* tables{{nnbsp}}<ref>{{cite web|url=https://michelf.ca/projects/php-markdown/extra|title=PHP Markdown Extra|website=Michel Fortin}}</ref> |
|||
* definition lists |
|||
* footnotes |
|||
* abbreviations |
|||
== |
== Examples == |
||
{|class="wikitable" |
{|class="wikitable" |
||
! width="33%" | Text using Markdown syntax |
! width="33%" | Text using Markdown syntax |
||
! width="34%" | Corresponding HTML produced by a Markdown processor |
! width="34%" | Corresponding HTML produced by a Markdown processor |
||
! width="33%" | Text viewed in a browser |
! width="33%" | Text viewed in a browser |
||
|-valign="top" |
|-valign="top" |
||
| |
| |
||
< |
<syntaxhighlight lang="md"> |
||
Heading |
Heading |
||
======= |
======= |
||
Line 127: | Line 134: | ||
----------- |
----------- |
||
# Alternative heading |
|||
Paragraphs are separated |
|||
by a blank line. |
|||
## Alternative sub-heading |
|||
Two spaces at the end of a line |
|||
produces a line break. |
|||
Paragraphs are separated |
|||
Text attributes _italic_, |
|||
by a blank line. |
|||
**bold**, `monospace`. |
|||
Two spaces at the end of a line |
|||
Horizontal rule: |
|||
produce a line break. |
|||
</syntaxhighlight> |
|||
--- |
|||
Strikethrough: |
|||
~~strikethrough~~ |
|||
Bullet list: |
|||
* apples |
|||
* oranges |
|||
* pears |
|||
Numbered list: |
|||
1. lather |
|||
2. rinse |
|||
3. repeat |
|||
An [example](http://example.com). |
|||
![Image](Icon-pictures.png "icon") |
|||
> Markdown uses email-style > characters for blockquoting. |
|||
Inline <abbr title="Hypertext Markup Language">HTML</abbr> is supported. |
|||
</source> |
|||
| |
| |
||
<syntaxhighlight lang="html"> |
<syntaxhighlight lang="html"> |
||
Line 168: | Line 149: | ||
<h2>Sub-heading</h2> |
<h2>Sub-heading</h2> |
||
<h1>Alternative heading</h1> |
|||
<h2>Alternative sub-heading</h2> |
|||
<p>Paragraphs are separated |
<p>Paragraphs are separated |
||
Line 173: | Line 158: | ||
<p>Two spaces at the end of a line<br /> |
<p>Two spaces at the end of a line<br /> |
||
produce a line break.</p> |
|||
</syntaxhighlight> |
|||
|<div style="overflow: hidden; page-break-after: avoid; |
|||
font-size: 1.8em; font-family: Georgia,Times,serif; margin-top: 1em; margin-bottom: 0.25em; line-height: 1.3; padding: 0; border-bottom: 1px solid #AAAAAA;>Heading</div> |
|||
<div style="overflow: hidden; page-break-after: avoid; |
|||
<p>Text attributes <em>italic</em>, |
|||
font-size: 1.5em; font-family: Georgia,Times,serif; margin-top: 1em; margin-bottom: 0.25em; line-height: 1.3; padding: 0; border-bottom: 1px solid #AAAAAA;>Sub-heading</div> |
|||
<strong>bold</strong>, <code>monospace</code>.</p> |
|||
<div style="overflow: hidden; page-break-after: avoid; |
|||
<p>Horizontal rule:</p> |
|||
font-size: 1.8em; font-family: Georgia,Times,serif; margin-top: 1em; margin-bottom: 0.25em; line-height: 1.3; padding: 0; border-bottom: 1px solid #AAAAAA;>Alternative heading</div> |
|||
<div style="overflow: hidden; page-break-after: avoid; |
|||
<hr /> |
|||
font-size: 1.5em; font-family: Georgia,Times,serif; margin-top: 1em; margin-bottom: 0.25em; line-height: 1.3; padding: 0; border-bottom: 1px solid #AAAAAA;>Alternative sub-heading</div> |
|||
Paragraphs are separated |
|||
<p>Strikethrough:</p> |
|||
by a blank line. |
|||
<strike>strikethrough</strike> |
|||
Two spaces at the end of a line<br /> |
|||
<p>Bullet list:</p> |
|||
produce a line break. |
|||
|- |
|||
<ul> |
|||
|<syntaxhighlight lang="md">Text attributes _italic_, **bold**, `monospace`. |
|||
<li>apples</li> |
|||
<li>oranges</li> |
|||
<li>pears</li> |
|||
</ul> |
|||
Horizontal rule: |
|||
<p>Numbered list:</p> |
|||
--- |
|||
<ol> |
|||
<li>lather</li> |
|||
<li>rinse</li> |
|||
<li>repeat</li> |
|||
</ol> |
|||
</syntaxhighlight> |
|||
<p>An <a href="http://example.com">example</a>.</p> |
|||
| |
|||
<syntaxhighlight lang="html"><p>Text attributes <em>italic</em>, <strong>bold</strong>, <code>monospace</code>.</p> |
|||
<p>Horizontal rule:</p> |
|||
<p><img alt="Image" title="icon" src="Icon-pictures.png" /></p> |
|||
<hr /> |
|||
<blockquote> |
|||
<p>Markdown uses email-style > characters for blockquoting.</p> |
|||
</blockquote> |
|||
<p>Inline <abbr title="Hypertext Markup Language">HTML</abbr> is supported.</p> |
|||
</syntaxhighlight> |
</syntaxhighlight> |
||
|Text attributes ''italic'', '''bold''', <code>monospace</code>.</p> |
|||
| |
|||
Horizontal rule: |
|||
<div style="color: #000000; background: none; overflow: hidden; page-break-after: avoid; |
|||
font-size: 1.8em; font-family: Georgia,Times,serif; margin-top: 1em; margin-bottom: 0.25em; line-height: 1.3; padding: 0; border-bottom: 1px solid #AAAAAA;>Heading</div> |
|||
<hr /> |
|||
<div style="color: #000000; background: none; overflow: hidden; page-break-after: avoid; |
|||
font-size: 1.5em; font-family: Georgia,Times,serif; margin-top: 1em; margin-bottom: 0.25em; line-height: 1.3; padding: 0; border-bottom: 1px solid #AAAAAA;>Sub-heading</div> |
|||
|- |
|||
Paragraphs are separated |
|||
|<syntaxhighlight lang="md"> |
|||
by a blank line. |
|||
Bullet lists nested within numbered list: |
|||
1. fruits |
|||
Two spaces at the end of a line<br /> |
|||
* apple |
|||
produces a line break. |
|||
* banana |
|||
2. vegetables |
|||
- carrot |
|||
- broccoli |
|||
</syntaxhighlight> |
|||
| |
|||
<syntaxhighlight lang="html"><p>Bullet lists nested within numbered list:</p> |
|||
<ol> |
|||
Text attributes ''italic'', |
|||
<li>fruits <ul> |
|||
'''bold''', <code>monospace</code>. |
|||
<li>apple</li> |
|||
<li>banana</li> |
|||
</ul></li> |
|||
<li>vegetables <ul> |
|||
<li>carrot</li> |
|||
<li>broccoli</li> |
|||
</ul></li> |
|||
</ol> |
|||
</syntaxhighlight> |
|||
Horizontal rule: |
|||
|Bullet lists nested within numbered list: |
|||
# fruits |
|||
<hr /> |
|||
#* apple |
|||
#* banana |
|||
# vegetables |
|||
#* carrot |
|||
#* broccoli |
|||
|- |
|||
|<syntaxhighlight lang="md">A [link](http://example.com). |
|||
![Image](Icon-pictures.png "icon") |
|||
Strikethrough: |
|||
> Markdown uses email-style |
|||
<s>strikethrough</s> |
|||
characters for blockquoting. |
|||
> |
|||
> Multiple paragraphs need to be prepended individually. |
|||
Most inline <abbr title="Hypertext Markup Language">HTML</abbr> tags are supported. |
|||
</syntaxhighlight> |
|||
| |
|||
<syntaxhighlight lang="html"><p>A <a href="http://example.com">link</a>.</p> |
|||
<p><img alt="Image" title="icon" src="Icon-pictures.png" /></p> |
|||
Bullet list: |
|||
<blockquote> |
|||
* apples |
|||
<p>Markdown uses email-style characters for blockquoting.</p> |
|||
* oranges |
|||
<p>Multiple paragraphs need to be prepended individually.</p> |
|||
* pears |
|||
</blockquote> |
|||
<p>Most inline <abbr title="Hypertext Markup Language">HTML</abbr> tags are supported.</p> |
|||
Numbered list: |
|||
</syntaxhighlight> |
|||
# lather |
|||
|A [http://example.com/ link]. |
|||
# rinse |
|||
# repeat |
|||
An [http://example.com example]. |
|||
[[File:Icon-pictures.png|alt=Image|link=|icon]] |
[[File:Icon-pictures.png|alt=Image|link=|icon]] |
||
<blockquote> |
<blockquote> |
||
Markdown uses email-style |
Markdown uses email-style characters for blockquoting. |
||
Multiple paragraphs need to be prepended individually. |
|||
</blockquote> |
</blockquote> |
||
Most inline <abbr title="Hypertext Markup Language">HTML</abbr> tags are supported. |
|||
<!-- Spare row markup |
|||
|- |
|||
|<syntaxhighlight lang="md">m |
|||
</syntaxhighlight> |
|||
| |
|||
<syntaxhighlight lang="html">h |
|||
</syntaxhighlight> |
|||
|end |
|||
--> |
|||
|} |
|} |
||
==Implementations== |
== Implementations == |
||
Implementations of Markdown are available for over a dozen [[programming language]]s; in addition, many [[Application software|applications]], platforms and [[Software framework|frameworks]] support Markdown.<ref>{{cite web|title=W3C Community Page of Markdown Implementations|url=https://www.w3.org/community/markdown/wiki/MarkdownImplementations|website=W3C Markdown Wiki|access-date=24 March 2016|archive-date=17 September 2020|archive-url=https://web.archive.org/web/20200917231621/https://www.w3.org/community/markdown/wiki/MarkdownImplementations|url-status=live}}</ref> For example, Markdown [[Plug-in (computing)|plugins]] exist for every major [[blog]]ging platform.<ref name="ArsTechnica2014"/> |
|||
<!-- linked from redirect [[GitHub Flavored Markdown]] --> |
|||
Implementations of Markdown are available for over a dozen programming languages; in addition, many platforms and frameworks support Markdown.<ref>{{cite web|title=W3C Community Page of Markdown Implementations|url=https://www.w3.org/community/markdown/wiki/MarkdownImplementations|website=W3C Markdown Wiki|accessdate=24 March 2016}}</ref> For example, Markdown plugins exist for every major blogging platform.<ref>{{cite web | url=https://arstechnica.com/information-technology/2014/10/markdown-throwdown-what-happens-when-foss-software-gets-corporate-backing/ |date=2014-10-05 |title= Markdown THrowdown – What happens when FOSS software gets corporate backing |publisher=Ars Technica}}</ref> |
|||
While Markdown is a minimal markup language and is read and edited with a normal text editor, there are specially designed editors that preview the files with styles, which are available for all major platforms. Many general |
While Markdown is a minimal markup language and is read and edited with a normal [[text editor]], there are specially designed editors that preview the files with styles, which are available for all major platforms. Many general-purpose text and [[Source-code editor|code editors]] have [[syntax highlighting]] plugins for Markdown built into them or available as optional download. Editors may feature a side-by-side preview window or render the code directly in a [[WYSIWYG]] fashion. |
||
Some apps, services and editors support Markdown as an editing format, including: |
|||
* The sourcecode documentation generator [[Doxygen]] supports Markdown with extra features.<ref>{{cite web|url=http://doxygen.nl/manual/markdown.html|title=Doxygen Manual: Markdown support}}</ref> |
|||
* [[RStudio]], an [[Integrated development environment|IDE]] for [[R (programming language)|R]], provides a [[C++]] [[wrapper function]] for a markdown variant called sundown.<ref>{{cite web|url=https://github.com/rstudio/rstudio/blob/master/src/cpp/core/markdown/Markdown.cpp|title=Markdown.cpp|date=2015-06-30<!-- last commit for Markdown.cpp as of July 7, 2016 -->|publisher=[[GitHub]] project [[RStudio]]|author=jjallaire|author-link=Joseph J. Allaire|author2=e.a.|accessdate=2016-07-07}}</ref> |
|||
* GitHub Flavored Markdown (GFM) ignores underscores in words, and adds [[syntax highlighting]], [[task list]]s,<ref>{{cite web|url=https://help.github.com/articles/writing-on-github|title=Writing on GitHub|website=help.github.com|publisher=GitHub, Inc.|accessdate=9 July 2014}}</ref> and tables.<ref name="gfm_on_github2">{{cite web|url=https://help.github.com/articles/github-flavored-markdown|title=GitHub Flavored Markdown|publisher=github.com|accessdate=29 March 2013}}</ref> |
|||
* Discount – a [[C (programming language)|C]] implementation.<ref>{{cite web|url=http://www.pell.portland.or.us/~orc/Code/discount/|title=Discount - a C implementation of the Markdown markup language|accessdate=2014-11-01}}</ref><ref>{{cite web|url=https://github.com/Orc/discount|title=DISCOUNT|author=David Parsons|publisher=[[GitHub]]|quote={{openhub|discount|discount}}|date=2016-05-28<!-- last commit as of July 7, 2016 -->|accessdate=2016-07-07}}</ref> |
|||
* MarkAPL is a converter written in Dyalog [[APL (programming language)|APL]]. It supports fenced blocks, smart typography, link references, and special attributes, and can generate a table of contents.<ref>{{cite web|url=https://github.com/aplteam/MarkAPL|title=Markdown converter written in Dyalog APL.}}</ref> |
|||
* PHP Markdown - a library package that includes the PHP Markdown parser and its sibling PHP Markdown Extra with additional features.<ref>{{cite web|url=https://michelf.ca/projects/php-markdown/|title=PHP Markdown|accessdate=2016-03-01}}</ref> |
|||
* Markdig – A .NET library that follows the CommonMark specifications, and includes a collection of extensions and the ability for the user to create their own. |
|||
* [[Bugzilla]] uses a customized version of Markdown.<ref>{{Cite web |title=330707 - Add optional support for MarkDown |url=https://bugzilla.mozilla.org/show_bug.cgi?id=330707 |access-date=2022-10-11 |website=bugzilla.mozilla.org |language=en |archive-date=2022-10-11 |archive-url=https://web.archive.org/web/20221011143200/https://bugzilla.mozilla.org/show_bug.cgi?id=330707 |url-status=live }}</ref> |
|||
==See also== |
|||
* [[ChatGPT]]: Output from the LLM formatted in Markdown will be rendered in LaTeX and HTML by the ChatGPT client, and the model is encouraged to use Markdown to format its output. Markdown provided by the user will not be formatted by the client, but will still be passed to the model unaltered. |
|||
* [[Discord (software)|Discord]]: chat messages<ref>{{cite web|title=Markdown Text 101 (Chat Formatting: Bold, Italic, Underline)|url=https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline-?page=4|archive-url=https://web.archive.org/web/20200626015843/https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline-?page=4|url-status=dead|archive-date=June 26, 2020|website=discord.com}}</ref> |
|||
* [[Discourse (software)|Discourse]] uses the CommonMark flavor of Markdown in the forum post composer. |
|||
* [[Doxygen]]: a source code documentation generator which supports Markdown with extra features<ref>{{cite web|url=http://doxygen.nl/manual/markdown.html|title=Doxygen Manual: Markdown support|access-date=2019-08-09|archive-date=2019-08-09|archive-url=https://web.archive.org/web/20190809222422/http://doxygen.nl/manual/markdown.html|url-status=live}}</ref> |
|||
* [[GitHub]] Flavored Markdown (GFM) ignores underscores in words, and adds [[syntax highlighting]], [[task list]]s,<ref>{{cite web|url=https://help.github.com/articles/writing-on-github|title=Writing on GitHub|website=help.github.com|publisher=GitHub, Inc.|access-date=9 July 2014|archive-date=4 June 2018|archive-url=https://web.archive.org/web/20180604165012/https://help.github.com/articles/writing-on-github/|url-status=live}}</ref> and tables<ref name="gfm_on_github" /> |
|||
* The [[GNOME Evolution]] email client supports composing messages in Markdown format,<ref>{{cite tweet |user=EvolutionGnome |number=1506712955743883283 |title=Evolution 3.44 is out and already available on #Flathub! Besides many smaller improvements and fixes it brings a markdown editor to compose messages. 👇}}</ref> with the ability to send and render emails in pure Markdown format (<code>Content-Type: text/markdown;</code>) or to convert Markdown to [[plaintext]] or [[HTML email]] when sending. |
|||
* [[Joplin (software)|Joplin]]: a note-taking application that supports markdown formatting<ref>{{Cite web |title=Markdown Guide |url=https://joplinapp.org/markdown/index.html |access-date=2022-07-14 |website=joplinapp.org |language=en |archive-date=2022-09-23 |archive-url=https://web.archive.org/web/20220923082130/https://joplinapp.org/markdown/index.html |url-status=live }}</ref> |
|||
* [[JotterPad]]: an online WYSIWYG editor that supports Markdown and Fountain<ref>{{Cite web|date=2020-11-17|title=Why You Need a WYSIWYG Editor When Writing in Markdown and Fountain|url=https://blog.jotterpad.app/why-need-wysiwyg-markdown-fountain-editor/|access-date=2020-12-06|website=JotterPad Blog|language=en|archive-date=2020-11-27|archive-url=https://web.archive.org/web/20201127173121/https://blog.jotterpad.app/why-need-wysiwyg-markdown-fountain-editor/|url-status=live}}</ref> |
|||
* [[Kanboard]] uses the standard Markdown syntax as its only formatting syntax for task descriptions.<ref>{{Cite web |title=Markdown Syntax — Kanboard documentation |url=https://docs.kanboard.org/en/latest/user_guide/markdown_syntax.html |access-date=2022-10-11 |website=docs.kanboard.org |archive-date=2022-10-11 |archive-url=https://web.archive.org/web/20221011143151/https://docs.kanboard.org/en/latest/user_guide/markdown_syntax.html |url-status=live }}</ref> |
|||
* [[Microsoft Azure DevOps]]' wiki feature supports both common Markdown conventions and GitHub Flavored Markdown<ref>{{cite web | url=https://learn.microsoft.com/en-us/azure/devops/project/wiki/markdown-guidance?view=azure-devops | title=Markdown syntax for files, widgets, wikis - Azure DevOps | date=25 March 2024 | access-date=18 April 2024 | archive-date=18 April 2024 | archive-url=https://web.archive.org/web/20240418165734/https://learn.microsoft.com/en-us/azure/devops/project/wiki/markdown-guidance?view=azure-devops | url-status=live }}</ref> |
|||
* [[Microsoft Teams]]: chat messages<ref>{{Cite web|url=https://support.microsoft.com/en-us/office/use-markdown-formatting-in-teams-4d10bd65-55e2-4b2d-a1f3-2bebdcd2c772|title=Use Markdown formatting in Teams|access-date=2022-01-13|website=[[Microsoft]]|archive-date=2022-01-13|archive-url=https://web.archive.org/web/20220113145710/https://support.microsoft.com/en-us/office/use-markdown-formatting-in-teams-4d10bd65-55e2-4b2d-a1f3-2bebdcd2c772|url-status=live}}</ref> |
|||
* [[Misskey]], its numerous forks and other [[Fediverse]] platforms such as [[Akkoma]]<ref>{{Cite web |title=Akkoma - Magically Expressive Social Media |url=https://akkoma.social/ |access-date=2024-04-18 |website=akkoma.social |language=en |archive-date=2023-04-05 |archive-url=https://web.archive.org/web/20230405054140/https://akkoma.social/ |url-status=live }}</ref> use a custom text format misleadingly called "Misskey-Flavored Markdown (MFM)", with support for standard nestable block quotes <code>></code> and inline emphasis <code>_*`</code> as well as extensions seen elsewhere for <code>@</code> mentions, <code>#</code> tags, custom [[emoji]] <code>:foo:</code>, automatic URL detection and toggleable link target preview, but no support for headings, lists, reference links and other standard Markdown features. It supports a handful of HTML-like tags (<code><small> <center> <plain></code>) and a special notation with English keywords or key-value pairs <code>$[''key=value'' ''content'']</code> for spans with stylistic effects applied, e.g. fonts, blurs, borders and transformations such as flipping, shifting, rotating, scaling and animation, but also for [[furigana]] and search boxes.<ref>{{Cite web |title=MFM |url=https://misskey-hub.net/en/docs/for-users/features/mfm// |access-date=2024-04-18 |website=Misskey Hub |language=en-US |archive-date=2024-03-24 |archive-url=https://web.archive.org/web/20240324181300/https://misskey-hub.net/en/docs/for-users/features/mfm/ |url-status=live }}</ref> The message format of such [[ActivityPub]] objects that can be consumed as messages is <code>text/x.misskeymarkdown</code>. |
|||
* The [[Mozilla Thunderbird]] email client supports Markdown through the "[https://addons.thunderbird.net/en-US/thunderbird/addon/markdown-here-revival/ Markdown here Revival]" add-on. |
|||
* [[Nextcloud|Nextcloud Notes]]: the default app for taking notes on the Nextcloud platform supports formatting using Markdown<ref>{{Cite web|title=Nextcloud Notes * App|url=https://apps.nextcloud.com/apps/notes|access-date=2022-02-18|website=Nextcloud Apps|language=en|archive-date=2022-02-18|archive-url=https://web.archive.org/web/20220218082520/https://apps.nextcloud.com/apps/notes|url-status=live}}</ref> |
|||
* [[Obsidian (software)|Obsidian]] is note-taking software based on Markdown files.<ref>{{Cite web |title=Obsidian |url=https://obsidian.md/ |access-date=2022-07-14 |website=obsidian.md |language=en |archive-date=2022-07-12 |archive-url=https://web.archive.org/web/20220712202219/https://obsidian.md/ |url-status=live }}</ref> |
|||
* [[RMarkdown]]<ref>{{Cite book|url=https://bookdown.org/yihui/rmarkdown/|title=R Markdown: The Definitive Guide|access-date=2021-08-23|archive-date=2021-04-13|archive-url=https://web.archive.org/web/20210413073844/https://bookdown.org/yihui/rmarkdown/|url-status=live}}</ref> |
|||
* [[RStudio]]: an [[Integrated development environment|IDE]] for [[R (programming language)|R]]. It provides a [[C++]] [[wrapper function]] for a markdown variant called sundown<ref>{{cite web|url=https://github.com/rstudio/rstudio/blob/master/src/cpp/core/markdown/Markdown.cpp|title=Markdown.cpp|date=2015-06-30<!-- last commit for Markdown.cpp as of July 7, 2016 -->|publisher=[[GitHub]] project [[RStudio]]|first1=J.J.|last1=Allaire|author-link1=Joseph J. Allaire|author2=e.a.|access-date=2016-07-07|archive-date=2017-07-26|archive-url=https://web.archive.org/web/20170726011514/https://github.com/rstudio/rstudio/blob/master/src/cpp/core/markdown/Markdown.cpp|url-status=live}}</ref> |
|||
* [[Simplenote]]<ref>{{Cite web |date=2015-07-30 |title=Help |url=https://simplenote.com/help/ |access-date=2022-07-14 |website=Simplenote |language=en |archive-date=2022-07-14 |archive-url=https://web.archive.org/web/20220714190437/https://simplenote.com/help/ |url-status=live }}</ref> |
|||
== See also == |
|||
* [[Comparison of document markup languages]] |
* [[Comparison of document markup languages]] |
||
* [[Comparison of documentation generators]] |
* [[Comparison of documentation generators]] |
||
Line 281: | Line 317: | ||
* [[Wiki markup]] |
* [[Wiki markup]] |
||
== Explanatory notes == |
|||
==References== |
|||
{{ |
{{Reflist|group=note}} |
||
== References == |
|||
{{Reflist|30em|refs= |
|||
<ref name="ArsTechnica2014">{{cite news |last=Gilbertson |date=October 5, 2014 |first=Scott |title=Markdown throwdown: What happens when FOSS software gets corporate backing? |url=https://arstechnica.com/information-technology/2014/10/markdown-throwdown-what-happens-when-foss-software-gets-corporate-backing/ |work=[[Ars Technica]] |access-date=June 14, 2017 |archive-date=November 14, 2020 |archive-url=https://web.archive.org/web/20201114231130/https://arstechnica.com/information-technology/2014/10/markdown-throwdown-what-happens-when-foss-software-gets-corporate-backing/ |url-status=live |quote=[[CommonMark]] fork could end up better for users... but original creators seem to disagree.}}</ref> |
|||
}} |
|||
==External links== |
== External links == |
||
* {{ |
* {{Official website|https://daringfireball.net/projects/markdown/}} for original John Gruber markup |
||
{{Document markup languages}} |
{{Document markup languages}} |
||
{{Authority control|state=autocollapse}} |
|||
[[Category:Computer-related introductions in 2004]] |
[[Category:Computer-related introductions in 2004]] |
||
[[Category:Lightweight markup languages]] |
[[Category:Lightweight markup languages]] |
||
[[Category:Note-taking]] |
|||
[[Category:Open formats]] |
[[Category:Open formats]] |
Latest revision as of 14:25, 4 January 2025
Filename extensions | |
---|---|
Internet media type | text/markdown [2] |
Uniform Type Identifier (UTI) | net.daringfireball.markdown |
Developed by | |
Initial release | March 9, 2004[3][4] |
Latest release | 1.0.1 December 17, 2004[5] |
Type of format | Open file format[6] |
Extended to | pandoc, MultiMarkdown, Markdown Extra, CommonMark,[7] RMarkdown[8] |
Website | daringfireball |
Markdown[9] is a lightweight markup language for creating formatted text using a plain-text editor. John Gruber created Markdown in 2004 as an easy-to-read markup language.[9] Markdown is widely used for blogging and instant messaging, and also used elsewhere in online forums, collaborative software, documentation pages, and readme files.
The initial description of Markdown[10] contained ambiguities and raised unanswered questions, causing implementations to both intentionally and accidentally diverge from the original version. This was addressed in 2014 when long-standing Markdown contributors released CommonMark, an unambiguous specification and test suite for Markdown.[11]
History
[edit]Markdown was inspired by pre-existing conventions for marking up plain text in email and usenet posts,[12] such as the earlier markup languages setext (c. 1992), Textile (c. 2002), and reStructuredText (c. 2002).[9]
In 2002 Aaron Swartz created atx and referred to it as "the true structured text format". Gruber created the Markdown language in 2004 with Swartz as his "sounding board".[13] The goal of the language was to enable people "to write using an easy-to-read and easy-to-write plain text format, optionally convert it to structurally valid XHTML (or HTML)".[5]
Another key design goal was readability, that the language be readable as-is, without looking like it has been marked up with tags or formatting instructions,[9] unlike text formatted with "heavier" markup languages, such as Rich Text Format (RTF), HTML, or even wikitext (each of which have obvious in-line tags and formatting instructions which can make the text more difficult for humans to read).
Gruber wrote a Perl script, Markdown.pl
, which converts marked-up text input to valid, well-formed XHTML or HTML and replaces angle brackets (<
, >
) and ampersands (&
) with their corresponding character entity references. It can take the role of a standalone script, a plugin for Blosxom or a Movable Type, or of a text filter for BBEdit.[5]
Rise and divergence
[edit]As Markdown's popularity grew rapidly, many Markdown implementations appeared, driven mostly by the need for additional features such as tables, footnotes, definition lists,[note 1] and Markdown inside HTML blocks.
The behavior of some of these diverged from the reference implementation, as Markdown was only characterised by an informal specification[16] and a Perl implementation for conversion to HTML.
At the same time, a number of ambiguities in the informal specification had attracted attention.[17] These issues spurred the creation of tools such as Babelmark[18][19] to compare the output of various implementations,[20] and an effort by some developers of Markdown parsers for standardisation. However, Gruber has argued that complete standardization would be a mistake: "Different sites (and people) have different needs. No one syntax would make all happy."[21]
Gruber avoided using curly braces in Markdown to unofficially reserve them for implementation-specific extensions.[22]
Standardization
[edit]Filename extensions | .md , .markdown [2] |
---|---|
Internet media type | text/markdown; variant=CommonMark [7] |
Uniform Type Identifier (UTI) | uncertain[23] |
UTI conformation | public.plain-text |
Developed by | John MacFarlane, open source |
Initial release | October 25, 2014 |
Latest release | 0.31.2 January 28, 2024[24] |
Type of format | Open file format |
Extended from | Markdown |
Extended to | GitHub Flavored Markdown |
Website | commonmark |
From 2012, a group of people, including Jeff Atwood and John MacFarlane, launched what Atwood characterised as a standardisation effort.[11]
A community website now aims to "document various tools and resources available to document authors and developers, as well as implementors of the various Markdown implementations".[25]
In September 2014, Gruber objected to the usage of "Markdown" in the name of this effort and it was rebranded as CommonMark.[12][26][27] CommonMark.org published several versions of a specification, reference implementation, test suite, and "[plans] to announce a finalized 1.0 spec and test suite in 2019".[28]
No 1.0 spec has since been released, as major issues still remain unsolved.[29]
Nonetheless, the following websites and projects have adopted CommonMark: Discourse, GitHub, GitLab, Reddit, Qt, Stack Exchange (Stack Overflow), and Swift.
In March 2016, two relevant informational Internet RFCs were published:
- RFC 7763 introduced MIME type
text/markdown
. - RFC 7764 discussed and registered the variants MultiMarkdown, GitHub Flavored Markdown (GFM), Pandoc, and Markdown Extra among others.[30]
Variants
[edit]Websites like Bitbucket, Diaspora, GitHub,[31] OpenStreetMap, Reddit,[32] SourceForge[33] and Stack Exchange[34] use variants of Markdown to make discussions between users easier.
Depending on implementation, basic inline HTML tags may be supported.[35]
Italic text may be implemented by _underscores_
or *single-asterisks*
.[36]
GitHub Flavored Markdown
[edit]GitHub had been using its own variant of Markdown since as early as 2009,[37] which added support for additional formatting such as tables and nesting block content inside list elements, as well as GitHub-specific features such as auto-linking references to commits, issues, usernames, etc.
In 2017, GitHub released a formal specification of its GitHub Flavored Markdown (GFM) that is based on CommonMark.[31] It is a strict superset of CommonMark, following its specification exactly except for tables, strikethrough, autolinks and task lists, which GFM adds as extensions.[38]
Accordingly, GitHub also changed the parser used on their sites, which required that some documents be changed. For instance, GFM now requires that the hash symbol that creates a heading be separated from the heading text by a space character.
Markdown Extra
[edit]Markdown Extra is a lightweight markup language based on Markdown implemented in PHP (originally), Python and Ruby.[39] It adds the following features that are not available with regular Markdown:
- Markdown markup inside HTML blocks
- Elements with id/class attribute
- "Fenced code blocks" that span multiple lines of code
- Tables[40]
- Definition lists
- Footnotes
- Abbreviations
Markdown Extra is supported in some content management systems such as Drupal,[41] Grav (CMS) and TYPO3.[42]
Examples
[edit]Text using Markdown syntax | Corresponding HTML produced by a Markdown processor | Text viewed in a browser |
---|---|---|
Heading
=======
Sub-heading
-----------
# Alternative heading
## Alternative sub-heading
Paragraphs are separated
by a blank line.
Two spaces at the end of a line
produce a line break.
|
<h1>Heading</h1>
<h2>Sub-heading</h2>
<h1>Alternative heading</h1>
<h2>Alternative sub-heading</h2>
<p>Paragraphs are separated
by a blank line.</p>
<p>Two spaces at the end of a line<br />
produce a line break.</p>
|
Paragraphs are separated by a blank line. Two spaces at the end of a line |
Text attributes _italic_, **bold**, `monospace`.
Horizontal rule:
---
|
<p>Text attributes <em>italic</em>, <strong>bold</strong>, <code>monospace</code>.</p>
<p>Horizontal rule:</p>
<hr />
|
Text attributes italic, bold, monospace .
Horizontal rule: |
Bullet lists nested within numbered list:
1. fruits
* apple
* banana
2. vegetables
- carrot
- broccoli
|
<p>Bullet lists nested within numbered list:</p>
<ol>
<li>fruits <ul>
<li>apple</li>
<li>banana</li>
</ul></li>
<li>vegetables <ul>
<li>carrot</li>
<li>broccoli</li>
</ul></li>
</ol>
|
Bullet lists nested within numbered list:
|
A [link](http://example.com).
![Image](Icon-pictures.png "icon")
> Markdown uses email-style
characters for blockquoting.
>
> Multiple paragraphs need to be prepended individually.
Most inline <abbr title="Hypertext Markup Language">HTML</abbr> tags are supported.
|
<p>A <a href="http://example.com">link</a>.</p>
<p><img alt="Image" title="icon" src="Icon-pictures.png" /></p>
<blockquote>
<p>Markdown uses email-style characters for blockquoting.</p>
<p>Multiple paragraphs need to be prepended individually.</p>
</blockquote>
<p>Most inline <abbr title="Hypertext Markup Language">HTML</abbr> tags are supported.</p>
|
A link.
Most inline HTML tags are supported. |
Implementations
[edit]Implementations of Markdown are available for over a dozen programming languages; in addition, many applications, platforms and frameworks support Markdown.[43] For example, Markdown plugins exist for every major blogging platform.[12]
While Markdown is a minimal markup language and is read and edited with a normal text editor, there are specially designed editors that preview the files with styles, which are available for all major platforms. Many general-purpose text and code editors have syntax highlighting plugins for Markdown built into them or available as optional download. Editors may feature a side-by-side preview window or render the code directly in a WYSIWYG fashion.
Some apps, services and editors support Markdown as an editing format, including:
- Bugzilla uses a customized version of Markdown.[44]
- ChatGPT: Output from the LLM formatted in Markdown will be rendered in LaTeX and HTML by the ChatGPT client, and the model is encouraged to use Markdown to format its output. Markdown provided by the user will not be formatted by the client, but will still be passed to the model unaltered.
- Discord: chat messages[45]
- Discourse uses the CommonMark flavor of Markdown in the forum post composer.
- Doxygen: a source code documentation generator which supports Markdown with extra features[46]
- GitHub Flavored Markdown (GFM) ignores underscores in words, and adds syntax highlighting, task lists,[47] and tables[31]
- The GNOME Evolution email client supports composing messages in Markdown format,[48] with the ability to send and render emails in pure Markdown format (
Content-Type: text/markdown;
) or to convert Markdown to plaintext or HTML email when sending. - Joplin: a note-taking application that supports markdown formatting[49]
- JotterPad: an online WYSIWYG editor that supports Markdown and Fountain[50]
- Kanboard uses the standard Markdown syntax as its only formatting syntax for task descriptions.[51]
- Microsoft Azure DevOps' wiki feature supports both common Markdown conventions and GitHub Flavored Markdown[52]
- Microsoft Teams: chat messages[53]
- Misskey, its numerous forks and other Fediverse platforms such as Akkoma[54] use a custom text format misleadingly called "Misskey-Flavored Markdown (MFM)", with support for standard nestable block quotes
>
and inline emphasis_*`
as well as extensions seen elsewhere for@
mentions,#
tags, custom emoji:foo:
, automatic URL detection and toggleable link target preview, but no support for headings, lists, reference links and other standard Markdown features. It supports a handful of HTML-like tags (<small> <center> <plain>
) and a special notation with English keywords or key-value pairs$[key=value content]
for spans with stylistic effects applied, e.g. fonts, blurs, borders and transformations such as flipping, shifting, rotating, scaling and animation, but also for furigana and search boxes.[55] The message format of such ActivityPub objects that can be consumed as messages istext/x.misskeymarkdown
. - The Mozilla Thunderbird email client supports Markdown through the "Markdown here Revival" add-on.
- Nextcloud Notes: the default app for taking notes on the Nextcloud platform supports formatting using Markdown[56]
- Obsidian is note-taking software based on Markdown files.[57]
- RMarkdown[58]
- RStudio: an IDE for R. It provides a C++ wrapper function for a markdown variant called sundown[59]
- Simplenote[60]
See also
[edit]- Comparison of document markup languages
- Comparison of documentation generators
- Lightweight markup language
- Wiki markup
Explanatory notes
[edit]- ^ Technically HTML description lists
References
[edit]- ^ Gruber, John (8 January 2014). "The Markdown File Extension". The Daring Fireball Company, LLC. Archived from the original on 12 July 2020. Retrieved 27 March 2022.
Too late now, I suppose, but the only file extension I would endorse is ".markdown", for the same reason offered by Hilton Lipschitz: We no longer live in a 8.3 world, so we should be using the most descriptive file extensions. It's sad that all our operating systems rely on this stupid convention instead of the better creator code or a metadata model, but great that they now support longer file extensions.
- ^ a b c Leonard, Sean (March 2016). "The text/markdown Media Type". Request for Comments: 7763. Internet Engineering Task Force. Archived from the original on 22 March 2022. Retrieved 27 March 2022.
This document registers the text/markdown media type for use with Markdown, a family of plain-text formatting syntaxes that optionally can be converted to formal markup languages such as HTML.
- ^ Swartz, Aaron (2004-03-19). "Markdown". Aaron Swartz: The Weblog. Archived from the original on 2017-12-24. Retrieved 2013-09-01.
- ^ Gruber, John. "Markdown". Daring Fireball. Archived from the original on 2004-03-11. Retrieved 2022-08-20.
- ^ a b c Markdown 1.0.1 readme source code "Daring Fireball – Markdown". 2004-12-17. Archived from the original on 2004-04-02.
- ^ "Markdown: License". Daring Fireball. Archived from the original on 2020-02-18. Retrieved 2014-04-25.
- ^ a b Leonard, Sean (March 2016). "Guidance on Markdown: Design Philosophies, Stability Strategies, and Select Registrations". Request for Comments: 7764. Internet Engineering Task Force. Archived from the original on 17 April 2022. Retrieved 27 March 2022.
This document elaborates upon the text/markdown media type for use with Markdown, a family of plain-text formatting syntaxes that optionally can be converted to formal markup languages such as HTML. Background information, local storage strategies, and additional syntax registrations are supplied.
- ^ "RMarkdown Reference site". Archived from the original on 2020-03-03. Retrieved 2019-11-21.
- ^ a b c d Markdown Syntax "Daring Fireball – Markdown – Syntax". 2013-06-13. "Readability, however, is emphasized above all else. 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. While Markdown's syntax has been influenced by several existing text-to-HTML filters — including Setext, atx, Textile, reStructuredText, Grutatext[14], and EtText[15] — the single biggest source of inspiration for Markdown's syntax is the format of plain text email."
- ^ "Daring Fireball: Introducing Markdown". daringfireball.net. Archived from the original on 2020-09-20. Retrieved 2020-09-23.
- ^ a b Atwood, Jeff (2012-10-25). "The Future of Markdown". CodingHorror.com. Archived from the original on 2014-02-11. Retrieved 2014-04-25.
- ^ a b c Gilbertson, Scott (October 5, 2014). "Markdown throwdown: What happens when FOSS software gets corporate backing?". Ars Technica. Archived from the original on November 14, 2020. Retrieved June 14, 2017.
CommonMark fork could end up better for users... but original creators seem to disagree.
- ^ @gruber (June 12, 2016). "I should write about it, but it's painful. More or less: Aaron was my sounding board, my muse" (Tweet) – via Twitter.
- ^ "Un naufragio personal: The Grutatxt markup". triptico.com. Retrieved 2022-06-30.
- ^ "EtText: Documentation: Using EtText". ettext.taint.org. Retrieved 2022-06-30.
- ^ "Markdown Syntax Documentation". Daring Fireball. Archived from the original on 2019-09-09. Retrieved 2018-03-09.
- ^ "GitHub Flavored Markdown Spec – Why is a spec needed?". github.github.com. Archived from the original on 2020-02-03. Retrieved 2018-05-17.
- ^ "Babelmark 2 – Compare markdown implementations". Johnmacfarlane.net. Archived from the original on 2017-07-18. Retrieved 2014-04-25.
- ^ "Babelmark 3 – Compare Markdown Implementations". github.io. Archived from the original on 2020-11-12. Retrieved 2017-12-10.
- ^ "Babelmark 2 – FAQ". Johnmacfarlane.net. Archived from the original on 2017-07-28. Retrieved 2014-04-25.
- ^ Gruber, John [@gruber] (4 September 2014). "@tobie @espadrine @comex @wycats Because different sites (and people) have different needs. No one syntax would make all happy" (Tweet) – via Twitter.
- ^ Gruber, John (19 May 2022). "Markdoc". Daring Fireball. Archived from the original on 19 May 2022. Retrieved May 19, 2022.
I love their syntax extensions — very true to the spirit of Markdown. They use curly braces for their extensions; I'm not sure I ever made this clear, publicly, but I avoided using curly braces in Markdown itself — even though they are very tempting characters — to unofficially reserve them for implementation-specific extensions. Markdoc's extensive use of curly braces for its syntax is exactly the sort of thing I was thinking about.
- ^ "UTI of a CommonMark document". 12 April 2017. Archived from the original on 22 November 2018. Retrieved 29 September 2017.
- ^ "CommonMark specification". Archived from the original on 2017-08-07. Retrieved 2017-07-26.
- ^ "Markdown Community Page". GitHub. Archived from the original on 2020-10-26. Retrieved 2014-04-25.
- ^ "Standard Markdown is now Common Markdown". Jeff Atwood. 4 September 2014. Archived from the original on 2014-10-09. Retrieved 2014-10-07.
- ^ "Standard Markdown Becomes Common Markdown then CommonMark". InfoQ. Archived from the original on 2020-09-30. Retrieved 2014-10-07.
- ^ "CommonMark". Archived from the original on 12 April 2016. Retrieved 20 Jun 2018.
The current version of the CommonMark spec is complete, and quite robust after a year of public feedback … but not quite final. With your help, we plan to announce a finalized 1.0 spec and test suite in 2019.
- ^ "Issues we MUST resolve before 1.0 release [6 remaining]". CommonMark Discussion. 2015-07-26. Archived from the original on 2021-04-14. Retrieved 2020-10-02.
- ^ "Markdown Variants". IANA. 2016-03-28. Archived from the original on 2020-10-27. Retrieved 2016-07-06.
- ^ a b c "GitHub Flavored Markdown Spec". GitHub. Archived from the original on 2020-02-03. Retrieved 2020-06-11.
- ^ "Reddit markdown primer. Or, how do you do all that fancy formatting in your comments, anyway?". Reddit. Archived from the original on 2019-06-11. Retrieved 2013-03-29.
- ^ "SourceForge: Markdown Syntax Guide". SourceForge. Archived from the original on 2019-06-13. Retrieved 2013-05-10.
- ^ "Markdown Editing Help". StackOverflow.com. Archived from the original on 2014-03-28. Retrieved 2014-04-11.
- ^ "Markdown Syntax Documentation". daringfireball.net. Archived from the original on 2019-09-09. Retrieved 2021-03-01.
- ^ "Basic Syntax: Italic". The Markdown Guide. Matt Cone. Archived from the original on 26 March 2022. Retrieved 27 March 2022.
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.
- ^ Tom Preston-Werner. "GitHub Flavored Markdown Examples". GitHub. Archived from the original on 2021-05-13. Retrieved 2021-04-02.
- ^ "A formal spec for GitHub Flavored Markdown". GitHub Engineering. 14 March 2017. Archived from the original on 3 February 2020. Retrieved 16 Mar 2017.
- ^ Fortin, Michel (2018). "PHP Markdown Extra". Michel Fortin website. Archived from the original on 2021-01-17. Retrieved 2018-12-26.
- ^ "PHP Markdown Extra". Michel Fortin. Archived from the original on 2021-01-17. Retrieved 2018-12-26.
- ^ "Markdown editor for BUEditor". 4 December 2008. Archived from the original on 17 September 2020. Retrieved 15 January 2017.
- ^ "Markdown for TYPO3 (markdown_content)". extensions.typo3.org. Archived from the original on 2021-02-01. Retrieved 2019-02-06.
- ^ "W3C Community Page of Markdown Implementations". W3C Markdown Wiki. Archived from the original on 17 September 2020. Retrieved 24 March 2016.
- ^ "330707 - Add optional support for MarkDown". bugzilla.mozilla.org. Archived from the original on 2022-10-11. Retrieved 2022-10-11.
- ^ "Markdown Text 101 (Chat Formatting: Bold, Italic, Underline)". discord.com. Archived from the original on June 26, 2020.
- ^ "Doxygen Manual: Markdown support". Archived from the original on 2019-08-09. Retrieved 2019-08-09.
- ^ "Writing on GitHub". help.github.com. GitHub, Inc. Archived from the original on 4 June 2018. Retrieved 9 July 2014.
- ^ @EvolutionGnome (March 23, 2022). "Evolution 3.44 is out and already available on #Flathub! Besides many smaller improvements and fixes it brings a markdown editor to compose messages. 👇" (Tweet) – via Twitter.
- ^ "Markdown Guide". joplinapp.org. Archived from the original on 2022-09-23. Retrieved 2022-07-14.
- ^ "Why You Need a WYSIWYG Editor When Writing in Markdown and Fountain". JotterPad Blog. 2020-11-17. Archived from the original on 2020-11-27. Retrieved 2020-12-06.
- ^ "Markdown Syntax — Kanboard documentation". docs.kanboard.org. Archived from the original on 2022-10-11. Retrieved 2022-10-11.
- ^ "Markdown syntax for files, widgets, wikis - Azure DevOps". 25 March 2024. Archived from the original on 18 April 2024. Retrieved 18 April 2024.
- ^ "Use Markdown formatting in Teams". Microsoft. Archived from the original on 2022-01-13. Retrieved 2022-01-13.
- ^ "Akkoma - Magically Expressive Social Media". akkoma.social. Archived from the original on 2023-04-05. Retrieved 2024-04-18.
- ^ "MFM". Misskey Hub. Archived from the original on 2024-03-24. Retrieved 2024-04-18.
- ^ "Nextcloud Notes * App". Nextcloud Apps. Archived from the original on 2022-02-18. Retrieved 2022-02-18.
- ^ "Obsidian". obsidian.md. Archived from the original on 2022-07-12. Retrieved 2022-07-14.
- ^ R Markdown: The Definitive Guide. Archived from the original on 2021-04-13. Retrieved 2021-08-23.
- ^ Allaire, J.J.; e.a. (2015-06-30). "Markdown.cpp". GitHub project RStudio. Archived from the original on 2017-07-26. Retrieved 2016-07-07.
- ^ "Help". Simplenote. 2015-07-30. Archived from the original on 2022-07-14. Retrieved 2022-07-14.
External links
[edit]- Official website for original John Gruber markup