Timeline
Timeline.
Dated entries covering Markdown's predecessors, 2004 release, adoption, dialects, and specification work.
-
Setext appears in TidBITS
TidBITS publishes issues in a structure-enhanced plain-text format later known as Setext.
Context: Daring Fireball's Markdown syntax documentation lists Setext as an influence. Markdown also uses the term Setext-style headings for underlined headings.
-
reStructuredText appears in Docutils
reStructuredText develops in the Python documentation ecosystem; Docutils 0.1 is released on 2002-04-20 after earlier reStructuredText and Docstring Processing System work.
Context: Markdown's syntax documentation lists reStructuredText as an influence. It represents a more structured and documentation-oriented branch of lightweight markup.
-
Textile is available for web text formatting
Dean Allen's Textile is documented as a lightweight markup system for formatting web text.
Context: Gruber compares Markdown with Textile in the first public Markdown announcement. Textile was part of the lightweight markup context around Markdown's 2004 release.
-
Aaron Swartz publishes atx
Aaron Swartz's atx page describes a structured text format for plain text.
Context: Markdown later uses the term ATX-style headings for hash-prefixed headings. atx should be treated as related context and naming history, not as Markdown itself.
-
Markdown 1.0b1 appears on the project page
An archived Daring Fireball project-page source lists Markdown 1.0b1, dated 9 March 2004, with download, Dingus, license, and mailing-list links.
Context: This is the earliest dated public Markdown artifact currently registered here. It precedes the 2004-03-15 weblog announcement, while a later Markdown 1.0 post still points to an unresolved February public release.
-
Markdown is announced on Daring Fireball
John Gruber announces Markdown on Daring Fireball's weblog as a text-to-HTML formatting tool for web writers.
Context: The weblog announcement gives a clear public explanation of Markdown after the beta project page was already available.
-
Gruber publishes Dive Into Markdown
Dive Into Markdown explains Markdown's email-style source text and contrasts it with composing weblog posts in raw HTML.
Context: The post documents Markdown's stated design goals: readable source text, HTML output, and compatibility with inline HTML.
-
Swartz publishes a Markdown account
Aaron Swartz describes working with John Gruber for months on Markdown, discussing syntax details, testing the format, and writing the reverse-conversion tool html2text.
Context: The account supports Swartz's collaboration and html2text role while distinguishing those contributions from Gruber's Perl implementation.
-
Boing Boing covers Markdown during launch week
Boing Boing describes Markdown as a project unveiled by Aaron Swartz and John Gruber, linking to Daring Fireball via Aaron Swartz.
Context: The item records early public authorship associations. Role descriptions should still be checked against primary project pages and author accounts.
-
Markdown 1.0b4 and html2text are announced
Gruber announces Markdown 1.0b4 and notes Aaron Swartz's html2text converter from HTML to Markdown-compatible plain text.
Context: The entry distinguishes Markdown.pl from related tooling and records html2text as part of the early Markdown toolset.
-
Markdown 1.0 is released
Gruber announces Markdown 1.0 as out of beta, with syntax, licensing, port, and integration notes.
Context: The post describes Markdown both as a syntax and as Perl software, and records early ports and integrations.
Sources: Daring Fireball: Markdown 1.0 -
Markdown 1.0.1 is released
Markdown 1.0.1 is released with bug fixes, syntax tweaks, and changes around code spans, link definitions, escapes, comments, lists, and other edge cases.
Context: Because Markdown.pl 1.0.1 became the last widely cited original release, its behavior remains important for later implementation comparisons.
-
Markdown adopts a BSD-style license
Starting with Markdown 1.0.1, Markdown changes from the GPL to a less restrictive BSD-style license.
Context: The licensing change reduced restrictions on reuse in open-source and commercial tools.
Sources: Daring Fireball: Markdown Licensing -
PHP Markdown Extra is released
Michel Fortin releases PHP Markdown Extra, an extension of PHP Markdown. Its documentation covers features such as tables, definition lists, footnotes, fenced code blocks, and Markdown inside selected HTML blocks.
Context: Documents an early extension branch that added document features outside original Markdown.pl.
-
MultiMarkdown supports document conversion workflows
Fletcher T. Penney releases Mac OS X drag-and-drop tools that convert MultiMarkdown documents to XHTML, LaTeX, and PDF.
Context: The release is an early dated public marker for MultiMarkdown as a document-oriented Markdown extension with multi-format output.
-
Pandoc is announced
John MacFarlane announces an early Pandoc release, a Haskell Markdown implementation and document converter with output formats including HTML, LaTeX, reStructuredText, RTF, and S5 slides.
Context: Pandoc connects Markdown parsing with document conversion and later provides context for CommonMark through MacFarlane's specification work.
-
Stack Overflow evaluates Markdown editing
While building Stack Overflow, Jeff Atwood evaluates markup and editing options and identifies WMD, a Markdown editor with real-time preview, as a promising fit.
Context: Records Markdown's consideration in Stack Overflow's editor design before public launch.
-
Stack Overflow publicly launches
Stack Overflow publicly launches after its private beta; Markdown-style editing is part of its Q&A workflow.
Context: Places Markdown-style formatting in a developer Q&A workflow.
-
GitHub announces GFM for comments and messages
GitHub announces that comments, messages, and wall posts now use GitHub Flavored Markdown.
Context: Documents GitHub's platform-specific dialect for comments, messages, and wall posts.
-
Atwood reviews Markdown use on Stack Overflow
Atwood reviews Stack Overflow's first year using Markdown and compares some decisions with GitHub Flavored Markdown.
Context: The post documents practical parser and editor concerns on programming platforms, including autolinks and code-oriented behavior.
-
RStudio v0.96 adds R Markdown support
RStudio v0.96 adds support for dynamic web reports in the new R Markdown and R HTML formats through knitr integration. RPubs follows in June for publishing R Markdown documents to the web.
Context: Marks a dated public point when Markdown became an executable analysis-document workflow in the RStudio ecosystem, before the later rmarkdown package history.
-
Atwood calls for a Markdown spec and test suite
Jeff Atwood writes that Markdown's lack of a formal specification and tests has led to fragmentation and proposes that Markdown-using platforms collaborate on a specification.
Context: Documents a public proposal for specification work before the 2014 CommonMark project.
-
Standard Markdown specification effort is announced
Atwood announces a project named Standard Markdown, describing a specification, tests, and reference implementations with John MacFarlane as spec author.
Context: Gives the initial public name and shape of the project later renamed CommonMark.
-
Standard Markdown is renamed
After Gruber objects to the name Standard Markdown, Atwood publishes an apology, renames the project Common Markdown, and then notes that the project is using the name CommonMark.
Context: Documents the name objection and subsequent renaming as standardization history.
-
The text/markdown media type is registered
RFC 7763 registers the text/markdown media type, and RFC 7764 gives guidance on Markdown design philosophies, variants, and registration.
Context: The RFCs register a media type and describe Markdown variants without making Markdown syntax an Internet Standards Track specification.
-
GitHub publishes a formal GFM specification
GitHub announces a formal specification for GitHub Flavored Markdown, based on CommonMark and extended with GitHub-specific features.
Context: Documents a CommonMark-based formal specification for GitHub's Markdown dialect.
-
MDX combines Markdown with JSX components
MDX combines Markdown with JSX, JavaScript expressions, and ESM imports/exports, allowing authors to use components inside Markdown content.
Context: Documents a Markdown-based authoring format used with JavaScript component documentation and sites.
-
Obsidian 0.0.1 public release uses Markdown notes
Obsidian's changelog records 0.0.1 Desktop as a public initial release. The release lists vault selection, compatible files, wiki-style internal links, embeds, and a plugin system; current official docs describe Markdown .md files as Obsidian's primary note format.
Context: Anchors Obsidian's local Markdown-note model in a dated public desktop release.
-
Quarto is announced
Posit announces Quarto, an open-source scientific and technical publishing system built on Pandoc and described as the next generation of R Markdown.
Context: Documents a Pandoc-based publishing system that uses Markdown with computational notebooks and languages including Python, R, Julia, and Observable.
Sources: Posit: Announcing Quarto Quarto homepage -
CommonMark 0.31.2 is published
CommonMark Spec version 0.31.2 is published, continuing the long-running effort to define Markdown-compatible syntax with examples and tests.
Context: Identifies a dated release of the CommonMark specification, including examples and tests for Markdown-compatible parsing.
No timeline events match the current filter.