docs: improve LLM discovery surfaces - #57280
Conversation
Related to the llms.txt discovery lineage: merged #18276 already publishes |
teknium1
left a comment
There was a problem hiding this comment.
Thanks for improving discovery surfaces. Current main already publishes generated llms.txt and llms-full.txt at both the root and /docs/ via .github/workflows/deploy-site.yml:164-173, and documents those root URLs in website/docs/index.mdx:134-141.
Problems
- The new
llms.txt:35says the live site mirrors that file, but deployment copies the generatedwebsite/build/llms.txt; the generator owns that content inwebsite/scripts/generate-llms-txt.py:197-232. This creates a second independently maintained index and makes the stated mirroring relationship incorrect. The existing member comment correctly flagged this drift risk.
Suggested changes
- Rework the repo-root and deployed indexes to use one canonical source, or make the repository-root file an explicit pointer rather than a competing curated copy.
- Salvage the robots/sitemap and README work only after reconciling with the root LLM publication already on main.
Automated hermes-sweeper review.
| - Supports 20+ messaging platforms and agent tooling integrations | ||
|
|
||
| ## Agent-friendly docs | ||
| - The live site mirrors this file at the root and under `/docs/` |
There was a problem hiding this comment.
The deploy workflow copies generated website/build/llms.txt, not this independently maintained root file (.github/workflows/deploy-site.yml:164-173). Please make one source canonical or change this statement; otherwise the two indexes can drift immediately.
Summary
llms.txtfor GitHub/raw and agent discoveryllms.txt,llms-full.txt,robots.txt, andsitemap.xmlat the site root on deployVerification
npm ciandnpm run buildinwebsite/successfullyNotes