From: Bastien <email@example.com>
To: Laszlo Elo <firstname.lastname@example.org>
Subject: Re: ox-slimhtml
Date: Wed, 16 Dec 2020 12:45:01 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <41D2E10D-BCFF-4604-8417-B499514AF904@bald.cat> (Laszlo Elo's message of "Mon, 14 Dec 2020 00:48:27 -0500")
thanks for ox-slimhtml.el and for announcing it on the list.
> Amin was kind enough to poke me to submit and post about my package, ox-slimhtml.
> In a nutshell, it is an org-export backend - transcodes Org elements to HTML/text output.
> My primary use for it, is to create derived export backends. (picture a/b testing, for example)
> By default, it outputs HTML5, essentially (as it tries to not ignore current output preferences).
> Within each transcoder, I tried to pick out the relevant core elements
> being passed through - what I skipped from the original ox-html
> exporter is the domain logic surrounding templating and navigation.
> A sample of the output can be seen here http://bald.cat/ox-slimhtml/
> From a more detailed perspective, I use it to template the output of
> some Org documents (common sources of truth); these include some
> minimal Org markup, and as such, they provide convenient
> element-by-element programmatic access. This all depends on where
> you’d like to organize the logic behind each elements’ transcoding
> process, of course - so, for now, I’ll say that it works really nice
> for me. YMMV
I encourage everyone to try exporting Org documents to HTML using your
library and see how it compares with ox-html.el for a daily usage.
next prev parent reply other threads:[~2020-12-16 11:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 5:48 ox-slimhtml Laszlo Elo
2020-12-14 9:07 ` ox-slimhtml tomas
2020-12-16 11:45 ` Bastien [this message]
2021-09-25 15:50 ` ox-slimhtml Bastien Guerry
2021-10-03 15:53 ` ox-slimhtml Amin Bandali
2021-10-03 16:03 ` ox-slimhtml Timothy
2021-10-03 17:27 ` ox-slimhtml Bastien
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 \
* 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).