Re: Enhancing the HTML exporter: Create a new backend or contribute to the upstream

[Orm Finnendahl]

Hi,

 that makes no sense to me whatsoever: Post processing is already
possible and built into org-export. pagefind is an external product
with its own binaries, not written in elisp nor being by any means
connected to emacs and compiling index files on generated HTML files
is exactly that: A post process.

The javascript needed and all processing scripts can easily be
included in the header, so I don't see any point in this, except
writing a tutorial, how to integrate pagefind into someone's HTML
output with the means already available with the existing backend.

And that's not even contemplating, why someone would want to throw a
multipage site search indexer onto single page HTML output which
doesn't work on static files opened from local disks ;-)

--
Orm

Am Sonntag, den 08. September 2024 um 22:55:01 Uhr (+0700) schrieb Max Nikulin:
> On 08/09/2024 21:46, Max Nikulin wrote:
> > On 07/09/2024 18:53, Ihor Radchenko wrote:
> > > Then, pagefind can be the default (it is MIT license - GPL compatible),
> > 
> > It might be more tricky:
> 
> Sorry for the noise. Of course, if you are not going to include any pagefind
> code into Org then it is not an issue.
> 
> 
>