Enabling Github Flavored Markdown for Terms and Privacy Policy #645
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This enabled the GithibFlavoredMarkdownExtention for CommonMark. This includes: - Autolinks - Disallowed Raw HTML - Strikethrough - Tables - Task Lists
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This enables the GithubFlavoredMarkdownExtention for CommonMark. GFM is included in CommonMark and only has to be enabled to allow a list of markdown features:
Reasoning for enabling this by default
I feel like especially the Tables functionality is something that can benefit many users attempting to set up terms through Jetstream. These documents often include tables, and enabling this extension allows for printing them on the terms pages.