From: Diego Zamboni <diego@zzamboni.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Luis Roca <roca@pobox.com>, Diego Zamboni <diego@zzamboni.org>,
emacs-orgmode@gnu.org
Subject: Re: Moving from Jekyll to Orgmode
Date: Tue, 1 May 2018 20:41:09 +0200 [thread overview]
Message-ID: <A37660EB-5CE6-4FF1-9030-554717138D29@zzamboni.org> (raw)
In-Reply-To: <CAFyQvY1OinHDWyH-vPMwmqMn7=rc-JXtsWscpGeT_HxhHym5fQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1802 bytes --]
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 <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.
> I also have this little annotated diagram:
> https://discourse-cdn-sjc2.com/standard12/uploads/gohugo/original/2X/8/8dd4af3e103c3a691a71356aa3f91bfe1019ebae.png <https://discourse-cdn-sjc2.com/standard12/uploads/gohugo/original/2X/8/8dd4af3e103c3a691a71356aa3f91bfe1019ebae.png>
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
[-- Attachment #2: Type: text/html, Size: 3010 bytes --]
next prev parent reply other threads:[~2018-05-01 18:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 21:05 Moving from Jekyll to Orgmode ST
2018-04-28 21:40 ` Diego Zamboni
2018-04-28 21:42 ` Diego Zamboni
2018-04-28 22:13 ` Scott Randby
2018-04-29 8:50 ` ST
2018-04-29 9:07 ` Bastien
2018-04-29 9:22 ` ST
2018-04-29 12:58 ` Ista Zahn
2018-04-29 14:45 ` Scott Randby
2018-04-29 7:45 ` Saša Janiška
2018-04-29 12:55 ` Luis Roca
2018-04-30 20:28 ` Diego Zamboni
2018-04-30 22:43 ` Kaushal Modi
2018-05-01 18:41 ` Diego Zamboni [this message]
2018-05-04 6:49 ` Thomas S. Dye
2018-05-04 13:43 ` Kaushal Modi
2018-05-04 13:53 ` Kaushal Modi
2018-05-04 15:07 ` Thomas S. Dye
2018-04-29 16:45 ` Grant Rettke
2018-04-30 10:58 ` ST
2018-05-05 17:51 ` Rasmus
2018-05-07 8:39 ` ST
2018-05-07 22:21 ` Rasmus
2018-05-09 7:35 ` ST
2018-05-09 8:03 ` Thomas S. Dye
2018-05-09 12:37 ` ST
2018-05-09 11:38 ` Diego Zamboni
2018-05-09 12:21 ` Kaushal Modi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A37660EB-5CE6-4FF1-9030-554717138D29@zzamboni.org \
--to=diego@zzamboni.org \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=roca@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).