From: myglc2@gmail.com
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: org to static site?
Date: Tue, 05 Dec 2017 11:40:40 -0500 [thread overview]
Message-ID: <86indlw2k7.fsf@gmail.com> (raw)
In-Reply-To: <87o9nd73ww.fsf@gmx.us> (rasmus@gmx.us's message of "Tue, 05 Dec 2017 13:30:39 +0100")
On 12/05/2017 at 13:30 Rasmus writes:
> myglc2@gmail.com writes:
>
>> On 12/01/2017 at 18:19 Adonay Felipe Nogueira writes:
>>
>>> The best approach for me is also to use something such as org-publish,
>>> and a simple static site server such as GNU Serveez.
>>
>> Have you used org-publish in earnest? I settled on the approach used in
>> https://github.com/myglc2/emacsite only after trying out org-publish
>> extensively. I needed source and generated content to sit together in
>> the working tree of complex multi-level reproducible research projects
>> and to be transparently revision controlled and hosted on the
>> organization's Github Entreprise server.
>
> I am happy that you found a method that works for you.
>
> As a contrasting point, I don’t see why you couldn’t do that with
> ox-publish.el in addition to maybe Make.
>
> Based on your description, I’d copy source files using
> org-publish-attachment to a publish dir and compiled files to the same dir
> via different projects in org-publish-project-alist.
Yes, this works and I this before switching to the emacsite approach.
[...]
> If you have any suggestions on how to improve ox-publish to better suit
> please share them.
Does org-publish now support making the publishing directory coincide
with the project directory? If not, this is the suggestion.
next prev parent reply other threads:[~2017-12-05 16:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 15:00 org to static site? Matt Price
2017-05-31 15:08 ` Russell Adams
2017-05-31 15:17 ` Jeffrey Brent McBeth
2017-05-31 15:29 ` Russell Adams
2017-05-31 15:34 ` John Hendy
2017-05-31 16:20 ` Russell Adams
2017-05-31 16:37 ` John Kitchin
2017-05-31 15:32 ` John Hendy
2017-05-31 16:08 ` Puneeth Chaganti
2017-05-31 16:17 ` John Hendy
2017-05-31 17:05 ` Chunyang Xu
2017-05-31 19:51 ` John Ankarström
2017-05-31 18:23 ` lists
2017-06-01 7:46 ` Julian M. Burgos
2017-06-01 10:09 ` Rasmus
2017-06-04 18:26 ` Scott Randby
2017-06-05 5:59 ` John Ankarström
2017-06-05 16:54 ` Scott Randby
2017-06-05 21:16 ` Nick Dokos
2017-06-06 2:41 ` Scott Randby
2017-06-10 9:21 ` Nicolas Goaziou
2017-06-10 18:13 ` Scott Randby
2017-06-06 9:12 ` Fabrice Popineau
2017-06-08 8:14 ` Ken Mankoff
2017-11-30 5:13 ` George myglc2 Clemmer
2017-12-01 17:17 ` Tory S. Anderson
2017-12-01 21:13 ` George myglc2 Clemmer
2017-12-01 20:19 ` Adonay Felipe Nogueira
2017-12-02 2:53 ` myglc2
2017-12-05 12:30 ` Rasmus
2017-12-05 16:40 ` myglc2 [this message]
2017-12-05 19:10 ` ox-publish export subtree scopes? (Was: org to static site?) Kaushal Modi
2017-12-10 7:15 ` ox-publish export subtree scopes? Narendra Joshi
2017-12-19 11:53 ` Rasmus
2018-01-15 21:27 ` Adonay Felipe Nogueira
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=86indlw2k7.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).