Stream: IG creation
Topic: markdown rendering
Jens Villadsen (Feb 14 2019 at 10:20):
gives
is there a bug in the markdown rendering in the igPub or is it the encoding from forge?
The element in the structuredef looks like this:


[I'm an inline-style link with title](https://www.google.com "Google's Homepage")


[I'm an inline-style link with title](https://www.google.com) 
"
@Lloyd McKenzie @Michel Rutten
Lloyd McKenzie (Feb 14 2019 at 15:00):
Adding @Eric Haas as our resident markdown expert
Eric Haas (Feb 14 2019 at 19:26):
I'm not sure what you are referring to re markdown styling. Note that there are some place where the markdown is not rendered, including in the the resource narrative and some artifacts generated by the build process. Such when using the prepackaged lists {% include list-profiles.xhtml %}
The content inside of block-level elements is ignored by the parser.
To solve this look at the Kramdown documentation about mixing html and markdown. You can use this..
'markdown="1"' inside of xhtml elements or add '{::options parse_block_html="true" /}' to the page. but be forewarned the output is not allays what you want. for example the end tags show up if they are not on a separate line and there is a return after the list bullets.
Jens Villadsen (Feb 18 2019 at 08:42):
The markdown examples I looked at was https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#links
Eric Haas (Feb 18 2019 at 17:25):
The default for Jekyll is Kramdown
Last updated: Apr 12 2022 at 19:14 UTC
