From: ST <smntov@gmail.com>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: Moving from Jekyll to Orgmode
Date: Wed, 09 May 2018 10:35:24 +0300 [thread overview]
Message-ID: <1525851324.2021.59.camel@gmail.com> (raw)
In-Reply-To: <87muxb6ra4.fsf@gmx.us>
On Tue, 2018-05-08 at 00:21 +0200, Rasmus wrote:
> ST <smntov@gmail.com> writes:
>
> >> > 2. how can one create "prettified" links, i.e. /features/ instead
> >> > of /features.html ? Basically during the website generation for the file
> >
> >> > features.org a directory `features` needs to be created and the html
> >> > file placed into `features/index.html` ... Is there a tutorial on how to
> >> > do that?
> >>
> >> You make a wrapper around org-html-publish-to-html that creates folders
> >> and from filename and save file as index in the folder. The wrapper
> >> function is then used as the :publishing-function in
> >> org-publish-project-alist.
> >>
> >> Something like this (untested).
> >>
> >> (lambda (plist filename pub-dir)
> >> (let ((dir (make-directory (file-name-as-directory (file-name-base filename))
> >> pub-dir)))
> >> (org-latex-publish-to-html plist filename dir)
> >> (rename-file (concat dir (file-name-base filename) ".html")
> >> (concat dir "index.html"))))
> >>
> >>
> >> You could also move around your source files before publishing via the
> >> :preparation-function.
> >
> > Thank you very much! Unfortunately I don't know lisp, so I have to learn
> > it first to understand your solution... but now I have something to
> > start with. I wish org html export will become a real static site
> > generator, like jekyll, hugo, etc..
>
> I *think* that is what ox-publish is, but indeed, it’s a bit hairy to set
> up.
Is the difficulty to setup ox-publish the sole disadvantage vis.
ox-hugo/ox-jekyll/etc.? Is the functionality the same more_or_less?
What ox-hugo devs/users have to say on this?
next prev parent reply other threads:[~2018-05-09 7:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 21:05 Moving from Jekyll to Orgmode ST
2018-04-28 21:40 ` Diego Zamboni
2018-04-28 21:42 ` Diego Zamboni
2018-04-28 22:13 ` Scott Randby
2018-04-29 8:50 ` ST
2018-04-29 9:07 ` Bastien
2018-04-29 9:22 ` ST
2018-04-29 12:58 ` Ista Zahn
2018-04-29 14:45 ` Scott Randby
2018-04-29 7:45 ` Saša Janiška
2018-04-29 12:55 ` Luis Roca
2018-04-30 20:28 ` Diego Zamboni
2018-04-30 22:43 ` Kaushal Modi
2018-05-01 18:41 ` Diego Zamboni
2018-05-04 6:49 ` Thomas S. Dye
2018-05-04 13:43 ` Kaushal Modi
2018-05-04 13:53 ` Kaushal Modi
2018-05-04 15:07 ` Thomas S. Dye
2018-04-29 16:45 ` Grant Rettke
2018-04-30 10:58 ` ST
2018-05-05 17:51 ` Rasmus
2018-05-07 8:39 ` ST
2018-05-07 22:21 ` Rasmus
2018-05-09 7:35 ` ST [this message]
2018-05-09 8:03 ` Thomas S. Dye
2018-05-09 12:37 ` ST
2018-05-09 11:38 ` Diego Zamboni
2018-05-09 12:21 ` Kaushal Modi
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=1525851324.2021.59.camel@gmail.com \
--to=smntov@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).