Markdown: Difference between revisions

CommonMark
Filename extensions	.md, .markdown
Internet media type	text/markdown; variant=CommonMark
Uniform Type Identifier (UTI)	uncertain
UTI conformation	public.plain-text
Developed by	John MacFarlane, open source
Initial release	October 25, 2014 (9 years ago)
Latest release	0.30; June 19, 2021 (2 years ago)
Type of format	Open file format
Extended from	Markdown
Extended to	GitHub Flavored Markdown
Website	commonmark.org spec.commonmark.org

Markdown
Filename extensions	.md, .markdown
Internet media type	text/markdown
Uniform Type Identifier (UTI)	net.daringfireball.markdown
Developed by	John Gruber;
Initial release	March 9, 2004 (20 years ago)
Latest release	1.0.1; December 17, 2004 (19 years ago)
Type of format	Open file format
Extended to	pandoc, MultiMarkdown, Markdown Extra, CommonMark, RMarkdown
Website	daringfireball.net/projects/markdown/

Browse history interactively

← Previous edit Next edit →

Content deleted Content added

VisualWikitext

Inline

Revision as of 09:03, 20 May 2024

Markdown^[9] is a lightweight markup language for creating formatted text using a plain-text editor. John Gruber created Markdown in 2004, in collaboration with Aaron Swartz,^[10]^[11] as a markup language that is intended to be easy to read in its source code form.^[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^[12] 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.^[13]

History

Markdown was inspired by pre-existing conventions for marking up plain text in email and usenet posts, 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."^[14] The goal of 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]

Its 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

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^[17] and a Perl implementation for conversion to HTML.

At the same time, a number of ambiguities in the informal specification had attracted attention.^[18] These issues spurred the creation of tools such as Babelmark^[19]^[20] to compare the output of various implementations,^[21] 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."^[22]

Gruber avoided using curly braces in Markdown to unofficially reserve them for implementation-specific extensions.^[23]

Standardization

From 2012, a group of people, including Jeff Atwood and John MacFarlane, launched what Atwood characterised as a standardisation effort.^[13] 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".^[26] In September 2014, Gruber objected to the usage of "Markdown" in the name of this effort and it was rebranded as CommonMark.^[27]^[28] 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."^[29] No 1.0 spec has since been released as major issues still remain unsolved.^[30] 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.^[31]

Variants

Websites like Bitbucket, Diaspora, GitHub,^[32] OpenStreetMap, Reddit,^[33] SourceForge,^[34] and Stack Exchange^[35] use variants of Markdown to make discussions between users easier.

Depending on implementation, basic inline HTML tags may be supported.^[36] Italic text may be implemented by _underscores_ or *single-asterisks*.^[37]

GitHub Flavored Markdown

GitHub had been using its own variant of Markdown since as early as 2009,^[38] 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.^[32] It is a strict superset of CommonMark, following its specification exactly except for tables, strikethrough, autolinks and task lists, which GFM adds as extensions.^[39] 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

Markdown Extra is a lightweight markup language based on Markdown implemented in PHP (originally), Python and Ruby.^[40] 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^[41]
Definition lists
Footnotes
Abbreviations

Markdown Extra is supported in some content management systems such as Drupal,^[42] Grav (CMS) and TYPO3.^[43]

LiaScript

LiaScript^[44] is a Markdown dialect that was designed to create interactive educational content. It is implemented in Elm and TypeScript and adds additional syntax elements to define features like:

Animations
Automatic speech output
Mathematical formulas (using KaTeX)
ASCII art diagrams
Various types of quizzes and surveys
JavaScript is natively supported and can be attached to various elements, this way code fragments can be made executable and editable

Examples

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>	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.
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: fruits apple banana vegetables carrot broccoli
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. Markdown uses email-style characters for blockquoting. Multiple paragraphs need to be prepended individually. Most inline HTML tags are supported.

Implementations

Implementations of Markdown are available for over a dozen programming languages; in addition, many applications, platforms and frameworks support Markdown.^[45] For example, Markdown plugins exist for every major blogging platform.^[46]

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.^[47]
ChatGPT: Output from the AI model 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 AI model unaltered.
Discord: chat messages^[48]
Discourse uses the CommonMark flavor of Markdown in the forum post composer.
Doxygen: a source code documentation generator which supports Markdown with extra features^[49]
GitHub Flavored Markdown (GFM) ignores underscores in words, and adds syntax highlighting, task lists,^[50] and tables^[32]
The GNOME Evolution email client supports composing messages in Markdown format,^[51] 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^[52]
JotterPad: an online WYSIWYG editor that supports Markdown and Fountain^[53]
Kanboard uses the standard Markdown syntax as its only formatting syntax for task descriptions.^[54]
Microsoft Azure DevOps' wiki feature has its own implementation^[55]
Microsoft Teams: chat messages^[56]
Misskey, its numerous forks and other Fediverse platforms such as Akkoma^[57] 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.^[58] The message format of such ActivityPub objects that can be consumed as messages is text/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^[59]
Obsidian is note-taking software based on Markdown files.^[60]
RMarkdown^[61]
RStudio: an IDE for R. It provides a C++ wrapper function for a markdown variant called sundown^[62]
Simplenote^[63]

Explanatory notes

^ Technically HTML description lists

References

^ 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^[15], and EtText^[16] — the single biggest source of inspiration for Markdown's syntax is the format of plain text email."
^ Hendler, James (10 November 2022). "Foreword by James Hendler". Aaron Swartz's A Programmable Web: An Unfinished Work (PDF). Synthesis Lectures on Data, Semantics, and Knowledge. Springer Nature Switzerland. pp. ix. doi:10.1007/978-3-031-79444-5. ISBN 978-3-031-79444-5. Retrieved 12 January 2024 – via Wikisource. This document was originally produced in "markdown" format, a simplified HTML/Wiki format that Aaron co-designed with John Gruber ca. 2004.
^ Krewinkel, Albert; Winkler, Robert (8 May 2017). "Formatting Open Science: agilely creating multiple document formats for academic manuscripts with Pandoc Scholar". PeerJ Computer Science. 3: 6. doi:10.7717/peerj-cs.112. S2CID 26747579. Markdown was originally developed by John Gruber in collaboration with Aaron Swartz, with the goal to simplify the writing of HTML documents
^ "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.
^ @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] (September 4, 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.
^ Dietrich, André. "LiaScript". liascript.github.io. Archived from the original on 2022-01-19. Retrieved 2022-01-17.
^ "W3C Community Page of Markdown Implementations". W3C Markdown Wiki. Archived from the original on 17 September 2020. Retrieved 24 March 2016.
^ "Markdown THrowdown – What happens when FOSS software gets corporate backing". Ars Technica. 2014-10-05. Archived from the original on 2020-11-14. Retrieved 2017-06-14.
^ "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.
^ "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. Retrieved 2024-04-18.
^ "MFM". Misskey Hub. 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

Official website for original John Gruber markup

[17] Technically HTML description lists

[df-2022-1] 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.

[rfc7763-2] 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.

[markdown-swartz-3] Swartz, Aaron (2004-03-19). "Markdown". Aaron Swartz: The Weblog. Archived from the original on 2017-12-24. Retrieved 2013-09-01.

[gruber-2004-release-4] Gruber, John. "Markdown". Daring Fireball. Archived from the original on 2004-03-11. Retrieved 2022-08-20.

[md-5] Markdown 1.0.1 readme source code "Daring Fireball – Markdown". 2004-12-17. Archived from the original on 2004-04-02.

[license-6] "Markdown: License". Daring Fireball. Archived from the original on 2020-02-18. Retrieved 2014-04-25.

[rfc7764-7] 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-8] "RMarkdown Reference site". Archived from the original on 2020-03-03. Retrieved 2019-11-21.

[philosophy-9] 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^[15], and EtText^[16] — the single biggest source of inspiration for Markdown's syntax is the format of plain text email."

[Hendler_2022-10] Hendler, James (10 November 2022). "Foreword by James Hendler". Aaron Swartz's A Programmable Web: An Unfinished Work (PDF). Synthesis Lectures on Data, Semantics, and Knowledge. Springer Nature Switzerland. pp. ix. doi:10.1007/978-3-031-79444-5. ISBN 978-3-031-79444-5. Retrieved 12 January 2024 – via Wikisource. This document was originally produced in "markdown" format, a simplified HTML/Wiki format that Aaron co-designed with John Gruber ca. 2004.

[PeerJ_2017-11] Krewinkel, Albert; Winkler, Robert (8 May 2017). "Formatting Open Science: agilely creating multiple document formats for academic manuscripts with Pandoc Scholar". PeerJ Computer Science. 3: 6. doi:10.7717/peerj-cs.112. S2CID 26747579. Markdown was originally developed by John Gruber in collaboration with Aaron Swartz, with the goal to simplify the writing of HTML documents

[12] "Daring Fireball: Introducing Markdown". daringfireball.net. Archived from the original on 2020-09-20. Retrieved 2020-09-23.

[FutureOfMarkdown-13] Atwood, Jeff (2012-10-25). "The Future of Markdown". CodingHorror.com. Archived from the original on 2014-02-11. Retrieved 2014-04-25.

[Gruber-14] @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.

[grutatext-15] "Un naufragio personal: The Grutatxt markup". triptico.com. Retrieved 2022-06-30.

[ettext-16] "EtText: Documentation: Using EtText". ettext.taint.org. Retrieved 2022-06-30.

[18] "Markdown Syntax Documentation". Daring Fireball. Archived from the original on 2019-09-09. Retrieved 2018-03-09.

[gfm_on_github-why_spec-19] "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-20] "Babelmark 2 – Compare markdown implementations". Johnmacfarlane.net. Archived from the original on 2017-07-18. Retrieved 2014-04-25.

[babelmark-3-21] "Babelmark 3 – Compare Markdown Implementations". github.io. Archived from the original on 2020-11-12. Retrieved 2017-12-10.

[22] "Babelmark 2 – FAQ". Johnmacfarlane.net. Archived from the original on 2017-07-28. Retrieved 2014-04-25.

[23] Gruber, John [@gruber] (September 4, 2014). "@tobie @espadrine @comex @wycats Because different sites (and people) have different needs. No one syntax would make all happy" (Tweet) – via Twitter.

[curlyBraces-24] 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.

[cm-uti-25] "UTI of a CommonMark document". 12 April 2017. Archived from the original on 22 November 2018. Retrieved 29 September 2017.

[cm-spec-26] "CommonMark specification". Archived from the original on 2017-08-07. Retrieved 2017-07-26.

[27] "Markdown Community Page". GitHub. Archived from the original on 2020-10-26. Retrieved 2014-04-25.

[28] "Standard Markdown is now Common Markdown". Jeff Atwood. 4 September 2014. Archived from the original on 2014-10-09. Retrieved 2014-10-07.

[29] "Standard Markdown Becomes Common Markdown then CommonMark". InfoQ. Archived from the original on 2020-09-30. Retrieved 2014-10-07.

[commonmark.org-30] "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.

[31] "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.

[IANA-32] "Markdown Variants". IANA. 2016-03-28. Archived from the original on 2020-10-27. Retrieved 2016-07-06.

[gfm_on_github-33] "GitHub Flavored Markdown Spec". GitHub. Archived from the original on 2020-02-03. Retrieved 2020-06-11.

[34] "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.

[35] "SourceForge: Markdown Syntax Guide". SourceForge. Archived from the original on 2019-06-13. Retrieved 2013-05-10.

[36] "Markdown Editing Help". StackOverflow.com. Archived from the original on 2014-03-28. Retrieved 2014-04-11.

[37] "Markdown Syntax Documentation". daringfireball.net. Archived from the original on 2019-09-09. Retrieved 2021-03-01.

[italic-38] "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.

[39] Tom Preston-Werner. "GitHub Flavored Markdown Examples". GitHub. Archived from the original on 2021-05-13. Retrieved 2021-04-02.

[40] "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-2018-41] Fortin, Michel (2018). "PHP Markdown Extra". Michel Fortin website. Archived from the original on 2021-01-17. Retrieved 2018-12-26.

[42] "PHP Markdown Extra". Michel Fortin. Archived from the original on 2021-01-17. Retrieved 2018-12-26.

[43] "Markdown editor for BUEditor". 4 December 2008. Archived from the original on 17 September 2020. Retrieved 15 January 2017.

[44] "Markdown for TYPO3 (markdown_content)". extensions.typo3.org. Archived from the original on 2021-02-01. Retrieved 2019-02-06.

[45] Dietrich, André. "LiaScript". liascript.github.io. Archived from the original on 2022-01-19. Retrieved 2022-01-17.

[46] "W3C Community Page of Markdown Implementations". W3C Markdown Wiki. Archived from the original on 17 September 2020. Retrieved 24 March 2016.

[47] "Markdown THrowdown – What happens when FOSS software gets corporate backing". Ars Technica. 2014-10-05. Archived from the original on 2020-11-14. Retrieved 2017-06-14.

[48] "330707 - Add optional support for MarkDown". bugzilla.mozilla.org. Archived from the original on 2022-10-11. Retrieved 2022-10-11.

[49] "Markdown Text 101 (Chat Formatting: Bold, Italic, Underline)". discord.com. Archived from the original on June 26, 2020.

[50] "Doxygen Manual: Markdown support". Archived from the original on 2019-08-09. Retrieved 2019-08-09.

[51] "Writing on GitHub". help.github.com. GitHub, Inc. Archived from the original on 4 June 2018. Retrieved 9 July 2014.

[52] @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.

[53] "Markdown Guide". joplinapp.org. Archived from the original on 2022-09-23. Retrieved 2022-07-14.

[54] "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.

[55] "Markdown Syntax — Kanboard documentation". docs.kanboard.org. Archived from the original on 2022-10-11. Retrieved 2022-10-11.

[56] "Markdown syntax for files, widgets, wikis - Azure DevOps". 25 March 2024.

[57] "Use Markdown formatting in Teams". Microsoft. Archived from the original on 2022-01-13. Retrieved 2022-01-13.

[58] "Akkoma - Magically Expressive Social Media". akkoma.social. Retrieved 2024-04-18.

[59] "MFM". Misskey Hub. Retrieved 2024-04-18.

[60] "Nextcloud Notes * App". Nextcloud Apps. Archived from the original on 2022-02-18. Retrieved 2022-02-18.

[61] "Obsidian". obsidian.md. Archived from the original on 2022-07-12. Retrieved 2022-07-14.

[62] R Markdown: The Definitive Guide. Archived from the original on 2021-04-13. Retrieved 2021-08-23.

[63] 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.

[64] "Help". Simplenote. 2015-07-30. Archived from the original on 2022-07-14. Retrieved 2022-07-14.

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[11]

[12]

[13]

[14]

[note 1]

[17]

[18]

[19]

[20]

[21]

[22]

[23]

[24]

[25]

[26]

[27]

[28]

[29]

[30]

[31]

[32]

[33]

[34]

[35]

[36]

[37]

[38]

[39]

[40]

[41]

[42]

[43]

[44]

[45]

[46]

[47]

[48]

[49]

[50]

[51]

[52]

[53]

[54]

[55]

[56]

[57]

[58]

[59]

[60]

[61]

[62]

[63]

[15]

[16]

@@ Line 2: / Line 2: @@
 {{For|the marketing term|Price markdown}}
 {{Infobox file format
-| child         =
 | name          = Markdown
 | logo          = Markdown-mark.svg
@@ Line 10: / Line 9: @@
 | screenshot_size =
 | caption       =
-| _noextcode    = on
+| _noextcode    =
-| 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" />
+| 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" />
 | _nomimecode   = on
-| mime          = <code>text/markdown</code><ref name="rfc7763">{{cite web | url=https://datatracker.ietf.org/doc/html/rfc7763 | title=The text/markdown Media Type | publisher=Internet Engineering Task Force | work=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>
+| 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>
 | type code     =
 | uniform type  = <code>net.daringfireball.markdown</code>
 | conforms to   =
 | magic         =
-| owner         = [[John Gruber]]
+| owner         = {{plainlist|
+* [[John Gruber]]
+}}
 | 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>
 | latest release version = 1.0.1
@@ Line 26: / Line 27: @@
 | contained by  =
 | extended from =
-| extended to   = [[pandoc]], [[MultiMarkdown]], [[Markdown Extra]], [[#Standardization|CommonMark]],<ref name="rfc7764">{{cite web | url=https://datatracker.ietf.org/doc/html/rfc7764 | title=Guidance on Markdown: Design Philosophies, Stability Strategies, and Select Registrations | publisher=Internet Engineering Task Force | work=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>
+| 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>
 | standard      =
 | standards     =
@@ Line 33: / Line 34: @@
 }}
-'''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 a [[markup language]] that is appealing to human readers in its source code form.<ref name="philosophy" /> Markdown is widely used in [[blog]]ging, [[instant messaging]], [[online forums]], [[collaborative software]], [[documentation]] pages, and [[README|readme files]].
+'''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, in collaboration with [[Aaron Swartz]],<ref name="Hendler 2022">{{cite book |last1=Hendler |first1=James |authorlink=James Hendler |chapter=Foreword by James Hendler |title=Aaron Swartz's A Programmable Web: An Unfinished Work |series=Synthesis Lectures on Data, Semantics, and Knowledge |date=10 November 2022 |publisher=[[Springer Nature Switzerland]] |pages=ix |chapter-url=https://en.wikisource.org/w/index.php?title=File:Aaron_Swartz_s_A_Programmable_Web_An_Unfinished_Work.pdf&page=11 |url=https://en.wikisource.org/wiki/Index:Aaron_Swartz_s_A_Programmable_Web_An_Unfinished_Work.pdf |doi=10.1007/978-3-031-79444-5 |isbn=978-3-031-79444-5 |access-date=12 January 2024 |language=en |via=[[Wikisource]] |quote=This document was originally produced in "markdown" format, a simplified HTML/Wiki format that Aaron co-designed with John Gruber ca. 2004.}}</ref><ref name="PeerJ 2017">{{cite journal |last1=Krewinkel |first1=Albert |last2=Winkler |first2=Robert |title=Formatting Open Science: agilely creating multiple document formats for academic manuscripts with Pandoc Scholar |journal=[[PeerJ Computer Science]] |pages=6 |language=en |doi=10.7717/peerj-cs.112 |date=8 May 2017 |volume=3 |doi-access=free |s2cid=26747579 |quote=Markdown was originally developed by John Gruber in collaboration with Aaron Swartz, with the goal to simplify the writing of HTML documents}}</ref> as a [[markup language]] that is intended to be easy to read in its source code form.<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]].
-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" />
+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" />
 == History ==
-Markdown was inspired by pre-existing [[Convention (norm)|conventions]] for marking up [[plain text]] in [[email]] and [[usenet]] posts, such as the earlier markup languages [[setext]] ''(c. 1992)'', [[Textile (markup language)|Textile]] ''(c. 2002)'', and [[reStructuredText]] ''(c. 2002)''.<ref name="philosophy" />
+Markdown was inspired by pre-existing [[Convention (norm)|conventions]] for marking up [[plain text]] in [[email]] and [[usenet]] posts, such as the earlier markup languages [[setext]] ({{Circa|1992}}), [[Textile (markup language)|Textile]] (c. 2002), and [[reStructuredText]] (c. 2002).<ref name="philosophy" />
-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 Schwartz acting as beta tester,<ref name="markdown-swartz" /><ref name="gruber-2004-release" /> had 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 |archive-url=https://web.archive.org/web/20040402182332/http://daringfireball.net/projects/markdown/ |archive-date=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 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 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).
@@ Line 47: / Line 48: @@
 == Rise and divergence ==
-As Markdown's popularity grew rapidly, many Markdown implementations appeared, driven mostly by the need for additional features such as tables, footnotes, definition lists,<ref group=note>Technically HTML description lists.</ref> and Markdown inside HTML blocks.
+As Markdown's popularity grew rapidly, many Markdown implementations appeared, driven mostly by the need for additional features such as tables, footnotes, definition lists,<ref group="note">Technically HTML description lists</ref> 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<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.
@@ Line 53: / Line 54: @@
 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 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>
+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>
 == Standardization ==
@@ Line 80: / Line 81: @@
 | standard      =
 | type          = [[Open file format]]
-| url           = {{URL|http://spec.commonmark.org/}}
+| url           = {{URL|https://commonmark.org/}}
+{{URL|http://spec.commonmark.org/}}
 }}
@@ Line 90: / Line 92: @@
 == 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 facilitate discussion between users.
+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> and/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>
+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 ===
 <!-- linked from redirect [[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> adding 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, 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> 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.
+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, 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 ===
@@ Line 110: / Line 112: @@
  | archive-url = https://web.archive.org/web/20210117015819/https://michelf.ca/projects/php-markdown/extra/
  | url-status = live
- }}</ref> It adds the following features not available with plain Markdown syntax:
+ }}</ref> It adds the following features that are not available with regular Markdown:
 * Markdown markup inside [[HTML]] blocks
@@ Line 120: / Line 122: @@
 * 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> 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 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>
 === LiaScript ===
@@ Line 302: / Line 304: @@
 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 that support Markdown as an editing format, including:
+Some apps, services and editors support Markdown as an editing format, including:
-* [[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>
+* [[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>
+* [[ChatGPT]]: Output from the AI model 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 AI 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.
-* [[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>
 * [[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>
-* [[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>
+* [[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" />
-* 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" />
-* [[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>
-* [[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>
-* [[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>
-* [[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>
-* [[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>
 * 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>
-* 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.
+* [[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 has its own implementation<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 }}</ref>
-* [[Discourse (software)|Discourse]] uses the CommonMark flavor of Markdown in the forum post composer.
-* [[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>
+* [[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}}</ref> use a custom text format misleadingly called "Misskey-Flavored Markdown (MFM)", with support for standard nestable block quotes <code>&gt;</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>&lt;small> &lt;center> &lt;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}}</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 ==

v t e Document markup languages
Office suite	Compound Document Format OOXML SpreadsheetML PresentationML WordprocessingML ODF UOF
Well-known	HTML XHTML MathML RTF TeX LaTeX Markdown
Lesser-known	AmigaGuide AsciiDoc BBCode CML C-HTML ConTeXt CrossMark DITA Djot DocBook EAD Enriched text FHTML GML GuideML HDML HyTime IPF LilyPond LinuxDoc Lout MIF MAML MEI MusicXML OMDoc OpenMath Org-mode POD ReStructuredText RTML RFT S1000D Setext TEI Texinfo troff Wikitext WML WapTV XAML
List of document markup languages

Authority control databases
International	FAST
National	Israel United States