{"section":"tutorials","requestedLocale":"en","requestedSlug":"cms-overview","locale":"en","slug":"cms-overview","path":"docs/en/tutorials/storefront/cms/cms-overview.md","branch":"main","content":"> The CMS is available for FastStore stores from v3 and above, and Headless Stores. If your store uses FastStore v1 or v2, refer to <a href=\"/en/docs/tutorials/headless-cms-overview\">Headless CMS (Legacy)</a>.\r\n\r\nThe Content Management System (CMS) provides merchants with the flexibility and control needed to manage and structure their storefront content independently. It allows business teams and content editors to create multiple versions of content, collaborate on details, review for quality, and schedule publishing. To access the CMS, open the VTEX Admin and go to **Storefront > Content > Content**.\r\n\r\n## Getting started\r\n\r\nEvery piece of content a shopper sees starts with a developer, who defines which fields can be edited, their types, and their names. Once the developer publishes that structure, content operators use the Admin to create, review, and publish pages based on it, without writing code.\r\n\r\n![cms-workflow-overview](https://vtexhelp.vtexassets.com/assets/docs/src/cms-workflow___1051ba6444b1b3aeaf5a5623620dc62f.png)\r\n\r\nBefore you begin, make sure you have:\r\n\r\n| Requirement | Description |\r\n| ----------- | ----------- |\r\n| A schema published by a developer | Without it, there are no fields to edit. Developers can find the setup steps in the Developer Portal guide [Getting started with CMS](https://developers.vtex.com/docs/guides/getting-started-with-cms). |\r\n| The right role | The CMS has three roles: Content Producer, Content Editor, and Content Administrator. See [CMS roles and permissions](/en/docs/tutorials/cms-roles-and-permissions). |\r\n| A configured store with a Preview URL | A store links your storefront to the CMS and holds its settings, including the locales and the Preview URL used to preview entries and branches before publishing. See [Configuring stores](/en/docs/tutorials/cms-configuring-stores). |\r\n\r\nAfter completing these requirements, follow these steps to start working with the CMS:\r\n\r\n1. **Configure your store.** Define the store name, the Preview URL, and the locales. Learn more in [Configuring stores](/en/docs/tutorials/cms-configuring-stores).\r\n2. **Create a branch and edit content.** Work in an isolated branch, preview your changes, and merge them into `main` now or on a scheduled date. Learn more in [Versions and branches](/en/docs/tutorials/managing-versions-and-branches) and [Collaboration workflows](/en/docs/tutorials/collaboration-workflows).\r\n3. **Restore earlier work if needed.** See [Version history](/en/docs/tutorials/cms-version-history).\r\n4. **Translate your content.** Set up locales and fallback behavior. Learn more in [Configuring locales](/en/docs/tutorials/configuring-locales), [Localizing content](/en/docs/tutorials/localizing-content), and [Understanding locale fallback rules](/en/docs/tutorials/understanding-locale-fallback-rules).\r\n\r\n> ℹ️ Developers can find the technical side of the CMS, such as environment setup and schema declarations, in the [Developer Portal](https://developers.vtex.com/docs/guides/getting-started-with-cms).\r\n\r\n## Main parts of the CMS\r\n\r\nBelow are the main parts of the CMS:\r\n\r\n## All content\r\n\r\n![cms-overview](https://vtexhelp.vtexassets.com/assets/docs/src/cms-overview___4da66fe4346083e5056bc43f9c49db1a.png)\r\n\r\n**All content** is the main dashboard of the Content Management system. It allows you to list and manage all the digital content of your store, including pages, layouts, templates, and global sections, within the VTEX Admin. This central hub aims to streamline the content creation, editing, and publishing process through a modular system with version control (branches).\r\n\r\n## Stores\r\n\r\n![cms-stores](https://vtexhelp.vtexassets.com/assets/docs/src/cms-stores___6a92351517b7672eb34b4427765cbd2e.png)\r\n\r\nThe Stores page displays each storefront linked to the account's CMS, allowing you to manage them. On the Stores page, you can:\r\n\r\n* View all stores for the account and see which storefronts they are connected to.  \r\n* Add new stores to link additional storefronts or projects to the CMS.  \r\n* Open a store's settings to manage its preview/build URLs, repository integration, and default and fallback locales for content delivery.\r\n\r\n## Branches\r\n\r\n![cms-branches](https://vtexhelp.vtexassets.com/assets/docs/src/cms-branches___d4cbb256190ee104d3794e2c812b4c8f.png)\r\n\r\nBranches provide a collaborative workspace where teams can work on content changes in an isolated environment before merging them into the Main branch and without impacting the live storefront.\r\n\r\nEach branch is an isolated version of your content, allowing multiple editors to create, update, and refine pages, layouts, and sections simultaneously. All changes are tracked per content item, making it easy to see who made the change, what was changed, and when.\r\n\r\nThe collaboration flow in a branch is:\r\n\r\n* **Edit:** Multiple editors work in the same branch, making content updates independently.  \r\n* **Track:** Every change is versioned, with clear visibility into who made each update and when.  \r\n* **Preview:** Teams preview unpublished changes in a storefront context to review and validate content.  \r\n* **Merge:** Once approved, the branch is merged into the Main branch, publishing all changes to the live store.\r\n\r\n## Media\r\n\r\n![cms-media](https://vtexhelp.vtexassets.com/assets/docs/src/cms-media___a1a25d3327a2cbebe9aa1f5effb84df7.png)\r\n\r\nMedia allows managing store media files, such as images and videos. For images, you can upload and organize files up to 5 MB in the following formats: PNG, JPG, GIF, SVG, and WebP. For videos, you can add a URL to an externally hosted video provider, such as YouTube.\r\n\r\nFor more details, see the [Media](https://newhelp.vtex.com/docs/tutorials/media-overview) guide."}