From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Brett Viren <bv@bnl.gov>
Cc: "emacs-orgmode@gnu.org Mode" <emacs-orgmode@gnu.org>
Subject: Re: Amazing demonstration by John Kitchin
Date: Fri, 27 Sep 2013 11:04:02 -0400 [thread overview]
Message-ID: <CAJ51ETrUsbSwc3vMx4+Zr_hBihBhnZB4CBnm27oZOOnqoZ=h=g@mail.gmail.com> (raw)
In-Reply-To: <ir4mwmyv076.fsf@lycastus.phy.bnl.gov>
[-- Attachment #1: Type: text/plain, Size: 2165 bytes --]
Here is part of how I use org-mode to publish to my blog:
http://jkitchin.github.io/blog/2013/09/27/Publishing-to-blogofile-using-org-mode/
My approach is pretty automated, but I have left some manual steps in
place. Basically I write a post as a heading in some org-file, press a key,
which generates the html post in the required format and in the right
place. Then I build the blog, and push it to github. All that could happen
with a key press, but sometimes I like to inspect the content before
pushing.
I will try to describe the actual blog setup another time. I use blogofile,
which is a static blog generator, so it is quite different from using
wordpress, or other blog systems that you publish to via rss, xml-rpc,
etc...
John
-----------------------------------
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
On Fri, Sep 27, 2013 at 9:55 AM, Brett Viren <bv@bnl.gov> wrote:
> John, I finally got a chance to watch your really nice SciPy talk last
> night.
>
> I've been trying to incorporate Reproducible Research methods with org
> into my own work. I strive to do more and what you are doing looks to
> provide a wealth of examples. I hope more researchers follow this
> methodology.
>
> One thing I've yet to get a good handle on is publishing org content in
> an automated (and beautiful) way. I was very taken with your github.io
> pages and would like to try to set up something similar for myself.
>
> Do you have a write-up or other guidance on this that I might follow?
> I've started to go through your related github repositories to figure
> out what you do but if something more guided exists it would help.
>
> Thanks,
> -Brett.
>
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
> > Hi,
> >
> > I don't know if this has been linked to before on this mailing
> > list. At SciPy 2013, John Kitchin has made an amazing
> > demonstration of Org-mode as a tool for reproducible research.
> > Really amazing to watch.
> >
> > http://www.youtube.com/watch?v=1-dUkyn_fZA
> >
> > - Carsten
>
[-- Attachment #2: Type: text/html, Size: 3059 bytes --]
next prev parent reply other threads:[~2013-09-27 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-14 17:26 Amazing demonstration by John Kitchin Carsten Dominik
2013-09-16 11:22 ` Suvayu Ali
2013-09-27 13:55 ` Brett Viren
2013-09-27 15:04 ` John Kitchin [this message]
2013-09-27 15:41 ` Brett Viren
2013-09-27 17:01 ` John Kitchin
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='CAJ51ETrUsbSwc3vMx4+Zr_hBihBhnZB4CBnm27oZOOnqoZ=h=g@mail.gmail.com' \
--to=jkitchin@andrew.cmu.edu \
--cc=bv@bnl.gov \
--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).