#Framework Initiative

Is GLFM a coding standard or a parser standard?

GitLab Flavored Markdown (GLFM) would be a better choice

Is GLFM fully compatible with Python Markdown (goes back to the mkdocs discussion before)?

I’ve spent more time dealing with markdown since #10. My experience now is that it may be very hard to specify a coding standard and unlikely that we will find own pre-made.

There is a big difference between a coding standard and a parsing standard.

A coding standard dictates how detail must be laid out even though the language supports a diffrent layout, while a parser standard defines how it must be laid out to parse and any deviation will result in an error state:

To put the above in the form of an example:
PHP defines a parsing standard.
drupal/coder defines a coding standard.

Is it within the Coding Standards charter to define the use of a parser standard?

I agree, given that drupal.org issues will move to Gitlab, GitLab Flavored Markdown (GLFM) would be a better choice.

Perhaps we need to create a new issue "Adopt GitLab Flavored Markdown (GLFM) as standard for Markdown files"?

Or can we change the title in this issue, if that's where where the consensus seems to be? Then the discussion and arguments will not be spread over two Markdown issues ...

@balu_ertl: What do you think about that?

I agree that there's not been consensus yet.

I don't think CommonMark allows for having tables, and I think that is an important extension to have. It is in Github and Gitlab flavored markdown, and given our integration with Gitlab, it might be a good idea to go for that?

It is confusing that the current text section shows other issues. Skimming through I don't see that there is consensus on CommonMark. Since I think this needs more discussion I am changing the status to 'active'.