# Standard Markdown is now Common Markdown

**URL:** <https://talk.commonmark.org/t/standard-markdown-is-now-common-markdown/404>\
**Category:** Uncategorized\
**Created:** [September 5, 2014, 6:34am UTC](https://talk.commonmark.org/t/standard-markdown-is-now-common-markdown/404 "2014-09-05T06:34:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![stuartpb](https://talk.commonmark.org/user_avatar/talk.commonmark.org/stuartpb/32/155_2.png) [@stuartpb](https://talk.commonmark.org/u/stuartpb)\
**Post date:** [September 5, 2014, 6:34am UTC](https://talk.commonmark.org/t/standard-markdown-is-now-common-markdown/404/1 "2014-09-05T06:34:50Z")

</div>

In case anybody is just reading the forum and not keeping up with outside news:

> **[Standard Markdown is now Common Markdown](https://blog.codinghorror.com/standard-markdown-is-now-common-markdown/)**
>
> Let me open with an apology to John Gruber for my previous blog post.
> 
> We’ve been working on the Standard Markdown project for about two years now. We invited John Gruber, the original creator of Markdown, to join the project via email in November...

---

<div class="post-metadata">

**Author:** ![mofosyne](https://talk.commonmark.org/user_avatar/talk.commonmark.org/mofosyne/32/1438_2.png) [@mofosyne](https://talk.commonmark.org/u/mofosyne)\
**Post date:** [September 5, 2014, 7:04am UTC](https://talk.commonmark.org/t/standard-markdown-is-now-common-markdown/404/2 "2014-09-05T07:04:32Z")

</div>

Man, I hope Gruber is fine with this… else, “strict Markdown” is not too bad.

---

<div class="post-metadata">

**Author:** ![ComplexPoint](https://talk.commonmark.org/letter_avatar_proxy/v2/letter/c/5f9b8f/32.png) [@ComplexPoint](https://talk.commonmark.org/u/ComplexPoint)\
**Post date:** [September 5, 2014, 8:05am UTC](https://talk.commonmark.org/t/standard-markdown-is-now-common-markdown/404/3 "2014-09-05T08:05:33Z")

</div>

What did it take to make the ‘Common’ stick in ‘Common Lisp’ ?

The skills, resources and kudos of the American National Standards Institute …

Perhaps pulling down the Jolly Roger and hoisting an adjusted flag will prove enough to reassure, but the critical thing will not be the flag or the spec, but the building of confidence and consensus.

That is not a technical task – it takes human skills – and this ship may need a change of of owners and captain if others are not to flee or attack at the sight of it.

---

<div class="post-metadata">

**Author:** ![ComplexPoint](https://talk.commonmark.org/letter_avatar_proxy/v2/letter/c/5f9b8f/32.png) [@ComplexPoint](https://talk.commonmark.org/u/ComplexPoint)\
**Post date:** [September 5, 2014, 8:33am UTC](https://talk.commonmark.org/t/standard-markdown-is-now-common-markdown/404/4 "2014-09-05T08:33:16Z")

</div>

I fear [Dr Drang may be right](http://www.leancrew.com/all-this/2014/09/yamf/) – the nature, composition, and balance of forces within this process may not be able to produce much more than [YAMF](http://www.leancrew.com/all-this/2014/09/yamf/) Yet Another Markdown Flavor.

( The handling of fenced code-blocks does seem expressive )

> **[YAMF](http://www.leancrew.com/all-this/2014/09/yamf/)**
>
> Another great post

---

<div class="post-metadata">

**Author:** ![codinghorror](https://talk.commonmark.org/user_avatar/talk.commonmark.org/codinghorror/32/2_2.png) [@codinghorror](https://talk.commonmark.org/u/codinghorror)\
**Post date:** [September 5, 2014, 11:17pm UTC](https://talk.commonmark.org/t/standard-markdown-is-now-common-markdown/404/5 "2014-09-05T23:17:08Z")

</div>

Per:

> [@Standard Markdown is now CommonMark](http://talk.commonmark.org/t/standard-markdown-is-now-commonmark/434):
>
> The Standard Markdown project, [in accordance with the wishes of John Gruber](http://blog.codinghorror.com/standard-markdown-is-now-common-markdown/), has been renamed to CommonMark. Please be patient as we complete the rename, this will take a few days, but the core domains are updated: [http://standardmarkdown.com](http://standardmarkdown.com) All old discussions about name will now be closed as resolved.

This topic is now closed. New replies are no longer allowed.
