Repository navigation
docs: publish domain llms.txt files for agents crawling the site - #675
Merged
Merged
Conversation
Give each extension surface its own text file and point llms.txt at that map so an agent loads one product area.
bcantoni
approved these changes
Nov 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
llms-*.txtfile per extension surface during the docs build, and replacellms.txtwith a map of those files so an agent loads a single product area.llms-full.txtstays generated and unlinked. Workspace extensions are omitted because this site has nodocs/workspaceextpages.Test plan
yarn buildsucceeds with the frozen lockfilellms.txtand confirm it lists Data Apps, Dashboard Extensions, Viz Extensions, Core, Extension Fundamentals, Design Guidelines, and Referencellms-workspaceext.txtis absent