# Ox-hugo & go-org

**URL:** <https://discourse.gohugo.io/t/ox-hugo-go-org/21254>\
**Category:** support\
**Created:** [October 13, 2019, 12:22pm UTC](https://discourse.gohugo.io/t/ox-hugo-go-org/21254 "2019-10-13T12:22:28Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![gour](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/gour/32/197_2.png) [@gour](https://discourse.gohugo.io/u/gour)\
**Post date:** [October 13, 2019, 12:22pm UTC](https://discourse.gohugo.io/t/ox-hugo-go-org/21254/1 "2019-10-13T12:22:28Z")

</div>

I have to start working on more content and creating few web sites so wonder whether there is plan to use [go-org](https://github.com/niklasfasching/go-org) (if mature enough) within ox-hugo or it is still safer to convert org-mode markup to Blackfriday’s markdown?

---

<div class="post-metadata">

**Author:** ![kaushalmodi](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/kaushalmodi/32/2567_2.png) [@kaushalmodi](https://discourse.gohugo.io/u/kaushalmodi)\
**Post date:** [October 14, 2019, 3:00am UTC](https://discourse.gohugo.io/t/ox-hugo-go-org/21254/2 "2019-10-14T03:00:18Z")

</div>

> [@gour](#):
>
> whether there is plan to use [go-org](https://github.com/niklasfasching/go-org) (if mature enough) within ox-hugo

I cannot “use” go-org in ox-hugo 🙂

- go-org kind of translates Org to HTML.
- ox-hugo translates Org to Markdown, which then Blackfriday picks up to translate to HTML.

You would need to pick one of these two Org mode support options.

Theoretically, I can make ox-hugo export from Org to Org (yes `ox-org` exists) for go-org to pick up, but I don’t see much value in that effort, especially because `ox-hugo` has been pretty stable in what it does for a while now.

---

<div class="post-metadata">

**Author:** ![gour](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/gour/32/197_2.png) [@gour](https://discourse.gohugo.io/u/gour)\
**Post date:** [October 14, 2019, 5:30am UTC](https://discourse.gohugo.io/t/ox-hugo-go-org/21254/3 "2019-10-14T05:30:19Z")

</div>

> [@kaushalmodi](#):
>
> Theoretically, I can make ox-hugo export from Org to Org (yes `ox-org` exists) for go-org to pick up, but I don’t see much value in that effort, especially because `ox-hugo` has been pretty stable in what it does for a while now.

Any insight how does go-org behave with ox-hugo’s testing suite which is, afaik, quite comprehensive?

---

<div class="post-metadata">

**Author:** ![kaushalmodi](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/kaushalmodi/32/2567_2.png) [@kaushalmodi](https://discourse.gohugo.io/u/kaushalmodi)\
**Post date:** [October 14, 2019, 1:53pm UTC](https://discourse.gohugo.io/t/ox-hugo-go-org/21254/4 "2019-10-14T13:53:31Z")

</div>

No, I am not qualified enough to tell how well go-org runs the ox-hugo test suite “as-is”.

All I can tell is that ox-hugo is for a better in-Emacs and better native Org mode experience. ox-hugo supports posts written as Org mode subtrees, allows inheritance of Org mode property drawers, supports Org macros, any arbitrary user-written _Elisp hooks and advices_ around the ox-hugo functions, and much more (including not requiring Hugo features like archetypes, shortcodes and the new cascade front-matter for most cases)!

So in the end, it’s you, the user, who needs to try out the native Org mode support in Hugo via go-org and the Org -\> Markdown flow via ox-hugo and see that best works for you.

* * *

ox-hugo was developed for one purpose and it’s still true… it makes it trivial to take **any** of your existing Org mode files and convert them to Hugo content by adding just 2 Org keywords at the minimum (`HUGO_BASE_DIR` and `EXPORT_FILE_NAME`), without even needing to move those files from where they already are.

---

<div class="post-metadata">

**Author:** ![gour](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/gour/32/197_2.png) [@gour](https://discourse.gohugo.io/u/gour)\
**Post date:** [October 14, 2019, 7:45pm UTC](https://discourse.gohugo.io/t/ox-hugo-go-org/21254/5 "2019-10-14T19:45:26Z")

</div>

> [@](#):
>
> No, I am not qualified enough to tell how well go-org runs the ox-hugo test suite “as-is”.

OK.

> [@](#):
>
> All I can tell is that ox-hugo is for a better in-Emacs and better native Org mode experience.

I must say that, so far, I’m very pleased with ox-hugo!

> [@](#):
>
> So in the end, it’s you, the user, who needs to try out the native Org mode support in Hugo via go-org and the Org → Markdown flow via ox-hugo and see that best works for you.

Fair-enough. I’ll try go-org to see how it goes, although not sure how complete its orientation is in comparison with ‘native’ org-mode. 🙄

> [@](#):
>
> …it makes it trivial to take **any** of your existing Org mode files and convert them to Hugo content by adding just 2 Org keywords at the minimum (`HUGO_BASE_DIR` and `EXPORT_FILE_NAME`), without even needing to move those files from where they already are.

That’s, great indeed! Thank you for your input as well as work on ox-hugo. 😉

---

<div class="post-metadata">

**Author:** ![gour](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/gour/32/197_2.png) [@gour](https://discourse.gohugo.io/u/gour)\
**Post date:** [November 21, 2019, 2:18pm UTC](https://discourse.gohugo.io/t/ox-hugo-go-org/21254/6 "2019-11-21T14:18:05Z")

</div>

> [@kaushalmodi](#):
>
> All I can tell is that ox-hugo is for a better in-Emacs and better native Org mode experience.

You’re right!

I was playing a bit with go-org and it’s more natural (for me) to write posts using ox-hugo…

Just wonder if the migration to [Goldmark](https://github.com/yuin/goldmark) is going to be [smooth](https://github.com/gohugoio/hugo/issues/5963) ?

---

<div class="post-metadata">

**Author:** ![kaushalmodi](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/kaushalmodi/32/2567_2.png) [@kaushalmodi](https://discourse.gohugo.io/u/kaushalmodi)\
**Post date:** [November 30, 2019, 5:43am UTC](https://discourse.gohugo.io/t/ox-hugo-go-org/21254/7 "2019-11-30T05:43:19Z")

</div>

> [@gour](#):
>
> Just wonder if the migration to [Goldmark](https://github.com/yuin/goldmark) is going to be [smooth](https://github.com/gohugoio/hugo/issues/5963) ?

From my initial testing, `ox-hugo` Markdown exports work just fine with Hugo v0.60+ as well once you have this in your `config.toml` to allow embedded HTML in the Markdown content files:

```toml
[markup]
  [markup.goldmark]
    [markup.goldmark.renderer]
      unsafe = true

```

See [https://gohugo.io/news/0.60.0-relnotes/](https://gohugo.io/news/0.60.0-relnotes/) for details.

_If you are still using `ox-hugo` and if you are finding issues with ox-hugo + Hugo 0.60+, please open issues on ox-hugo repo._

---

<div class="post-metadata">

**Author:** ![gour](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/gour/32/197_2.png) [@gour](https://discourse.gohugo.io/u/gour)\
**Post date:** [November 18, 2024, 6:31pm UTC](https://discourse.gohugo.io/t/ox-hugo-go-org/21254/8 "2024-11-18T18:31:09Z")

</div>

Hello,

I spent some time trying out with some Wikis, but returning to Hugo, where “Content is King” (written in one’s beloved editor. 🙂

Can someone help me with the original topic ox-hugo vs go-org years after my original post?

Are there any important pro/cons one should be aware of before deciding which one to use?

---

<div class="post-metadata">

**Author:** ![jmooring](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/jmooring/32/4214_2.png) [@jmooring](https://discourse.gohugo.io/u/jmooring)\
**Post date:** [November 18, 2024, 6:43pm UTC](https://discourse.gohugo.io/t/ox-hugo-go-org/21254/9 "2024-11-18T18:43:28Z")

</div>

Both projects are actively maintained.

The guidance from @kaushalmodi is still applicable today.

---

<div class="post-metadata">

**Author:** ![dertuxmalwieder](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/dertuxmalwieder/32/496_2.png) [@dertuxmalwieder](https://discourse.gohugo.io/u/dertuxmalwieder)\
**Post date:** [November 19, 2024, 12:53am UTC](https://discourse.gohugo.io/t/ox-hugo-go-org/21254/10 "2024-11-19T00:53:19Z")

</div>

> [@gour](#):
>
> Are there any important pro/cons one should be aware of before deciding which one to use?

`ox-hugo` integrates just well into GNU Emacs while `go-org` does not.

---

<div class="post-metadata">

**Author:** ![gour](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/gour/32/197_2.png) [@gour](https://discourse.gohugo.io/u/gour)\
**Post date:** [November 19, 2024, 11:28am UTC](https://discourse.gohugo.io/t/ox-hugo-go-org/21254/11 "2024-11-19T11:28:33Z")

</div>

> [@dertuxmalwieder](#):
>
> `ox-hugo` integrates just well into GNU Emacs while `go-org` does not.

Yeah, thanks. That’s an important one!