Serve llms.txt at the site root
@phmatray is already working on this.
Since Sep 10, 2026.
Assessment
This issue has not been assessed yet.
Description
Problem
https://docs.fallout.build/llms.txt returns 404. An LLM answering a question about Fallout has to crawl the rendered site and spend most of its tokens on navigation chrome, or fall back on what it learned about NUKE and get the namespaces and the tool name wrong.
llms.txt is the convention that fixes this: one markdown file at the site root, listing every page with a one-line description.
Outcome
https://docs.fallout.build/llms.txt serves the generated index.
The file itself is already generated in the content repo. Fallout-build/Fallout#660 adds a GenerateLlmsTxt target that builds docs/llms.txt from the frontmatter of docs/website/, commits it, and gates it in CI so a page added without regenerating fails the build. That half is in Fallout-build/Fallout#661.
This repo only has to serve it. static/ is already served at the root here (/img/social-card.png resolves), so the whole change is getting docs/llms.txt from the content repo into static/llms.txt during the site build.
Acceptance criteria
-
curl https://docs.fallout.build/llms.txtreturns 200 with the file's content. - The served file matches
docs/llms.txtin Fallout-build/Fallout at the commit the site was built from. Copy it during the build rather than committing a second copy here, so the two cannot drift. - It is served as
text/plainortext/markdown, not downloaded as an attachment.
Notes
Neither half is user-visible alone: this repo without Fallout-build/Fallout#661 has nothing to serve, and Fallout-build/Fallout#661 without this repo generates a file nobody can fetch.
llms-full.txt (the whole corpus inlined rather than linked) is a deliberate non-goal for now. Worth doing later, and it is a different file with a different size budget.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Fallout-build/docs.fallout.build
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in Fallout-build/docs.fallout.build
Similar issues
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
github/docs#46222 · 1 comment ·
Maintainers usually reply within 1 day
-
agent-ready area: config area: skills type: chore upstream: brain-kit
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
enhancement priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
bug escritorio mapa
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
marcosferr/reporte-ciudadano#4 · 1 comment ·
-
area: material/sort gemini-triaged needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
angular/components#33933 ·
Maintainers usually reply within 1 day