feat: llms.txt should include full page content, not just TOC
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
Research direction
Start with src/server/routes/llms.txt.ts and src/lib/llms.ts, then compare get-llm-text.ts and [...slug].md.ts to understand how processed page content is obtained. Verify that /llms.txt includes titles, descriptions, and URLs, while /llms-full.txt includes all page content and individual .md routes remain working.
Written by the indexing model from the issue text.
Description
Problem
`src/server/routes/llms.txt.ts` and `src/lib/llms.ts` currently generate a table-of-contents-style output with just titles and URLs. The actual page content is not included, making the `llms.txt` output insufficient for LLM consumption.
`get-llm-text.ts` does fetch processed page content for individual pages, but the index route only lists titles.
Expected Behavior
The `llms.txt` endpoint should follow the emerging `llms.txt` convention:
- `/llms.txt` — index with titles, descriptions, and URLs
- `/llms-full.txt` — full content dump of all pages (for smaller sites)
- Individual page `.md` routes already work via `[...slug].md.ts`
The index should at minimum include page descriptions alongside titles.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 5h 16m
- Merged PRs (30d)
- 10
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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 raystack/chronicle
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
All issues in raystack/chronicle
Similar issues
-
area/core status/need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
google-gemini/gemini-cli#29602 ·
Maintainers usually reply within 1 day
-
area: backend enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
snapotter-hq/SnapOtter#1879 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Tencent/BrowserSkill#390 ·
Maintainers usually reply within 1 day
-
good first issue status: needs triaging type: bug version: 2.0
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
medusajs/medusa#17094 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day