[Feat]: Support for LLM

[productdevbook]

Which variants of Embla Carousel are relevant to this feature request?

• embla-carousel (Core)
• embla-carousel-react
• embla-carousel-vue
• embla-carousel-svelte
• embla-carousel-autoplay
• embla-carousel-auto-scroll
• embla-carousel-solid
• embla-carousel-auto-height
• embla-carousel-class-names
• embla-carousel-fade
• embla-carousel-docs (Documentation)
• embla-carousel-docs (Generator)

Feature description

Svelte provides a dedicated LLM documentation file (llms-full.txt)

Additional Context

Additional details here...

Before submitting

• I've made research efforts and searched the documentation
• I've searched for existing issues
• I agree to follow this project's Contributing Guidelines for feature requests

[davidjerleke]

Hi @productdevbook, thanks for opening this issue!

The request for "Support for LLM" is a bit broad—could you please clarify what you're looking for specifically? Are you referring to integration with a particular model or service, tools to work with LLM outputs, or something else entirely?

[productdevbook]

converting documentation to llms is like the link I gave in the example above. when we give it to ai, the library codes write beautifully.

[productdevbook]

https://svelte.dev/llms-full.txt expect us to publish it on the website.

example vitepress plugins. https://github.com/okineadev/vitepress-plugin-llms

[davidjerleke]

@productdevbook thank you for the help. I didn’t know this existed.

[productdevbook]

when you can offer this support ?

[davidjerleke]

Hi @productdevbook,
I can’t give a specific ETA at the moment, as this is an open-source project and development time is limited. Contributions or pull requests are always welcome in the meantime.

[davidjerleke]

@productdevbook — I’ll hold off on this for now.

From what I’ve seen, the llms-full.txt approach is still very much an informal convention rather than a standardized solution. A few points on the current status:

• It’s not widely adopted yet.
• There’s no formal specification or enforcement, unlike something like robots.txt.
• Its behavior and usage are mostly community-driven; LLMs may or may not respect it automatically.
• Variants like llms.txt or llms-full.txt are mostly conventions for sharing documentation with models, rather than standardized API integrations.

Because of this, it seems premature to build formal support in Embla Carousel. I’d rather focus on other features for now than spend time on something so experimental. Once and if the convention becomes more widely recognized, or there’s clearer guidance from the ecosystem, I’d be happy to revisit the feature request.