Skip to content

docs: add related-site and optional sections to llms.txt, dedupe developer docs - #511

Merged
Prashant-Surya merged 1 commit into
masterfrom
docs/llms-txt-sections
Aug 22, 2026
Merged

docs: add related-site and optional sections to llms.txt, dedupe developer docs#511
Prashant-Surya merged 1 commit into
masterfrom
docs/llms-txt-sections

Conversation

@vihar

@vihar vihar commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Summary

Item 4 from the is-agentic scan (independent of #508#510).

Problem. Each site's llms.txt only listed its own pages. An agent reading docs.plane.so got no pointer to the API reference, webhooks, MCP server, or self-hosting docs on developers.plane.so (and vice versa) — which is what the scan's Developer resource discoverability finding asks for ("list them in llms.txt"). The developer-docs file also listed 14 pages twice, and docs.plane.so didn't send the </llms.txt>; rel="describedby" Link header that developers.plane.so already does.

Change (both sites, consistent), checked against the llmstxt.org format (H1 + blockquote, H2 link sections, Optional, no duplicates, valid links):

  • customLLMsTxtTemplate — H1, blockquote, details, then H2 link sections:
    • ## Table of Contents — the generated sidebar index (unchanged)
    • ## Related documentation — the other Plane docs site's llms.txt plus its key entry pages (docs → API reference, webhooks, MCP server, self-hosting; developer docs → core concepts, quickstart, roles & permissions)
    • ## Optionalllms-full.txt, sitemap.xml, GitHub, plane.so (the spec's "skippable" section)
  • details now says every page is available as Markdown via .md or Accept: text/markdown.
  • developer-docs: the / sidebar only holds shortcut groups that repeat pages from the section sidebars; it's dropped from the llms.txt TOC via the plugin's sidebar hook, so every page appears exactly once (371 links / 357 unique → 365 / 365).
  • docs vercel.json: add </llms.txt>; rel="describedby"; type="text/plain" to the Link header (matches developer-docs).

Verification

  • pnpm check:types / check:format / pnpm build pass.
  • Generated dist/llms.txt on both sites: single blockquote, H2 sections Table of Contents | Related documentation | Optional, 0 duplicate URLs (137 links docs, 365 developer-docs).

Not changed — needs a content decision

developer-docs has an ### Other bucket at the end of the TOC for pages in no sidebar: api-reference/inbox-issue/* (looks like the pre-rename twin of api-reference/intake-issue/*, same six pages), api-reference/work-item-relations/*, and self-hosting/methods/one-click. They're live, indexable pages so I left them listed. If inbox-issue is legacy it should probably be redirected/removed, and the other two likely want sidebar entries — happy to do that as a separate PR.

Checklist

🤖 Generated with Claude Code

https://claude.ai/code/session_01CsPSwTnpsEb5c5Ud2CLrL8

@vercel

vercel Bot commented Aug 21, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
developer-docs Ready Ready Preview Aug 21, 2026 8:38pm
docs Ready Ready Preview Aug 21, 2026 8:38pm

Request Review

@coderabbitai

coderabbitai Bot commented Aug 21, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@vihar, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 17 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1a434f9f-cbd5-432d-a869-f25d987d1cc0

📥 Commits

Reviewing files that changed from the base of the PR and between aad24bb and f21372e.

📒 Files selected for processing (3)
  • apps/developer-docs/docs/.vitepress/config.mts
  • apps/docs/docs/.vitepress/config.ts
  • apps/docs/vercel.json

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

…loper docs

Both llms.txt files only listed their own site, so an agent reading
docs.plane.so had no pointer to the API reference, webhooks, MCP server or
self-hosting docs (and vice versa) — one of the is-agentic discoverability
findings. Following the llmstxt.org layout:

- custom template on both sites adds `## Related documentation` (the other
  Plane docs site's llms.txt plus its key entry pages) and `## Optional`
  (llms-full.txt, sitemap.xml, GitHub, plane.so)
- `details` now tells agents every page is available as Markdown via `.md`
  or `Accept: text/markdown`
- developer-docs: drop the "/" shortcut sidebar from the llms.txt table of
  contents — its four groups repeated 14 pages that the section sidebars
  already list, so every page now appears exactly once
- docs vercel.json: send the same `</llms.txt>; rel="describedby"` Link
  header that developer-docs already sends

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CsPSwTnpsEb5c5Ud2CLrL8
@Prashant-Surya
Prashant-Surya merged commit 0c20667 into master Aug 22, 2026
6 checks passed
@Prashant-Surya
Prashant-Surya deleted the docs/llms-txt-sections branch August 22, 2026 11:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants