From: Diego Zamboni <diego@zzamboni.org>
To: ST <smntov@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>, Rasmus <rasmus@gmx.us>
Subject: Re: Moving from Jekyll to Orgmode
Date: Wed, 9 May 2018 13:38:37 +0200 [thread overview]
Message-ID: <CAGY83EchNTJcRWkUKiUktKF6M2CSzqfsvMBmfeMnXmKBD63gzA@mail.gmail.com> (raw)
In-Reply-To: <1525851324.2021.59.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
>
>
> Is the difficulty to setup ox-publish the sole disadvantage vis.
> ox-hugo/ox-jekyll/etc.? Is the functionality the same more_or_less?
>
> What ox-hugo devs/users have to say on this?
I have never used ox-publish, but getting started with ox-hugo is really
easy. I think the main difference might be that ox-hugo is tailored
specifically for Hugo, which influences its expected directory structure,
file output format, etc. Ox-publish might be more generic and customizable
for arbitrary output formats.
--Diego
[-- Attachment #2: Type: text/html, Size: 825 bytes --]
next prev parent reply other threads:[~2018-05-09 11:38 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
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 [this message]
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=CAGY83EchNTJcRWkUKiUktKF6M2CSzqfsvMBmfeMnXmKBD63gzA@mail.gmail.com \
--to=diego@zzamboni.org \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
--cc=smntov@gmail.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).