I’m not too keen on the Inline Shortcode feature. I understand the need but I prefer to keep my content clean.

I implemented that feature just to get the Bootstrap people committed to going with Hugo. They have plenty of ad-hoc inline Liquid code that would not be practical to replace with regular shortcodes. I guess other will also find this useful, but it’s not for everyone.

If I’m understanding correctly, the inline shortcode is similar to the way Jekyll allows you to use Liquid tags within Markdown correct? If so, this is a major boost to people switching over. I much prefer Hugo but that one was Jekyll feature I sorely missed.

i’m very noob and was used to Jekyll where Liquid was everywhere…
but can’t use enableInlineShortcodes to print a simple {{.Page.Title}} in the markdown

i can use the useful {{% param myparam %}} but could i create dump shortcode that executes my custom template code in a page?

as i raise the topic: i have several pages that aren’t exacly “content”, but data elaboration… i don’t want to write a template for each of them, so if there was even just a frontmatter “enableTemplateParsing = true” for this page…

I always figured there are only two approaches to shortcodes: 1) you use shortcodes and create (very small) Hugo product lock-in or 2) You don’t use shortcodes at all and keep your content purely “clean” and tech agnostic. If you’re already going with #1, I think it’s great to add more features like the inline templating. I mean, why not?

As a side note, I’ve been playing with VuePress and other sorta extend-md-with-templating in the JS community, and ad hoc templating inside content can come in really handy for things like documentation. It makes sense for Hugo—as a major player in the static ecosystem—to offer a similar feature, IMHO. Thanks for all the hard work and continually impressive project, @bep and community! Looking forward to playing with these new features as soon as I have time

Since this is a release/announcement thread, you might get better feedback by opening up a new issue, FYI. Just thinking the community might not notice your support question where it’s currentlh written. Welcome to Hugo!

Sorry for the major delay. The Debian packaging of Hugo, has finally caught up. It had been paused since Hugo 0.48, awaiting for golang-1.11 to become available in Debian until 2018-11-20, but only until earlier this week that I had noticed… (my apologies)