Sources.

Context: Records the structure-enhanced text format used by TidBITS, a pre-Markdown plain-text format later cited in Markdown syntax documentation.

Documented points

• Setext appears before Markdown.
• The format was used for online plain-text publication.
• Markdown syntax documentation later names Setext as an influence and uses the term Setext-style headings.

Context: Documents Textile as a 2002 web text formatting tool.

Documented points

• Textile predates Markdown's 2004 public release.
• Markdown's first public announcement compares Markdown with Textile.

Context: Documents Textile syntax and current project behavior.

Documented points

• Textile remains a documented lightweight markup language.
• Current Textile features overlap with features later found in Markdown dialects.

Context: Provides project history for Docutils and its relationship to reStructuredText.

Documented points

• Docutils 0.1 was released on 2002-04-20.
• reStructuredText and Docutils predate Markdown's public release.

Context: Documents reStructuredText project history.

Documented points

• reStructuredText predates Markdown.
• The documented design is more structured and documentation-oriented than original Markdown.

Context: Public announcement for Markdown.

Documented points

• The announcement date is 2004-03-15.
• Markdown is described as a text-to-HTML formatting tool for web writers.
• The announcement lists Movable Type, Blosxom, and standalone Perl distribution forms.

Context: Early archived source for the Markdown project page, including the Markdown 1.0b1 download date.

Documented points

• The archived page lists Markdown 1.0b1 as a download dated 2004-03-09.
• The page describes Markdown as both syntax and a Perl software tool.
• The page links the project page to syntax, license, Dingus, and discussion-list material.
• The snapshot predates the 2004-03-15 Daring Fireball weblog announcement.

Context: Documents Gruber's explanation of Markdown's source-text and HTML-output model.

Documented points

• Markdown source text was designed to be readable as plain text.
• Markdown output was framed around HTML.
• Markdown was presented as complementary to HTML rather than as a replacement for it.

Context: Project page with download, overview, installation notes, license note, and acknowledgements.

Documented points

• Markdown is presented as both syntax and Perl software.
• Markdown's design goal emphasized readability.
• The page credits Aaron Swartz for ideas, feedback, testing, and html2text.
• The download page lists Markdown 1.0.1 by 2004-12-17.

Context: Original syntax documentation for Markdown.

Documented points

• The syntax page states readability as a design goal.
• The syntax page lists plain-text email and earlier text-to-HTML filters as influences.
• The syntax page documents Setext-style and ATX-style headings.
• The syntax page states that Markdown is not a replacement for HTML.

Context: Follow-up post mentioning Markdown 1.0b4 and html2text.

Documented points

• Markdown 1.0b4 was announced in the post.
• html2text was described as converting HTML to Markdown-formatted plain text.

Context: Release post for Markdown 1.0.

Documented points

• Markdown 1.0 was released in August 2004.
• The post says there had been a first public release back in February.
• The post records syntax and licensing changes.
• Code block rules were revised before 1.0.
• The post distinguishes Markdown as syntax and Perl software.

Context: Release post for Markdown 1.0.1.

Documented points

• Markdown 1.0.1 was released on 2004-12-17.
• Markdown 1.0.1 focused on bugs, ambiguities, and confusing edge cases.

Context: Licensing post for Markdown's switch from GPL to BSD-style terms.

Documented points

• Markdown licensing changed in 2004.
• The post links the license change to Markdown 1.0.1.

Context: Archive of the original Perl implementation.

Secondary URL or mirror

Documented points

• Markdown.pl was written in Perl.
• Implementation behavior is available as source code.
• The source code is separate from the prose syntax documentation.

Context: Contemporary account by Swartz of his work with Gruber on Markdown and html2text.

Secondary URL or mirror

Documented points

• Swartz describes months of work with Gruber.
• Swartz describes syntax discussion and testing.
• Swartz identifies html2text as his reverse-conversion tool.
• Swartz distinguishes Gruber's Perl implementation from the format.

Context: Swartz's earlier structured text format page.

Secondary URL or mirror

Documented points

• atx predates Markdown's public release.
• Markdown syntax documentation later uses ATX-style headings for hash-prefixed headings.

Context: Archived 2003 discussion containing atx context.

Documented points

• atx was discussed before Markdown's 2004 public release.
• The discussion appears in a W3C public archive.

Context: Swartz's HTML-to-text tool cited from Daring Fireball's Markdown page.

Documented points

• html2text is credited on Daring Fireball's Markdown project page.
• The tool is related to HTML-to-Markdown/plain-text conversion.

Context: Contemporary third-party coverage from 2004-03-19.

Documented points

• The article describes Markdown as unveiled by Aaron Swartz and John Gruber.
• The article links to Daring Fireball and Swartz context.
• It records reception language rather than project-maintainer role definitions.

Context: Documents Stack Overflow's Markdown editing workflow before public launch.

Documented points

• Markdown was selected as part of Stack Overflow's early editing experience.
• Real-time preview mattered to Stack Overflow's Markdown adoption.

Context: Documents Stack Overflow's early Markdown experience while the site was being built.

Documented points

• Stack Overflow was using the WMD Markdown control during development.
• Programming-oriented Markdown use exposed edge cases and practical needs.

Context: Gives Stack Overflow's launch date and early growth context.

Documented points

• Stack Overflow officially launched on 2008-09-15.
• The retrospective provides context for Stack Overflow as a Markdown-using developer platform.

Context: Reflects on Markdown after a year of Stack Overflow use and compares Stack Overflow's choices with GitHub Flavored Markdown.

Documented points

• Stack Overflow and GitHub both adjusted Markdown for programming audiences.
• The post records practical Markdown parser and editor issues on a programming platform.

Context: Current Stack Overflow Markdown help and CommonMark references.

Documented points

• Stack Overflow uses a Markdown-derived formatting system.
• Stack Overflow has platform-specific additions and restrictions.

Context: 2012 public post calling for a Markdown specification and test suite.

Documented points

• Atwood describes fragmentation and the lack of formal tests as problems.
• The post proposes a formal spec and test suite based on existing Markdown conventions.
• The post says Atwood sought Gruber's blessing for the effort.

Context: 2014 announcement of the project initially named Standard Markdown.

Documented points

• The project is described as a specification with implementations and tests.
• John MacFarlane is listed as the spec author.
• The announcement describes ambiguity in existing Markdown behavior as a target for specification work.

Context: Atwood post recording the name change from Standard Markdown to Common Markdown, and then CommonMark.

Documented points

• Gruber objected to the name Standard Markdown.
• Atwood apologized publicly.
• The project was renamed Common Markdown, then CommonMark.
• The post links the objection to the implication of standard status.

Context: Current public entry point for CommonMark.

Documented points

• CommonMark describes itself as a strongly defined, compatible specification of Markdown.
• CommonMark identifies John MacFarlane, Martin Woodward, and Jeff Atwood among current project contacts.
• CommonMark lists original 2014 participants.
• CommonMark describes Markdown as developed by John Gruber in collaboration with Aaron Swartz.

Context: Specification text for Markdown-compatible syntax.

Documented points

• Markdown was developed by John Gruber with help from Aaron Swartz and released in 2004 as a syntax description and Perl script.
• Original Markdown documentation left many parsing questions ambiguous.
• Dozens of implementations and extensions emerged after 2004.
• CommonMark attempts to specify Markdown syntax unambiguously.

Context: Repository for CommonMark specification source and tests.

Documented points

• The repository contains the specification source.
• The repository contains tests and reference implementation material.
• Development history is publicly available through the repository.

Context: Early public marker for GitHub Flavored Markdown across GitHub user content.

Documented points

• GitHub moved messages and comments to GitHub Flavored Markdown in April 2009.
• The post records GitHub's public use of the GFM name.

Context: Announces formalization of GitHub Flavored Markdown based on CommonMark.

Documented points

• GitHub formalized GFM by extending CommonMark.
• GitHub-specific features include tables, task lists, strikethrough, and autolinks.

Context: Canonical spec for GitHub Flavored Markdown.

Documented points

• GFM is the dialect supported for user content on GitHub.com and GitHub Enterprise.
• GFM is based on CommonMark.
• GFM describes itself as a strict superset of CommonMark.
• GFM defines extensions including tables, task list items, strikethrough, autolinks, and disallowed raw HTML.

Context: Current GitHub user documentation for writing with Markdown.

Documented points

• GitHub combines GFM with platform-specific writing features.
• GitHub uses Markdown in issues, pull requests, comments, and other user content.

Context: Documentation for an early PHP Markdown extension with additional document features.

Secondary URL or mirror

Documented points

• Markdown Extra added syntax beyond original Markdown.
• The documentation covers tables, footnotes, definition lists, and related extensions.

Context: Early dated public source for MultiMarkdown document-conversion workflows.

Secondary URL or mirror

Documented points

• Penney released Mac OS X drag-and-drop applications for MultiMarkdown on 2005-11-20.
• The tools converted MultiMarkdown documents to XHTML, LaTeX, and PDF.
• The page describes MultiMarkdown as an extension to Markdown.
• The page documents an initial public release for the drag-and-drop package, not necessarily the first release of MultiMarkdown itself.

Context: Documentation for a Markdown extension aimed at complete documents and multi-format output.

Secondary URL or mirror

Documented points

• MultiMarkdown was designed for complete documents, not only web fragments.
• MultiMarkdown supports features such as metadata, tables, footnotes, citations, cross-references, math, and multiple output formats.
• Current documentation describes MultiMarkdown as having started as a Perl script modified from Markdown.pl.
• MultiMarkdown version 2 began as a modification of Markdown.pl.

Context: Manual for Pandoc's Markdown reader and document conversion workflow.

Documented points

• Pandoc supports an extended Markdown and multiple Markdown variants.
• Pandoc converts Markdown to multiple output formats.
• MacFarlane's parser work also appears in later CommonMark specification history.

Context: Provides an early public announcement of Pandoc as a Markdown implementation and document converter.

Documented points

• Pandoc was publicly discussed in the Markdown community by 2006.
• Pandoc connected Markdown to multiple output formats early in its history.

Context: Documents Pandoc's explicit treatment of Markdown as a family of variants.

Documented points

• Pandoc supports multiple Markdown variants.
• Markdown behavior can be selected and modified through extensions.

Context: Documentation for R Markdown as a format for executable reports, notebooks, and statistical publishing.

Documented points

• R Markdown combines prose, code, and output.
• R Markdown uses Markdown in reproducible research and data analysis workflows.

Context: Current R Markdown project site describing documents that combine prose, code, and output.

Documented points

• R Markdown connects Markdown authoring with executable code.
• The site presents R Markdown as a document workflow for reports, presentations, dashboards, and notebooks.

Context: Documentation for a Markdown-based format that supports JSX components and JavaScript expressions.

Documented points

• MDX combines Markdown with JSX, JavaScript expressions, and ESM imports/exports.
• MDX is used in component-based front-end documentation and sites.

Context: Announcement for MDX reaching a stable 1.0 release after earlier use in component-driven documentation.

Documented points

• MDX reached a stable 1.0 release in 2019.
• The announcement describes use of MDX for component-rich content.

Context: Documents the compiler package for MDX's Markdown-plus-JSX workflow.

Documented points

• MDX is implemented through tooling that compiles Markdown and JSX together.
• MDX adapts Markdown for JavaScript and component publishing workflows.

Context: Current project positioning for MDX as Markdown with JSX components.

Documented points

• MDX is used to embed components in Markdown content.
• MDX positions Markdown inside JavaScript and JSX-based publishing workflows.

Context: Official dated release note for Obsidian's public initial desktop release.

Documented points

• Obsidian 0.0.1 Desktop is dated 2020-03-30.
• The changelog marks the release as public and initial.
• Notable features included vault selection, compatible files, internal links with autocomplete, embeds, and a plugin system.

Context: Current official documentation for Markdown files as Obsidian's primary note format.

Documented points

• Obsidian uses Markdown .md files as the primary format for notes.
• Markdown files can be imported into an Obsidian vault.
• Obsidian uses Obsidian Flavored Markdown.

Context: Current Obsidian documentation for Markdown-based note files.

Documented points

• Obsidian uses Markdown files as primary notes.
• Obsidian supports common Markdown features and app-specific extensions.

Context: Example of a contemporary application-specific Markdown dialect.

Documented points

• Obsidian uses a combination of Markdown flavors.
• Modern Markdown use often includes app-specific syntax and behavior.

Context: Official release announcement for RStudio v0.96 and its R Markdown support.

Documented points

• RStudio v0.96 was announced on 2012-05-14.
• The announcement describes tight integration with knitr.
• The announcement says v0.96 supports dynamic web reports with the new R Markdown and R HTML formats.
• The feature list includes editing and previewing R Markdown and R HTML files.

Context: Early public source connecting RStudio, RPubs, and R Markdown publishing.

Documented points

• RPubs was announced on 2012-06-04.
• The post describes RPubs documents as based on R Markdown.
• The post calls R Markdown a new feature of knitr 0.5 and RStudio 0.96.
• The post connects Markdown with reproducible analysis and code-plus-prose documents.

Context: CRAN archive evidence for early knitr versions around RStudio's R Markdown support.

Documented points

• The archive lists knitr 0.5 with a 2012-04-29 timestamp.
• RStudio v0.96 documentation requires knitr 0.5 or higher for related authoring features.
• The archive helps separate knitr package timing from RStudio and RPubs product announcements.

Context: Package-history source for distinguishing the later rmarkdown package from the 2012 R Markdown workflow.

Documented points

• The CRAN archive records rmarkdown source packages from 2014 onward.
• This package history should not be backdated to the 2012 RStudio and RPubs workflow.
• The archive helps distinguish R Markdown as an early workflow from rmarkdown as a later package.

Context: Announcement for Quarto as a scientific and technical publishing system built on Pandoc.

Documented points

• Quarto builds on lessons from R Markdown.
• Quarto is based on Pandoc and supports multi-language computational publishing.

Context: Current positioning for Quarto as a Markdown-based scientific and technical publishing system.

Documented points

• Quarto authors content using plain text Markdown or Jupyter notebooks.
• Quarto supports Python, R, Julia, Observable, and multiple output formats.

Context: Registers the text/markdown media type and formalizes the idea of Markdown variants.

Documented points

• text/markdown is registered as a media type.
• The RFC is informational, not an Internet Standards Track specification.
• Markdown is treated as a family of plain-text formatting syntaxes.
• The variant parameter identifies intended Markdown variants.

Context: Provides design philosophy, stability strategies, and variant registrations.

Documented points

• Markdown variants require careful identification.
• Markdown's ambiguity and diversity were significant enough to merit formal guidance.
• Standard, Common, and Markdown variant identifiers were reserved because of controversy.

Context: Current Stack Overflow formatting documentation.

Documented points

• Stack Overflow uses Markdown and a subset of HTML for posts.
• Stack Overflow documents Markdown for code-heavy Q&A communication.

Context: Current Reddit formatting documentation.

Documented points

• Reddit has used Markdown-like formatting for posts and comments.
• Platform Markdown may be mediated by rich text editors and platform-specific behavior.

Context: 2014 reporting on the CommonMark naming episode and community reaction.

Documented points

• The article reports public reaction to the Standard Markdown/CommonMark naming episode.
• The article discusses open-source stewardship and naming.
• The article is a secondary account.

Context: Third-party index of Obsidian release entries.

Documented points

• The index lists Obsidian release information.
• The index can help locate candidate public beta and release milestones.
• The index is not an official Obsidian source.

Context: Secondary overview with references to Markdown history and variants.

Documented points

• The page links to sources about Markdown history.
• The page summarizes authorship and dialect history as a secondary source.