# CommonMark now in use on GitLab

**URL:** <https://talk.commonmark.org/t/commonmark-now-in-use-on-gitlab/2944>\
**Category:** Application\
**Created:** [September 30, 2018, 6:51pm UTC](https://talk.commonmark.org/t/commonmark-now-in-use-on-gitlab/2944 "2018-09-30T18:51:09Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Crissov](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/crissov/32/1455_2.png) [@Crissov](https://talk.commonmark.org/u/Crissov)\
**Post date:** [October 1, 2018, 7:23am UTC](https://talk.commonmark.org/t/commonmark-now-in-use-on-gitlab/2944/2 "2018-10-01T07:23:03Z")

</div>

Your documentation needs some cleanup, though, because it puts some features under the _Standard Markdown_ heading that are neither in Commonmark nor in Gruberʼs specification, e.g. strike-through and tables.

It is not really helping that your are using the same acronym, “GFM”, to refer to Git_Lab_ Flavored Markdown that everyone else is using for Git_Hub_ Flavored Markdown. You should probably also document the differences between the two, e.g. `$`inline math`$`, fenced block quotes `>>>`, videos `![](foo.mp4)`, diffs `[+ ins +] {- del -}`.

We should really get on publishing extension modules with test cases, so implementations can claim interoperable conformance to them. They often differ in details, e.g. Gitlab apparently requires exactly two tildes `~~` before and after stricken text while Github collapses any matching number of tildes (like ```).

---

_[View the full topic](https://talk.commonmark.org/t/commonmark-now-in-use-on-gitlab/2944)._