Org-mode mailing list
 help / color / mirror / Atom feed
From: Bastien <bzg@gnu.org>
To: Laszlo Elo <hello@bald.cat>
Cc: emacs-orgmode@gnu.org
Subject: Re: ox-slimhtml
Date: Wed, 16 Dec 2020 12:45:01 +0100
Message-ID: <875z52ug8y.fsf@gnu.org> (raw)
In-Reply-To: <41D2E10D-BCFF-4604-8417-B499514AF904@bald.cat> (Laszlo Elo's message of "Mon, 14 Dec 2020 00:48:27 -0500")

Hi Laszlo,

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.

Thanks!

-- 
 Bastien


      parent reply	other threads:[~2020-12-16 11:46 UTC|newest]

Thread overview: 3+ 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]

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://orgmode.org

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875z52ug8y.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=hello@bald.cat \
    /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

Org-mode mailing list

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://orgmode.org/list/0 list/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 list list/ https://orgmode.org/list \
		emacs-orgmode@gnu.org
	public-inbox-index list

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.yhetil.org/yhetil.emacs.orgmode
	nntp://news.gmane.io/gmane.emacs.orgmode


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git