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

Hello, I have replied to your message, and the previous one, on the new thread dedicated to the search engine feature, at "Remarks #5": https://list.orgmode.org/878quf1ji0@k-7.ch/T/#m2425dcfc7665e88aefcbd81800d2d83aef98cd5b Best regards --- Gendre Sébastien Orm Finnendahl writes: >

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

Hello, I have replied to your message, and the previous one, on the new thread dedicated to the search engine feature, at "Remarks #3": https://list.orgmode.org/878quf1ji0@k-7.ch/T/#m2425dcfc7665e88aefcbd81800d2d83aef98cd5b Best regards --- Gendre Sébastien Orm Finnendahl writes: >

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

Hello, I have replied to your message, and the previous one, on the new thread dedicated to the search engine feature, at "Remarks #6": https://list.orgmode.org/878quf1ji0@k-7.ch/T/#m2425dcfc7665e88aefcbd81800d2d83aef98cd5b Best regards --- Gendre Sébastien Ihor Radchenko writes: >

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

Hello, I have replied to your message, and the previous one, on the new thread dedicated to the search engine feature, at "Remarks #4": https://list.orgmode.org/878quf1ji0@k-7.ch/T/#m2425dcfc7665e88aefcbd81800d2d83aef98cd5b Best regards --- Gendre Sébastien Ihor Radchenko writes: > O

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

Hello, I have replied to your message, and the previous one, on the new thread dedicated to the search engine feature, at "Remarks #2": https://list.orgmode.org/878quf1ji0@k-7.ch/T/#m2425dcfc7665e88aefcbd81800d2d83aef98cd5b Best regards --- Gendre Sébastien Max Nikulin writes: > O

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

Ihor Radchenko writes: > Before I continue with my replies, I'd like to add one general comment. > > You are suggesting a number of new diverse features. > Ideally, it is better to discuss and add them separately. > Especially, when we move ahead and discuss the concrete implementations > or patc

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

Orm Finnendahl writes: >> It should probably work for single page as well. I do not see why >> not. > > sure it works. I just question the raison d'etre, when single page > search is already integrated into webbrowsers. But as always there > will be people arguing that it is necessary to have a

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

Am Sonntag, den 08. September 2024 um 18:42:51 Uhr (+) schrieb Ihor Radchenko: > I agree that including indexer is just a question of adding specific > javascript. > > But I think that it would be useful to provide some default toggle to > include such a tool without having to know the details

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

Orm Finnendahl writes: > 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. > > A

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

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

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

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 is

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

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: emacs-devel. Re: [Nicolas Graves] [PATCH v6 01/10] rde: emacs: Start emacs in --daemon mode, with

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

Before I continue with my replies, I'd like to add one general comment. You are suggesting a number of new diverse features. Ideally, it is better to discuss and add them separately. Especially, when we move ahead and discuss the concrete implementations or patches. I will also provide some lin

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

Hello. Thank you for your reply, I add mines after the quotes. Ihor Radchenko writes: >> - A search field for an local search engine > > +1, but I would like to know more details - will it be something you > want to ship with Org mode, as JS? For now, I have done successful testes with Page

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

Sébastien Gendre writes: > Here is what I plan to add, on each generated webpage, compared to what > the built-in HTML exporter already provide: > > - A side panel containing: Some kind of side/top panel would make sense, I think. > - A site web name and/or logo +1 > - A search field for

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

Some precision about the time: I'm actually finishing the last work I have to do for the school, so I will be very busy until December. Until them, I can only dedicate my breaks to the enhancement of the HTML exporter. Sébastien Gendre writes: > [[PGP Signed Part:Good signature from B586F7

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

TL;DR: Plan to add features to HTML export, do I add them in the built-in HTML exporter (as upstream contribution) ? Or as a downloadable derived backend ? Which on do you prefer ? Hello, I plan to use Org-publish to create a website from Org-mode files. And I would have some feat