When I use them like this, in conjunction with the Columns plugin:
Some random text.
It results in a page rendered in an unpredictable way, depending on how snippet.php is structured – if it’s simple enough, everything is parsed correctly (i.e. a button or a label), if anything complex is used (like in this example) the plugin stops producing the correct markup.
Just as an example, here is the output of this test.
I’m using a clean installation of Kirby using exactly the example that I provided, and it doesn’t work.
If you take a closer look at the ugly p and br tags, they are not just being added, they are outside the column container, which has been in fact broken by the parsing.
I’m just wondering whether a change of order in the way tags and markdown is applied would change things. I don’t know the Kirbytext parser enough to be sure, and I’m not a programmer either, but I got the impression that making the Markdown pass first and then parsing the Kirbytags would fix the issue.
But I’m not sure this is worth the attention of you guys, although it seems to be a problem of any plugin that injects HTML into a Markdown Extra enabled panel.
Yes, I think so. But then changing the order of things, might break other stuff. I don’t know. You might want to check if there is an issue on GitHub, and if not, create one. But this won’t help you right now.
Depending what you need more, Markdown Extra or snippets within columns, you may want to consider alternatives:
As for footnotes, an alternative could be to use the @distantnativesfootnotes plugin.
For headline classes, I’m not so sure, maybe use kirbytags?
I can achieve the widget inside columns functionality by using a dedicated template.
Kirbytags for the headline classes is something I considered, but I like the unobtrusive Markdown Extra syntax more. Using templates for my exceptional use case with the columns seems to be less hacky and the right thing to do this time.