Re: Dynsite: easier configuration of projects, with config.or instead of emacs lisp and dynamic relative paths

[John Kitchin <jkitchin@andrew.cmu.edu>]

[-- Attachment #1: Type: text/plain, Size: 3035 bytes --]

I implemented a version of elisp links to dynamically generated content at
export time here:
http://jkitchin.github.io/blog/2013/10/14/Lisp-links-in-org-mode-to-dynamically-generated-content/

I am not sure it was you are thinking about, but maybe it could give you
some ideas.

j

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 Mon, Oct 14, 2013 at 1:14 PM, John Kitchin <jkitchin@andrew.cmu.edu>wrote:

> It seems like this is something that could be done with a filter pretty
> easily. Just define a lisp link, and write a filter that handles links of
> that type.
>
> I did something like this to selectively handle different types of links
> here:
> http://jkitchin.github.io/blog/2013/09/28/Changing-links-to-files-so-they-work-in-a-blog/
>
> basically you check the type of link, and set the output accordingly. you
> would ignore links that were not your lisp type.
>
> j
>
> 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 Sun, Oct 13, 2013 at 2:39 PM, Iannis Zannos <zannos@gmail.com> wrote:
>
>>
>> Hello,
>>
>> I'd like to present my project Dynsite for orgmode here, as I believe it
>> fits in well with the currnent status of org-publish. Dynamite is a package
>> that simplifies the task of creating project configurations for
>> org-publish. One can define many projects in a "site" just by placing a
>> config.org in any folder contained in the site, and writing the
>> properties of the project as org-mode nodes. Plus, relative paths from
>> subfolders to the root are provided automatically (no need to write a
>> separate property config for each level as in the latest org-publish
>> scheme).
>>
>> The documentation is here: http://iani.github.io/dynsite/
>> And the source code + documentation is here:
>> https://github.com/iani/dynsite
>>
>> The code is now compatible with the 8.0+ version of org-publish. Not
>> elegant code at all, but I hope it may give some useful ideas for general
>> use or future directions in Org mode.
>>
>> And a question: Looking at export filters, I see that there is no filter
>> for substituting the result of a lisp expression into the file. That would
>> be extremely handy.  The wonderful package o-blog is largely based on it. (
>> https://github.com/renard/o-blog). The format used by o-blog is:
>> <lisp>(ob:insert-template "page_header.html")</lisp>
>> Possibly one could use some other format like {lisp}....{/lisp}, or
>> something more aligned to current mark-up schemes in Org. This would open
>> up many useful possibilities. Any tips on adding new filters? Or other ways
>> to substitute the result of a lisp expression in the final rendered text?
>>
>> Iannis Zannos
>>
>
>

[-- Attachment #2: Type: text/html, Size: 4725 bytes --]