> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/chord-oms/content-management-cms.md).

# Content Management (CMS)

## Content Management on Chord

Chord uses a headless CMS (Content Management System) as the "source of truth" for your Jamstack site. We provide your CMS with extendable content types for your goods only limited by your imagination. Chord automatically syncs information from your OMS to the CMS as you add and update products in your store.

The big advantage to this approach is that developers will mostly need to be aware of the CMS and its APIs when building and maintaining your site instead of gluing together sources like in other e-commerce platforms.

### Explore more about Content Management on Chord:

* [Content Models (Shopify customers)](/chord-oms/shopify/content-management-shopify-version/content-models-shopify-customers.md)
* [Editing a Product in Contentful](/chord-oms/content-management-cms/contentful-101/editing-a-product-in-contentful.md)
* [Transactional Emails Templates/Variables](/chord-oms/content-management-cms/transactional-emails-templates-variables.md)


---

# 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.chord.co/chord-oms/content-management-cms.md?ask=<question>&goal=<user_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.