Yes, you are right. Maintaining a JS on org-mode could be a bad idea.

My main concerns with this third solution was more about:

* What if we also add a search capability in Org-mode and not only in
  HTML exported pages ?

* Do we have a search on the whole site directly from each page, or on a
  dedicated page ?


For the second point, it's a question I ask myself since multiple days.
From a user experience, is it better to have the search engine
accessible directly from each page or in a dedicated page.


Ihor Radchenko <yanta...@posteo.net> writes:

> Sébastien Gendre <s...@k-7.ch> writes:
>
>> A third solution would be to add a search feature to Org-mode, that
>> could be used from Org-mode and exported in HTML.
>> ...
>> # Step 1: Search feature in Org-mode only
>> ...
>> # Step 2: Add HTML export of the search feature
>> ...
>> # Step 3: An option in org-publish to auto-generate a search page
>
>> The search feature could be entirely new, or based on org-ql. It would
>> be nice to be based on org-ql, as I could help to make it upstream. It
>> would require to add files as target for search.
>>
>> For the search in the web page, I could write the JS script, re-use an
>> existing library or not. All the HTML part could be customized with
>> parameters specific to the HTML exporter.
>>
>> It's a lot of work and more ambitious than solution 1 or 2 in my
>> previous e-mail. But it would add the search feature not only in
>> HTML export but in Org-mode too. And it could help to make org-ql
>> upstream.
>
> I am skeptical about maintaining a JS script in the core.
> We had a very bad experience with infojs (which still lacks maintenance).
> I'd rather go for extendable infrastructure than implementing something
> from scratch.
>
> For org-ql, there are other reasons why org-ql is not upstreamed. They
> have nothing to do with the lack of motivation. They have something to
> do with the lack of free time on Adam's side.
> See https://github.com/alphapapa/org-ql/issues/409 and
> https://github.com/alphapapa/ts.el/issues/29

Attachment: signature.asc
Description: PGP signature

Reply via email to