Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Refactor the builder to emit llms-full.txt in upstream's per-page format:
# <title>
Source: <url> # no .md suffix
<blank lines> # 3 for MDX pages, 1 for OpenAPI ops
<body>
<blank lines> # 2 before the next page
OpenAPI operations now carry a synthesized metadata line
(`<spec> <method> <api-path>`) followed by the description, matching
how Mintlify renders spec-driven pages. `expandOpenApi` now returns
the method and API path alongside the existing fields.
Apply the high-frequency content transforms Mintlify does at build
time so MDX bodies look closer to the published markdown:
- bullet `- ` → `* `
- horizontal rule `---` → `***`
- code fence ``` ```lang ``` → ``` ```lang theme={"system"} ```
- internal links `/foo` → `/docs/foo`
- link-URL `\&` → `&`
- trailing whitespace trimmed on every line
Known divergences from upstream llms-full.txt (~53K of 87K lines):
- JSX component children (`<Tabs>`, `<Tab>`, `<Accordion>`, `<Steps>`)
are re-indented by 4 spaces per nesting level in upstream. We emit
them verbatim from the source MDX, because correct re-indentation
requires a real MDX/JSX parser (remark-mdx + remark-stringify with
component-aware rules).
- Markdown tables are column-padded in upstream so cell boundaries
align vertically. We emit tables verbatim.
- Some `<img>` tags get `src=` attributes injected from external data
(e.g. shields.io badge URLs). We can't reproduce these without
Mintlify's component resolution data.
- Blank-line spacing around components occasionally differs because
of the above re-indentation pass.
llms.txt remains byte-identical to upstream. Closing the llms-full.txt
gap fully would require implementing a Mintlify-compatible MDX
serializer; tracked as future work.
enesakar
approved these changes
May 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.