Perhaps you should raise an issue at the main Hugo repo.
However if the project will not need to provide code examples in content files, you can always disable standard syntax code blocks in the template with something like:
{{ replaceRE `\x60(.*?)\x60` `` .Content }}
Whenever backticks are found within a page’s .Content the above regular expression will capture everything between and remove it.
Hugo is an open source static site generator. Static HTML is always safer than dynamic.
So for a project that will have users with no technical skills or users who are not trustworthy I think that Hugo would serve your use case, as long as the project’s backend (config + templates) is not accessible to plain users.
I double-checked the whole repo and this looks like an unexpected behavior: the related branch does not refer to such “feature” with Attributes. (See also the release notes and the discussion #7548)
I guess I should open an issue but my time (and my english!) is a bit narrow these days and this repo is sometime intimidating. Anyone feels like doing this?
Thanks a lot for your advanced knowledge. I would like to understand the reason behind this, but couldn’t find details. How to know precisely which attributes are affected?
I would prefer to stick to basic Markdown for two reasons:
The content is portable with basic Markdown
Shortcode syntax is too difficult for newcomers
That’s no big deal though, and if no simple solution exists I’ll add a component / button in NetlifyCMS and everything will be find
Once again, thank you @alexandros and @jmooring for sharing, it’s good to know you’re around