Thanks! I am the ox-hugo developer. Would love to get feedback if you ever end up using it.

but I wouldn’t like to export to Markdown Blackfriday.

Out of curiosity, what’s the reason for that?

You can choose to export Org to Markdown using ox-hugo and commit the Markdown files, or do the ox-hugo export + run Hugo in tandem on CI (i.e. commit only the Org files). I use the latter approach for the https://ox-hugo.scripter.co and the official use-package doc site generation.

Just in case you don’t know what I am talking about, this is a LaTeX header:

#+DATE: [2016-09-01 jue 16:00]

Goorgeous expects the date to be already in TOML compatible date string format… few examples:

Although I like very much your project and I am still testing it, I’d like some tool able to manage native org-mode files with LaTeX headers as they are written.

Before testing your extension I was excited with the feature to use Emacs orgmode file so I have already inserted HUGO headers in the org files I’ve been playing with. If I have to do that for all of them it is another extra task.

You can choose to export Org to Markdown using ox-hugo and commit the Markdown files, or do the ox-hugo export + run Hugo in tandem on CI (i.e. commit only the Org files). I use the latter approach for the https://ox-hugo.scripter.co and the official use-package doc site generation.

I have chosen the option auto-export-on-saving (one post per file) and it works, but I also get other errors regarding timeset and configuration… I have to take a look again to some files I changed.

Well, that was my primary aim to write the ox-hugo package… though, “keep the Org files as they are” is more effective with per-subtree export option (example). For per-file export option, you do need to manually specify tags, etc (example).

flow:

I’d like some tool able to manage native org-mode files with LaTeX headers as they are written

I’d appreciate if you can open an issue on ox-hugo repo and post an example file of yours. I don’t exactly follow what you mean by “LaTeX headers”… The #+DATE example you posted earlier is an Org keyword, which is parsed by all Org exporters (including ox-latex, and even ox-hugo).

flow:

I have already inserted HUGO headers in the org files I’ve been playing with. If I have to do that for all of them it is another extra task.

As I mentioned earlier, unfortunately that’s the only way if you choose per-file export. If you organize your files as subtrees in a single Org file, most of the meta data required for Hugo front-matter is auto-interpreted as explained in the first table here. Re-organizing your files into subtrees would also be an extra task, but it would be a one-time thing. If you are mildly interested in the per-subtree export flow, see this recent test commit to ox-hugo that shows how a subtree added to the tests Org file exports to a Hugo markdown post.

flow:

but I also get other errors regarding timeset and configuration

I’d appreciate if you can open an issue on ox-hugo repo with your sample file and steps to reproduce those errors.

flow:

I have realized is orgmode which stamps time in that format,

Correct. That time stamp format has nothing to do with LaTeX… and thus I talk about clarifying what you mean by “LaTeX headers”.

so maybe if I get that (orgmode timestamp in RFC 3339) it is possible to use as they are written in orgmode.

Yes. You can customize the time stamp format to anything to like… see C-h v org-time-stamp-formats… change the cdr of that variable… eventually it is Emacs!

If the date stamp is the only thing that hinders your blogging flow, then may be you don’t need ox-hugo, but even then please file issues for the errors you are seeing.