From mboxrd@z Thu Jan 1 00:00:00 1970 From: Diego Zamboni Subject: Re: Moving from Jekyll to Orgmode Date: Tue, 1 May 2018 20:41:09 +0200 Message-ID: References: <1524949519.21032.171.camel@gmail.com> <874ljump59.fsf@atmarama.com> <02CE4F97-08E0-4A50-9CE5-68D0D7712ACD@zzamboni.org> Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Content-Type: multipart/alternative; boundary="Apple-Mail=_E8FABDC4-D0A4-401C-9593-0C2C86AA1049" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39134) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fDaDF-0001IO-3R for emacs-orgmode@gnu.org; Tue, 01 May 2018 14:41:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fDaDB-0002N3-Tb for emacs-orgmode@gnu.org; Tue, 01 May 2018 14:41:17 -0400 Received: from mail-wm0-x236.google.com ([2a00:1450:400c:c09::236]:40734) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fDaDB-0002KP-GP for emacs-orgmode@gnu.org; Tue, 01 May 2018 14:41:13 -0400 Received: by mail-wm0-x236.google.com with SMTP id j5so20371680wme.5 for ; Tue, 01 May 2018 11:41:13 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Kaushal Modi Cc: Luis Roca , Diego Zamboni , emacs-orgmode@gnu.org --Apple-Mail=_E8FABDC4-D0A4-401C-9593-0C2C86AA1049 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 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. > I also have this little annotated diagram: > = https://discourse-cdn-sjc2.com/standard12/uploads/gohugo/original/2X/8/8dd= 4af3e103c3a691a71356aa3f91bfe1019ebae.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: >=20 > {{ $.Scratch.Set "__repo_updated_time" (index (index (index (index = $repo_json "commit") "commit") "committer") "date") }}=20 Indeed, Hugo is incredibly powerful. I=E2=80=99m still far from an = expert on it, although I=E2=80=99ve started dabbling into = modifying/creating my own templates. Hugo has quite a bit of a learning = curve, so it=E2=80=99s not for everyone, but if you are willing to spend = some time learning it, it=E2=80=99s really worth the effort. Cheers, =E2=80=94Diego --Apple-Mail=_E8FABDC4-D0A4-401C-9593-0C2C86AA1049 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 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.

I = also have this little annotated diagram:
https://discourse-cdn-sjc2.com/standard12/uploads/gohugo/origin= al/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=E2=80=99m still = far from an expert on it, although I=E2=80=99ve started dabbling into = modifying/creating my own templates. Hugo has quite a bit of a learning = curve, so it=E2=80=99s not for everyone, but if you are willing to spend = some time learning it, it=E2=80=99s really worth the = effort.

Cheers,
=E2=80=94Diego
= --Apple-Mail=_E8FABDC4-D0A4-401C-9593-0C2C86AA1049--