For any markup that is not covered by Markdown’s syntax, you simply use HTML itself. There’s no need to preface it or delimit it to indicate that you’re switching from Markdown to HTML; you just use the tags.
For example, to add an HTML table to a Markdown article:
This is a regular paragraph.
<table>
<tr>
<td>Foo</td>
</tr>
</table>
This is another regular paragraph.
You can use a shortcode if you want to wrap markdown in HTML. This has pros and cons; namely, the pro is that it’s cleaner and easier to manage and repurpose, while the con is that the shortcodes are pretty Hugo specific.
Your original issue has very little to do with Hugo, just as an FYI: HTML-wrapped markdown is not rendered as markdown according to the spec.
Of course, you can just write flat HTML inside your markdown files as well, as already mentioned Throwing this out there in hope that it helps…
I looked into the Hugo issues (open and closed) but cannot really see why this is the case. Can someone from the Hugo team comment on this? ‘no longer being updated’ seems the first step to sunsetting this feature.
Just wonder if it still makes sense to convert to mmark. Don’t want to be reconverting my content at a later point.
I don’t use mmark. But for curiosity, is this official? If so, I’d be glad to take if off my checklist (working on an Org to ‘Markdown for Hugo’ exporter package).
I’m not a developer so I’m more guessing (due to no answer yet), but if I look at the vendor file in Hugo’s source code, I see that mmark from May 19 is used. (That’s how interpret it that .json file.)
That would match mmark release 1.3.5, which is one small version (0.0.1) behind the latest mmark release (1.3.6). I guess that Hugo bumps up the mmark version in the next non-bug fix release.
It can also mean that the May 19 comment that ‘Hugo doesn’t update mmark anymore’ is not accurate anymore. (Although it hasn’t been disputed by a developer either.)
Would love to hear some clarification instead of using my own uneducated guesses.