Make HoloViz documentation useful for llms and holoviz mcp servers

[MarcSkovMadsen]

Its early days but a standard for using an /llms.txt file to provide information to help LLMs use a website at inference time is emerging. See llmstxt.org.

I would like to propose to add this to all holoviz sites via nb-site.
I addition I would like to propose that all .md source files be included in the build docs together with .hml files.

See https://gofastmcp.com/getting-started/welcome#llm-friendly-docs for an example

• An new Sphinx llms.tx generator supports some of this. See sphinx-llms-txt.
• The sphinx-markdown-builder probably supports some of this too.

In addition it would enable building a mcp server into all holoviz packages without distribution the raw markdown files. See panel-extensions/panel-material-ui#346 for context. Here the docs index and raw .md source is collected into a big dict/ json for usage with the mcp server.

[maximlt]

You should chat with @ahuang11, he's looked into that recently.

[hoxbro]

Just some quick thoughts:

1. llms.txt - This should likely be tailored to each repository and placed within the repository itself.
2. llms-full.txt - This likely needs to be done in nbsite, as we need to convert the Notebook and .rst files into markdown.
3. .md files along with HTML files - Likely the same as above, but I'm not sure if one is better or if we need both, or if anyone knows.
4. MCP server - I think that because this is a new field, we should create a new package (for our use only, perhaps holoviz-mcp?) with a stable interface so that we can use it for our repositories. I have no idea how complex it is, but having the same code across 5-10 repositories seems too hard to maintain with so much shared code.