Folio Help Center for LLMs

Folio publishes machine-readable copies of its entire Help Center so you can point any LLM — ChatGPT, Claude, Gemini, Cursor, your own internal assistant — 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/start-here.md`).	Pulling one specific Help Center page into a chat.

Use it with your LLM

ChatGPT, Claude, Gemini, or any chat assistant

Paste this prompt into a new chat:

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.

For tasks that need a lot of Folio context up front (writing detailed implementation guides, comparing features, etc.), use llms-full.txt instead so the assistant has every page at once:

Read https://foliosolutions.net/llms-full.txt — this is the complete Folio documentation. Answer my questions about Folio using only what's in there.

Claude Projects, ChatGPT Custom GPTs, or other "knowledge base" features

Add https://foliosolutions.net/llms-full.txt as a knowledge source. Most knowledge-base UIs accept either a URL or a downloaded copy of the file. Re-fetching the URL periodically (or on every project update) keeps the knowledge current.

Cursor, Windsurf, or other AI-native dev tools

Reference the URL inline using your tool's URL syntax. In Cursor:

@https://foliosolutions.net/llms-full.txt

For a single page (for example, when working on something Folio-Docs-specific):

@https://foliosolutions.net/docs/user-guide/document-editor.md

Building your own AI agent or integration

Fetch /llms.txt first to get the page index, then fetch individual .md URLs as needed. Both files are served as plain text with the appropriate content-type headers, so a simple HTTP GET is all you need.

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.

Always current

These files are generated automatically on every site deploy from the same markdown that powers the human-readable Help Center. There is no separate copy to keep in sync — if a page is in the docs, it's in llms.txt within minutes of publish.

Questions?

Email hello@foliosolutions.net if your tool needs a different format, an additional endpoint, or has trouble fetching these URLs.