From: Alejandro Alcalde <algui91@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Migrating from HUGO to org-publish
Date: Sat, 23 May 2020 11:32:27 +0200 [thread overview]
Message-ID: <CAK-xUNCgRjpyZCW+F1kSLGAS9650M8HkYH_g8idjyMgp18a4bg@mail.gmail.com> (raw)
In-Reply-To: <871rnbhv1o.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
Hello Bastien,
thanks for replying. I am considering this post:
http://duncan.codes/posts/2019-09-03-migrating-from-jekyll-to-org/index.html
But I still need to figure out how I will try to avoid loosing too much
traffic due to 404 caused by blog posts not pointing to the same url.
Will keep you posted.
Bests
*-- Alejandro Alcalde - elbauldelprogramador.com
<http://elbauldelprogramador.com/en>*
On Sat, May 23, 2020 at 11:15 AM Bastien <bzg@gnu.org> wrote:
> Hi Alejandro,
>
> Alejandro Alcalde <algui91@gmail.com> writes:
>
> > 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
>
> I don't have any useful suggestion here, but if you finally manage to
> do the conversion, please consider explaining how you did it to other
> users, they'll surely appreciate it.
>
> Thanks!
>
> --
> Bastien
>
[-- Attachment #2: Type: text/html, Size: 1976 bytes --]
next prev parent reply other threads:[~2020-05-23 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 4:19 Migrating from HUGO to org-publish Alejandro Alcalde
2020-05-23 9:14 ` Bastien
2020-05-23 9:32 ` Alejandro Alcalde [this message]
2020-05-26 23:58 ` James R Miller
-- strict thread matches above, loose matches on Subject: below --
2020-05-12 12:40 Alejandro Alcalde
2020-12-10 6:42 ` Alejandro Alcalde
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=CAK-xUNCgRjpyZCW+F1kSLGAS9650M8HkYH_g8idjyMgp18a4bg@mail.gmail.com \
--to=algui91@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
/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).