[IMP] extensions: add copy to markdown button

[mattismegevand]

Add a "Copy to Markdown" button using Turndown to convert HTML docs to Markdown, with support for syntax-highlighted code blocks. This will allow an easier usage of LLM.

Here's how it look (copy button is next to version selector, right window show raw output and preview):

[robodoo]

[AntoineVDV]

Hi, could you elaborate on the purpose of this PR and/or link a related task?

From the current "allow an easier usage of LLM" explanation, I assume that it'd be because LLMs digest Markdown more easily than HTML, but it's not clear at all to me why the translation should happen in JS rather than on a server, and why every user should now have a very confusing copy to md button.

[mattismegevand]

Hello! Yes, this is something I’ve seen in other documentation systems and found very practical.
It’s especially useful for dev docs, as it allows you to copy clean Markdown and ask questions to LLMs with better context and fewer hallucinations.
I chose a client-side approach to avoid any backend changes, but I’m happy to adjust if you think it would be better handled server-side let me know!

[AntoineVDV]

Ok, I see. I thought it was meant for a specific project, like a RAG chatbot fetching information from the documentation, hence my suggestion to pre-process the information on the server.

For a general-purpose "copy to clipboard and paste in chatbot prompt" usage, I'm sure that the current approach fits very well. It might be perfect for power users of other technical documentation, but our readers are primarily functional people and not that tech-savvy.

WDYT @xpl-odoo @auva-odoo?

[mattismegevand]

I understand your point, potentially we could limit this feature to the dev docs only?
So that we don't confuse non-tech people.

[xpl-odoo]

Currently, I doubt it would be helpful for the average reader of the user's part of the documentation; the help chatbot should be enough in most cases.

[AntoineVDV]

I understand your point, potentially we could limit this feature to the dev docs only? So that we don't confuse non-tech people.

To be honest, I doubt this feature's usefulness would outweigh its maintenance cost in our dev docs. The information is scattered across a bazillion pages that all large LLMs have already digested thousands of times anyway. The per-page export and manually feeding limitations make me believe she should not go forward with this.

[mattismegevand]

Ok closing the PR then