Coming Soon Join the waitlist for 30% off your first year of Folio Docs

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. Large — chat tools with per-fetch limits may silently truncate it. One-shot context for tools that ingest whole files (Cursor, API calls, knowledge sources).
/llms-full-admin.txt
/llms-full-user-guide.txt
/llms-full-reference.txt
One section of the Help Center per file — Admin Setup, the End User Guide, or the Reference pages. Bulk context in a chat: each file fits under typical chat-tool fetch limits.
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 as an index of Folio's documentation, and fetch the pages you need from it as I ask questions. If your browsing tool refuses to fetch the .md URLs listed there, fetch https://foliosolutions.net/docs/llms instead โ€” the same index as an HTML page โ€” and follow its links.

For bulk context instead of page-by-page fetching, paste one of the section files — llms-full-admin.txt, llms-full-user-guide.txt, or llms-full-reference.txt. The complete llms-full.txt is best kept for tools that ingest whole files (Cursor, API calls, or a knowledge-source upload) — chat tools with per-fetch limits may silently truncate it.

Every page as markdown

Every Help Center page is linked below in its raw-markdown form — the same index as llms.txt, as real links. If you've pointed an LLM at this page, it can fetch any of these directly.

Admin Setup

End User Guide

Reference

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.