I have wanted to include rich formatted text in the callout boxes for some time. I have implemented this on FAIRDOM-SEEK Docs:
https://docs.seek4science.org/help/user-guide/isa-temporary-links

https://github.com/seek4science/seek-documentation/blob/main/_includes/callout-markdownify.html
This include file is based on callout.html but includes a title property and applies the markdownify filter to the content. It still supports the four types of callout.
https://github.com/seek4science/seek-documentation/blob/main/help/user-guide/isa-temporary-links.md
In this example, the content is written in the front-matter, using the multiline |- operator. The callout is used multiple times on the same page, in a loop. But of course it could be used, without the loop.
Is this something that I should add to base ETT in a pull request? If so, what would you want to be changed?
I have wanted to include rich formatted text in the callout boxes for some time. I have implemented this on FAIRDOM-SEEK Docs:
https://docs.seek4science.org/help/user-guide/isa-temporary-links

https://github.com/seek4science/seek-documentation/blob/main/_includes/callout-markdownify.html
This include file is based on
callout.htmlbut includes atitleproperty and applies themarkdownifyfilter to thecontent. It still supports the four types of callout.https://github.com/seek4science/seek-documentation/blob/main/help/user-guide/isa-temporary-links.md
In this example, the content is written in the front-matter, using the multiline
|-operator. The callout is used multiple times on the same page, in a loop. But of course it could be used, without the loop.Is this something that I should add to base ETT in a pull request? If so, what would you want to be changed?