| Hi Kaushal,
First of all, thanks for your kind words, and most of all for all your work on ox-hugo! So I don't recommend embedding Hugo shortcodes directly in Org files (even if they work.. not guaranteeing that such embedded Hugo shortcodes will always work). But shortcodes are still supported, though in a different style, leveraging the Org special blocks. That feature is yet undocumented. But it is fully implemented, tested (and used by me). See https://github.com/kaushalmodi/ox-hugo/issues/126 for more info.
Agree - the ideal would be to use regular org constructs for everything, but provide enough information to translate it into the appropriate shortcodes when appropriate.
Very useful! I had seen the table but the diagram (although it takes a bit to understand) make it all very visual.
Apart of the binary-static-ness of the hugo static site generator, another reason it appealed to me is that the Go templating syntax feels a bit /lispy/. For example, I use this:
{{ $.Scratch.Set "__repo_updated_time" (index (index (index (index $repo_json "commit") "commit") "committer") "date") }}
Indeed, Hugo is incredibly powerful. I’m still far from an expert on it, although I’ve started dabbling into modifying/creating my own templates. Hugo has quite a bit of a learning curve, so it’s not for everyone, but if you are willing to spend some time learning it, it’s really worth the effort.
Cheers, —Diego
|
