emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: John Hendy <jw.hendy@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Proposal for new/updated exporter tutorials on Worg
Date: Wed, 27 Mar 2013 23:51:46 -0500	[thread overview]
Message-ID: <CA+M2ft8+CJe_s--GU7EkcuqqVb2-tZdpA=X3s8wQUb2DsSRAzQ@mail.gmail.com> (raw)

Greetings,


I just pushed a changed to the 8.0 upgrade guide (scroll all the way
to the bottom):
- http://orgmode.org/worg/org-8.0.html

It features a table similar to that of the Babel languages:
- http://orgmode.org/worg/org-contrib/babel/languages.html

It simply lists the exporters Org offers, their .el location with
respect to Org directory (either in ./lisp/ox-* or
./contrib/lisp/ox-*) and a column for what I hope will turn into links
to updated exporter tutorials/detailed documentation similar to what
exists for Org Babel. Currently, Org exporter tutorials are spread
between =worg.git/org-tutorials= and =worg.git/exporters=. It looks
like the most up to date have started settling in
=worg.git/exporters=; what does the list think about deciding to stick
with that as the home for all new ox-* related documentation on Worg?

I'd propose they simply be titled according to the new names,
=worg.git/exporters/ox-*=.

I'm happy to help with a template (probably just porting
ob-doc-template to ox-template or something like that). I think the
Babel table is great; perhaps after Org-8.0 actually launches, the new
exporters could receive a similar "landing page"
(=worg.git/exporters/ox-summary= or similar) where that table could
reside and be updated as the new platform grows.

Individuals could contribute and add links at the table they can. I
think getting placeholders created for each exporter in the very near
future (which I also volunteer to do) will be really helpful as the
official shift to 8.0 happens. It will lower the barrier to entry for
getting information out of the mailing list and into Worg (I
anticipate lots more questions as infrequent upgraders/non-git users
migrate over).


Thanks for any comments/suggestions!
John

next             reply	other threads:[~2013-03-28  4:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28  4:51 John Hendy [this message]
2013-03-28  5:31 ` Proposal for new/updated exporter tutorials on Worg Thomas S. Dye
2013-03-28 10:37   ` Carsten Dominik
2013-03-28 12:35     ` John Hendy
2013-03-28 22:07       ` John Hendy
2013-03-30 13:45         ` Bastien
2013-04-01  4:58           ` John Hendy
2013-04-08 15:30             ` Bastien
2013-03-28 10:35 ` Carsten Dominik

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='CA+M2ft8+CJe_s--GU7EkcuqqVb2-tZdpA=X3s8wQUb2DsSRAzQ@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --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

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).