emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alejandro Alcalde <algui91@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Migrating from HUGO to org-publish
Date: Thu, 10 Dec 2020 07:42:18 +0100	[thread overview]
Message-ID: <CAK-xUNAiouBhmGhLyr85JNoaJhE2937Uk2D98O8icd0jWi5KOw@mail.gmail.com> (raw)
In-Reply-To: <CAK-xUNCcqCRF6L2YKUMriuVwxmBkg9GB6kR9eVMZbA7qvbqzgw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1587 bytes --]

Hello, at the end I manage to migrate without losing all hugo content.


Alejandro Alcalde <algui91@gmail.com> schrieb am Di. 12. Mai 2020 um 14:40:

> Hello, I am looking to migrate from Hugo to org-publish, is there an easy
> way? I’ve have found several guides to migrate from jekyll, like this one:
> https://duncan.codes/posts/2019-09-03-migrating-from-jekyll-to-org/index.html
> 2
> <https://duncan.codes/posts/2019-09-03-migrating-from-jekyll-to-org/index.html>
> Unfortunately I do not know how to do it smoothly with my set up.
> I have some posts written in plain org, that is no problem. But I also
> have the majority of my blog posts written in markdown (With YAML header
> and TOML header), since I once migrated from Jekyll to Hugo.
> I though maybe pandoc could help me in the process, but when converting a
> markdown file to org, I am loosing all TOML or YAML headers, so the
> resulting org file have no #+ properties.
> Any suggestions? I could write some python code that read YAML and TOML
> headers and output, but I have lots of custom headers (
> https://github.com/elbaulp/algui91-hugo/blob/master/content/post/create-deploy-telegram-bot.en.md)
> like url that will cause 404 errors when migrating to org-publish
> Thanks and Have a nice day.
> *-- Alejandro Alcalde - elbauldelprogramador.com
> <http://elbauldelprogramador.com/en>*
*-- Alejandro Alcalde - elbauldelprogramador.com

[-- Attachment #2: Type: text/html, Size: 4418 bytes --]

  reply	other threads:[~2020-12-10  6:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 12:40 Migrating from HUGO to org-publish Alejandro Alcalde
2020-12-10  6:42 ` Alejandro Alcalde [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-05-08  4:19 Alejandro Alcalde
2020-05-23  9:14 ` Bastien
2020-05-23  9:32   ` Alejandro Alcalde
2020-05-26 23:58     ` James R Miller

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:

  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=CAK-xUNAiouBhmGhLyr85JNoaJhE2937Uk2D98O8icd0jWi5KOw@mail.gmail.com \
    --to=algui91@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).