From mboxrd@z Thu Jan 1 00:00:00 1970 From: myglc2@gmail.com Subject: Re: org to static site? Date: Tue, 05 Dec 2017 11:40:40 -0500 Message-ID: <86indlw2k7.fsf@gmail.com> References: <86fu8w5oyf.fsf@gmail.com> <87fu8unqut.fsf@hyperbola.info> <86wp25kfgb.fsf@gmail.com> <87o9nd73ww.fsf@gmx.us> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35590) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eMGH3-0005Lr-7R for emacs-orgmode@gnu.org; Tue, 05 Dec 2017 11:40:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eMGGz-0002jD-Ar for emacs-orgmode@gnu.org; Tue, 05 Dec 2017 11:40:49 -0500 Received: from mail-wm0-x230.google.com ([2a00:1450:400c:c09::230]:42559) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eMGGz-0002iA-3t for emacs-orgmode@gnu.org; Tue, 05 Dec 2017 11:40:45 -0500 Received: by mail-wm0-x230.google.com with SMTP id l141so2461306wmg.1 for ; Tue, 05 Dec 2017 08:40:44 -0800 (PST) In-Reply-To: <87o9nd73ww.fsf@gmx.us> (rasmus@gmx.us's message of "Tue, 05 Dec 2017 13:30:39 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Rasmus Cc: emacs-orgmode@gnu.org 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=E2=80=99t see why you couldn=E2=80=99t do t= hat with > ox-publish.el in addition to maybe Make. > > Based on your description, I=E2=80=99d 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.