@@ -47,11 +47,29 @@ are properly written and use the original capitalization. For example, write
4747[ ` .textlintrc.yml ` ] ( https://github.com/open-telemetry/opentelemetry.io/blob/main/.textlintrc.yml )
4848file.
4949
50- ## Markdown standards
50+ ## Markdown
51+
52+ Site pages are written in the Markdown syntax supported by the [ Goldmark]
53+ Markdown renderer. For the full list of supported Markdown extensions, see
54+ [ Goldmark] .
55+
56+ You can also use the following extensions:
57+
58+ - [ GitHub-flavored Markdown] [ GFM ] (GFM) [ alerts] [ gfm-alerts ]
59+ - [ Emojis] . For the complete list of available emojis, see [ Emojis] from the
60+ Hugo docs.
61+
62+ [ Emojis ] : https://gohugo.io/quick-reference/emojis/
63+ [ gfm-alerts] :
64+ https://docs.github.com/en/contributing/style-guide-and-content-model/style-guide#alerts
65+ [ GFM ] : https://github.github.com/gfm/
66+ [ Goldmark ] : https://gohugo.io/configuration/markup/#goldmark
67+
68+ ### Markdown checks {#markdown-standards}
5169
5270To enforce standards and consistency for Markdown files, all files should follow
5371certain rules, enforced by [ markdownlint] . For a full list, check the
54- [ .markdownlint.yaml] file .
72+ [ .markdownlint.yaml] and [ .markdownlint-cli2.yaml ] files .
5573
5674We also enforce Markdown [ file format] ( #file-format ) and strip files of trailing
5775whitespace. This precludes the [ line break syntax] of 2+ spaces; use ` <br> `
@@ -107,6 +125,8 @@ To learn how to fix validation issues, see [Pull request checks](../pr-checks).
107125
108126[.markdownlint.yaml] :
109127 https://github.com/open-telemetry/opentelemetry.io/blob/main/.markdownlint.yaml
128+ [.markdownlint-cli2.yaml] :
129+ https://github.com/open-telemetry/opentelemetry.io/blob/main/.markdownlint-cli2.yaml
110130[line break syntax] : https://www.markdownguide.org/basic-syntax/#line-breaks
111131[markdownlint] : https://github.com/DavidAnson/markdownlint
112132[Prettier] : https://prettier.io
0 commit comments