From: Robert Klein <roklein@roklein.de>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Step by step tutorial on Worg on how to create a new export backend
Date: Sat, 15 Feb 2020 21:17:33 +0100 [thread overview]
Message-ID: <20200215211733.3ba67f0a@happy.intern.roklein.de> (raw)
In-Reply-To: <87lfp4yjy5.fsf@gnu.org>
On Fri, 14 Feb 2020 21:48:02 +0100
Bastien <bzg@gnu.org> wrote:
> We have a good reference documentation for creating export backends:
> https://orgmode.org/worg/dev/org-export-reference.html
>
> But we *badly* need a step by step tutorial on Worg.
>
> Anyone would like to volunteer for writing such a tutorial?
>
I actually began writing something about “deriving a export backend”
back in 2013.
Deriving a backend might be an ideal starting point of creating an
export backend; IIRC the main difference is, for a new backend you'll
have to provide /all/ the options whereas in a derived exporter you
could simply provide e.g. another src-block interpretation as
alternative to the html exporter.
Back then for some reason I didn't like punchagan's “org2blog” (which
is not an exporter) and wrote my own ox-blog (derived from ox-html) for
exporting into wordpress (i don't use wordpress anymore, so it's
rotting away on github...).
Best regards
Robert
next prev parent reply other threads:[~2020-02-15 20:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 20:48 Step by step tutorial on Worg on how to create a new export backend Bastien
2020-02-15 17:55 ` Marcin Borkowski
2020-02-16 0:46 ` Jean-Christophe Helary
2020-02-16 8:05 ` Marcin Borkowski
2020-02-16 8:09 ` Jean-Christophe Helary
2021-05-01 8:26 ` Emacs Lisp book (was: Step by step tutorial on Worg on how to create a new export backend) Marcin Borkowski
2021-05-01 8:37 ` Timothy
2021-05-01 9:33 ` Marcin Borkowski
2020-02-15 20:17 ` Robert Klein [this message]
2020-02-16 8:21 ` Step by step tutorial on Worg on how to create a new export backend Stig Brautaset
2020-02-16 10:49 ` Bastien
2020-02-20 22:00 ` Stig Brautaset
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=20200215211733.3ba67f0a@happy.intern.roklein.de \
--to=roklein@roklein.de \
--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).