docs(sphinx-gp-llms): correct attribution — docs.json from Lakebed, llms community-established

tony · tony · commit cc9118ca5cdd · 2026-05-25T08:32:50.000-05:00
why: docs.json convention originates from Lakebed, not Mintlify.
Mintlify's docs.json is closer to a manifest.json (theme, nav,
rendering config), not a documentation metadata object. The llms.txt
and llms-full.txt conventions are community-established by now.

what:
- Drop Mintlify from llms-full.txt and .md twins adopter lists
  where Anthropic, Cloudflare, GitBook are more prominent
- Clarify Mintlify's docs.json as manifest.json-like in the
  docs.json note (README and index.md)
- Replace Mintlify with Anthropic in .md twins attribution
diff --git a/docs/packages/sphinx-gp-llms/how-to.md b/docs/packages/sphinx-gp-llms/how-to.md
@@ -37,7 +37,7 @@ the site's content:
 
 Concatenated full-content Markdown of every documentation page,
 following the community convention adopted by Anthropic, Cloudflare,
-Mintlify, and GitBook. Each page appears under a title header with
+and GitBook. Each page appears under a title header with
 a source URL, separated by `---` dividers. Source files are included
 as-is — MyST pages are already Markdown; RST pages are included
 verbatim.
@@ -57,7 +57,7 @@ machine consumption:
 ### Per-page `.md` twins
 
 Source file copies alongside each HTML page, following the
-"Markdown for Agents" convention (Cloudflare, Mintlify, Stripe,
+"Markdown for Agents" convention (Cloudflare, Stripe, Anthropic,
 Vercel). Every HTML page at `/path/page.html` gets a sibling at
 `/path/page.md` containing the original source content.
 
diff --git a/docs/packages/sphinx-gp-llms/index.md b/docs/packages/sphinx-gp-llms/index.md
@@ -44,10 +44,11 @@ fetch them in Markdown.  It carries `agentEntrypoints` (pointers to
 per-page `markdownUrl` and `headings[]`, and the project's
 `sourceRepository`.
 
-There is no published specification for this format.  The convention
-originates from [Lakebed](https://docs.lakebed.dev/)
+There is no published specification for this format.  We first noticed
+the convention at [Lakebed](https://docs.lakebed.dev/)
 (`github.com/pingdotgg/span`).  Other documentation platforms also
 emit a file named `docs.json`, but those are typically site-builder
 configuration files (theme colors, navigation structure) rather than
-agent-oriented manifests — Mintlify's `docs.json`, for example, is a
-rendering configuration schema, not a content discovery format.
+agent-oriented manifests — Mintlify's `docs.json`, for example, is
+closer to a `manifest.json` that controls theme, navigation, and
+rendering rather than describing documentation content for agents.
diff --git a/packages/sphinx-gp-llms/README.md b/packages/sphinx-gp-llms/README.md
@@ -58,13 +58,14 @@ fetch them in Markdown. It carries `agentEntrypoints` (pointers to
 per-page `markdownUrl` and `headings[]`, and the project's
 `sourceRepository`.
 
-There is no published specification for this format. The convention
-originates from [Lakebed](https://docs.lakebed.dev/)
+There is no published specification for this format. We first noticed
+the convention at [Lakebed](https://docs.lakebed.dev/)
 (`github.com/pingdotgg/span`). Other documentation platforms also
 emit a file named `docs.json`, but those are typically site-builder
 configuration files (theme colors, navigation structure) rather than
-agent-oriented manifests — Mintlify's `docs.json`, for example, is a
-rendering configuration schema, not a content discovery format.
+agent-oriented manifests — Mintlify's `docs.json`, for example, is
+closer to a `manifest.json` that controls theme, navigation, and
+rendering rather than describing documentation content for agents.
 
 ## See also
 
diff --git a/packages/sphinx-gp-llms/src/sphinx_gp_llms/__init__.py b/packages/sphinx-gp-llms/src/sphinx_gp_llms/__init__.py
@@ -3,7 +3,7 @@
 Generates ``llms.txt``, ``llms-full.txt``, ``docs.json``, and per-page
 ``.md`` twin files during the standard HTML build, following conventions
 established by llmstxt.org (Jeremy Howard / Answer.AI), Cloudflare
-("Markdown for Agents"), Mintlify, and Lakebed (Ping).
+("Markdown for Agents"), and Lakebed (Ping).
 
 The extension hooks into ``build-finished`` to write output files and
 ``html-page-context`` to inject footer link variables into the template
diff --git a/packages/sphinx-gp-llms/src/sphinx_gp_llms/_llms_full_txt.py b/packages/sphinx-gp-llms/src/sphinx_gp_llms/_llms_full_txt.py
@@ -1,6 +1,6 @@
 """Generate ``llms-full.txt`` — concatenated full-content Markdown.
 
-Community convention adopted by Anthropic, Cloudflare, Mintlify, and
+Community convention adopted by Anthropic, Cloudflare, and
 GitBook.  Each page's source content is included under a title header
 with a source URL reference, separated by ``---`` dividers.
 
diff --git a/packages/sphinx-gp-llms/src/sphinx_gp_llms/_md_twins.py b/packages/sphinx-gp-llms/src/sphinx_gp_llms/_md_twins.py
@@ -1,7 +1,7 @@
 """Generate per-page ``.md`` twin files alongside HTML output.
 
 Implements the per-page Markdown endpoint convention popularized by
-Mintlify, Cloudflare ("Markdown for Agents"), Stripe, and Vercel.
+Cloudflare ("Markdown for Agents"), Stripe, Anthropic, and Vercel.
 Each HTML page at ``/path/page.html`` gets a Markdown sibling at
 ``/path/page.md`` containing the original source content.
 
