Help Center for LLMs
Folio publishes machine-readable copies of its entire Help Center so you can point any LLM at accurate, up-to-date documentation about Folio. No scraping, no stale snapshots, no guessing.
What is this?
Folio follows the llms.txt convention: a set of standardized URLs that publish a website's documentation as plain markdown so LLMs can consume it efficiently. Modern LLMs are very good at reading markdown but bad at navigating JavaScript-rendered marketing sites, so giving them the markdown directly produces faster, more accurate answers.
The files below regenerate on every site deploy — whatever you read in our docs is what an LLM will see.
URLs you can use
| URL | What it is | Best for |
|---|---|---|
foliosolutions.net/llms.txt | Index of every available page (marketing context + every Help Center page), grouped by section, with one-line descriptions. | Letting the LLM pick which pages to fetch as needed. |
foliosolutions.net/llms-full.txt | Every page (marketing + Help Center) concatenated into one file. | One-shot context for tools that prefer a single large file. |
foliosolutions.net/about/about-folio.md | Raw markdown of the marketing-context overview — positioning, products, use cases, features, comparison, pricing, FAQ. | Giving an LLM the "what is Folio and who is it for" pitch in one short file. |
foliosolutions.net/docs/<page>.md | Raw markdown of any single Help Center page (e.g. /docs/getting-started/installation.md). | Pulling one specific Help Center page into a chat. |
Use it with your LLM
Paste this into a new chat with ChatGPT, Claude, Gemini, or any assistant that can fetch a URL:
Read https://foliosolutions.net/llms.txt and use it as context for the rest of this conversation. When I ask about Folio, fetch any individual pages you need from the URLs in that file.
Swap in llms-full.txt when you'd rather hand over every page at once, or add either
URL as a knowledge source in tools that accept one.
Why this exists
We want LLMs to give accurate answers about Folio, not hallucinate based on stale or scraped content. Publishing our docs in this standardized format means any LLM-assisted user — an admin researching whether Folio fits their org, a developer integrating with the package, a sales prospect comparing options — can get straight to the source of truth.