@jgm Can we get a separate repository under https://github.com/commonmark/ that shall contain
- a spec to define these terms and
- specs for actual extensions (and modules and flavors) with embedded test cases like the main spec?
Chronological overview of existing meta threads
-
Add "plugin" syntax to the spec (2014 Sep/Oct)
wants generic processing instructions added to the base spec -
Guide for syntax extensions (2014 Sep)
same gist as this thread in the initial post that was quickly kidnapped in the responses -
Including Markdown Flavours Features (2014 Sep)
single supportive post -
Optional syntax (2014 Sep)
about graceful fallback, coordinated extensions etc. -
Multiple levels of CommonMark specification? (2014 Sep through 2016 May)
proposes overly complex spec levels -
Extension distributions (2014 Oct)
introduces distribution for what I called module above: a sensible collection of related and compatible extensions, single post -
Overview of existing MD extensions (common solutions, incompatibilities, …) (2015 Jun/Jul)
resulted in wiki entries for Proposed Extensions, existing Flavors and Deployed Extensions -
Flexibility and modularity for the win! and also extensions’ ecosystem (2015 Jun)
AST transforms etc. -
Sorely confused about "Extensions" (2015 Sep through 2016 Mar)
brief talk about extension (syntax), module (syntax), addon (implementation) -
Can I Use __ ? Markdown Version (w/ CommonMark) (2016 Mar)
announcement for an off-site documentation project -
Hooks for extensions (2016 Nov)
about extending the reference implementations in particular -
Extension spec as part of the Commonmark spec (2017 May)
same gist as this thread, single post -
A convention for flavor declaration (2017 Oct)
wants unobtrusive “namespacing”