Export to multiple HTML files

Export to multiple HTML files

[Pete Ley]

I can't seem to find anything in the manual or the googles.

Is there a ready-made way to use ox-html to export a subtree or file to
multiple HTML files? What I'm looking for is that format you find in
documentation (texinfo maybe? I'm not sure what is used -- forgive my
ignorance) online where it gives you the option of HTML -- one file and
HTML -- multiple files. Each heading's HTML file would just contain its
entry text and links to the HTML files of the subtrees.

Is this possible or do I need to hack something?

Thanks

Re: Export to multiple HTML files

[Marcin Borkowski]

On 2015-02-26, at 17:44, Pete Ley <peteley11235@gmail.com> wrote:

> I can't seem to find anything in the manual or the googles.
>
> Is there a ready-made way to use ox-html to export a subtree or file to
> multiple HTML files? What I'm looking for is that format you find in
> documentation (texinfo maybe? I'm not sure what is used -- forgive my
> ignorance) online where it gives you the option of HTML -- one file and
> HTML -- multiple files. Each heading's HTML file would just contain its
> entry text and links to the HTML files of the subtrees.

This: https://github.com/mbork/org-one-to-many may be a starting point.
It is a small library which splits an org file into many smaller ones.
(Bug reports/feature requests welcome, btw.)  The main function returns
the list of generated files, so you could #'mapc some export function
over it.

> Is this possible or do I need to hack something?
>
> Thanks

Hth,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University

Re: Export to multiple HTML files

[Pete Ley]

> This: https://github.com/mbork/org-one-to-many may be a starting point.
> It is a small library which splits an org file into many smaller ones.
> (Bug reports/feature requests welcome, btw.)  The main function returns
> the list of generated files, so you could #'mapc some export function
> over it.

Thanks! I'll check this out. It makes it a lot easier for another
project I'm working on involving Gopher, too.