Closed garrett closed 5 years ago
Here is a list of all pages that render a <code>
block, with links that point to the Beta site:
Here's the same list, but with the links pointing to a locally running instance:
PR #127 should handle bullet 303 on this list
Did not notice this issue at the time, but PR #96 fixes bullet 113 on this list.
@garrett is there an automated/semi-automated way to apply fixes to code blocks? maybe some search-and-replace?
PR #408 will fix item 83
@thatdocslady: Yes, I did what I could a while back. The conversions didn't do it 100% (especially as a lot of oVirt's code blocks were a bit odd or complex), so it needs manual intervention — hence this issue to track changes.
@rollandf's PR #445 fixes item 212
wont-fix
Many pages use code blocks. This issue addresses the need to review and optimize each code block. Optimized code blocks are indented starting at the flush left, surrounded by three backticks and, optionally, the programming language (which would cause the code block to be syntax highlighted)... instead of just merely being indented.
See http://kramdown.gettalong.org/syntax.html#code-blocks for more information.
Please note that we do not use the fenced code block style as in the Kramdown documentation, but use GitHub-style fenced code blocks (that is, backticks '`' instead of tildes '~').
See https://help.github.com/articles/github-flavored-markdown/#fenced-code-blocks
(Note: We basically use GitHub style Markdown with a bit of Kramdown enhancements on top. This is so we can preview most everything on GitHub directly and still can use classes and such with
{:.classnameone.classnametwo}
type Kramdown extensions.)