Co-maintainers welcome?

Hey Christoph, thanks for reaching out!

We just pushed our current version - it's a quick fork of the RobotsTxt → module with a few modifications. It’s still an early version with a dead-simple settings form, but we’re thinking about extending it and maybe even rewriting it with a different approach.

Since robots.txt is mostly a static file, something you set up once and rarely touch, it makes sense to store it as a static config value.

But with llms.txt, I can imagine scenarios where the content needs to be updated dynamically based on the site’s actual content (and not just with links to content like XML sitemaps do). One option we’ve been discussing is adding Token support to the llms.txt textarea, though that wouldn’t help much when it comes to rendering entities or pulling in menus. A more complex idea is to build a UI where you can add different "section types" (as plugins) that render things like plain markdown, an entity in a given display mode, a view, etc.

I’m definitely interested in what you’ve built and your overall approach, would love to collaborate!

Hi Nodar, sorry for the late reply, this week has been crazy! Like you we are thinking that a mostly static file is not the answer, although a simple solution as a start is better than nothing. We are thinking of creating a custom content entity, which removes the baggage of nodes but retains much of the content editing features that the llms.txt file will need.
In particular, I want to be deliberate about choice of links on the Docs section (I like what Rob Loach mentioned on Drupal Slack), and especially also about the optional details piece of the specification:
- [Link title](https://link_url): Optional link details

Thanks for pushing up the module, davituri. I've started bringing in features from my original prototype into this module. The first part is dynamically building the Title and Description: https://www.drupal.org/project/llmstxt/issues/3519314 📌 Add Title/Description to Config Page Needs review

Providing fields for the people to enter information, rather than having them write markdown, will ease the user experience, and perhaps allow the llms.txt file to be a bit more dynamic.