Re: [O] Moving from Jekyll to Orgmode

[Kaushal Modi]

Hello,

On Wed, May 9, 2018, 3:36 AM ST <address@hidden> 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