freeCodeCamp/devdocs

llms.txt end points for each doc route

Open

#2,520 opened on Jun 6, 2025

View on GitHub
 (0 comments) (2 reactions) (0 assignees)Ruby (2,598 forks)batch import
featurehelp wanted

Repository metrics

Stars
 (38,907 stars)
PR merge metrics
 (Avg merge 30d 13h) (8 merged PRs in 30d)

Description

Feature request

It would be great with all the lllm / context related type things going on if each route for a document would also expose a /llms.txt equiv route.

Summary

Can we implement llmstxt endpoints for documentation. here is a link to an example and further explanation of what llmstxt is https://llmstxt.org/

Examples

https://context7.com/openai/openai-agents-python/llms.txt

Contributor guide

Research direction
Examine how routes are defined in the app (likely in app.rb or similar). Look at an existing doc route to understand how parameters are handled. Then implement a new route that responds to /llms.txt (or similar) for each documentation set. The content should follow the llmstxt format as described at llmstxt.org. Ensure the route returns a text/plain content type.
Tech stack
ruby
Domain
documentationbackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Ruby basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80