Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide a markdown styleguide #56

Closed
gwarf opened this issue Aug 4, 2020 · 2 comments · Fixed by #73
Closed

Provide a markdown styleguide #56

gwarf opened this issue Aug 4, 2020 · 2 comments · Fixed by #73
Assignees
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@gwarf
Copy link
Member

gwarf commented Aug 4, 2020

In order to have a clear markdown styleguide that we can enforce using automated tools.

Hugo is using goldmark to parse and render markdown.
It's compliant with CommonMark.
GitHub Flavored Markdown is based on CommonMark.

So we need:

  • a style guide compliant with CommonMark
  • a linter able to enforce this when testing
  • ideally an auto formatter that can be used with VIM and IDE

Some style guides and documentation about markdown:

Some linters:

@gwarf gwarf added enhancement New feature or request help wanted Extra attention is needed labels Aug 4, 2020
@andrea-manzi
Copy link
Contributor

too many options:-)
this one looks quite similar to what we have now https://github.com/carwin/markdown-styleguide, ( that you try to enforce manually:-)) , and if we can keep using the linter we have now in travis would be better

@gwarf
Copy link
Member Author

gwarf commented Aug 4, 2020

Yes this one is nice as it's quite short and simple, but I would like to be sure that we have a style guide covering the Markdown flavour/derivative that we are using and that Hugo is using.
For the linter we need to be sure that it will be able to enforce our style guide, maybe mdl/markdownlint will be able, maybe not...
I've also tried to edit/simplify a bit the first post.

@gwarf gwarf linked a pull request Oct 6, 2020 that will close this issue
@gwarf gwarf closed this as completed in #73 Oct 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants