From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode markup vs rst for general content
Date: Thu, 09 Mar 2017 15:38:20 -0500 [thread overview]
Message-ID: <m2o9xa424j.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <87bmta5kfn.fsf@mat.ucm.es>
org does not deal with javascript or css for me. Those are defined by
the static blog engine (blogofile in this case).
I wrote some posts quite a while ago on the setup here:
http://kitchingroup.cheme.cmu.edu/blog/2013/09/27/Installing-and-configuring-blogofile/
http://kitchingroup.cheme.cmu.edu/blog/2013/09/27/Publishing-to-blogofile-using-org-mode/
If I was starting from scratch I would do something similar, but might
go more for Nikola, Pelican, or maybe one of the org-emacs solutions
that are around.
Uwe Brauer writes:
>>>> "John" == John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
> > Could you be more specific about what kind of richness you are looking
> > for? Many people blog from org-mode, including myself. I use org-mode to
> > generate html that is rendered with blogofile
> > (http://kitchingroup.cheme.cmu.edu) but others do many other variations.
>
> Hi John
>
> I just had a look[1], that page contains java script and css, how does org
> deal with those?
>
> Uwe
>
> Footnotes:
> [1] because I might be interested in doing something similar.
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2017-03-09 20:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 9:14 org-mode markup vs rst for general content Saša Janiška
2017-03-09 18:50 ` John Kitchin
2017-03-09 19:17 ` Uwe Brauer
2017-03-09 20:38 ` John Kitchin [this message]
2017-03-09 21:40 ` Uwe Brauer
2017-03-09 22:03 ` Saša Janiška
2017-03-09 23:27 ` Alan L Tyree
2017-03-10 0:17 ` Samuel Wales
2017-03-10 0:49 ` Alan L Tyree
2017-03-10 1:25 ` Alan L Tyree
2017-03-10 11:15 ` Uwe Brauer
2017-03-10 14:47 ` John Kitchin
2017-03-10 16:14 ` Uwe Brauer
2017-03-10 16:24 ` Uwe Brauer
2017-03-10 17:06 ` John Kitchin
2017-03-10 17:41 ` Uwe Brauer
[not found] ` <fc159a4ac13f4e439d8007f9de98d495@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-10 17:57 ` Eric S Fraga
2017-03-10 15:21 ` Saša Janiška
[not found] ` <e047c50c99ba4e8ba5ccfb4029b5aabc@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-10 9:09 ` Eric S Fraga
2017-03-10 20:32 ` Samuel Wales
2017-03-10 22:28 ` Alan L Tyree
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=m2o9xa424j.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=oub@mat.ucm.es \
/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).