From: Kaushal Modi <kaushal.modi@gmail.com>
To: ST <smntov@gmail.com>
Cc: emacs-orgmode@gnu.org, Rasmus <rasmus@gmx.us>
Subject: Re: Moving from Jekyll to Orgmode
Date: Wed, 09 May 2018 12:21:44 +0000 [thread overview]
Message-ID: <CAFyQvY0y8v9UPtmvR3zSrYT8W2orNzWxqSSmXR6eCoMBzyxHVg@mail.gmail.com> (raw)
In-Reply-To: <1525851324.2021.59.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1999 bytes --]
Hello,
On Wed, May 9, 2018, 3:36 AM ST <smntov@gmail.com> wrote:
>
> Is the difficulty to setup ox-publish the sole disadvantage vis.
> ox-hugo/ox-jekyll/etc.?
ox-publish is not *that* difficult to set up. Once you have it set up once,
you just reuse that with minor tweaks for different projects. The Org
manual has nice examples of simple and complex ox-publish configs; try them
out.
For me, personally, ox-publish didn't turn out to be the right tool for
blogging, especially where I want to have a single Org file to hold
multiple posts. I do use it though for applications like batch-exporting an
Org file or a directory of Org files to multiple formats.
Talking about comparing it with ox-hugo/ox-jekyll, etc... they don't
compare apples to apples.
Ox-publish is an inbuilt Org utility that works with *any* Org exporter
backend that has hooks for ox-publish (ox-hugo hasn't done that; read
further for more).
Whereas, ox-hugo is an Org exporter backend that exports to Markdown
(mostly standard Markdown + some Hugo specific syntax + bits and pieces of
HTML where necessary) + Hugo front-matter + fine-tuned "ox-publishy"
functionality.
Is the functionality the same more_or_less?
>
Again, not apples to apples..
>
Here's a coarse way to explain the function of ox-publish.. it takes the
Org files from the specified dir, exports them using an
ox-publish-supporting exporter, and puts them in some destination dir.
Ox-hugo does this:
- Exports the current Org file as a single post, or loops through subtrees
(using an interesting logic) in the current file and exports them as
individual posts. (Ox-publish does not allow exporting subtrees from a
single Org file.)
- The destination for exported Markdown files is decided based on
Hugo-specific Org keywords like HUGO_BASE_DIR, HUGO_SECTION, HUGO_BUNDLE.
Here's where ox-hugo works sort of like ox-publish.
What ox-hugo devs/users have to say on this?
>
Hope that helps clarify the differences.
Kaushal
> --
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 3263 bytes --]
prev parent reply other threads:[~2018-05-09 12:21 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
2018-05-09 12:21 ` Kaushal Modi [this message]
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=CAFyQvY0y8v9UPtmvR3zSrYT8W2orNzWxqSSmXR6eCoMBzyxHVg@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--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).