> For the complete documentation index, see [llms.txt](https://docs.overflowcms.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overflowcms.com/overview.md). # Overview ## OverflowCMS Docs OverflowCMS stores your content in a dedicated database outside Webflow, and renders it into markup you design natively in the Webflow Designer. No item limits, no 100-item collection-list cap, no forced plan upgrade when a blog or directory grows past what Webflow's CMS can hold. This site covers the product as it exists today: what's shipped, what a plan actually includes, and the exact HTML/attributes the embed script reads.


	Quickstart	Sign up, create a site and collection, and get a list rendering in Webflow in one pass.
	Core concepts	Workspaces, sites, collections, items, fields — how they nest and what each one gates.
	Embed script basics	The data-oc-* attribute contract that binds your Webflow markup to published content.
	Editor guide	Collections and fields, drafts and publishing, team roles.
	Plans & billing	What Starter and Pro include, and how upgrades work.
	API Reference	The public JSON API and the full embed attribute reference.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.overflowcms.com/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

:bolt:

:diagram-project:

:code:

:pen:

:credit-card:

:plug: