Update Asciidoc markup example with safe defaults #24920
Merged
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.
The cheat sheet uses the
asciidoc
markup language to demonstrate how to set up third party markup renderers. The current example has the following issues:By switching to
asciidoctor
, uses are suggested to utilize de facto/standard tooling for AsciiDoc.The
--embedded
parameter will strip out HTML tags that contain the document (such as<html></html>
) which aren't necessary for the render, and actually end up as text in the document if left in.The
--safe-mode
parameter (of which there are several profiles) imposes certain policies on the files it ingests and what the resulting output looks like. GitHub itself uses thesecure
profile (the highest), which can be a good starting point for those who are uncertain of what to do. By default, if no mode is specified whenasciidoctor
runs it defaults tounsafe
, i.e. no safety guidelines at all.