Draft Pages, CMS Pages, and Locales — lesson cover image

This lesson was released before Agents, Branching, and the CMS update on June 16, 2026. Some UI may differ, but the core concepts still apply.

Benjamin

1:44

Use Draft Pages, CMS Pages, and locales in Framer

Learn how to use Draft Pages, CMS Pages, and locales in Framer. Drafts are helpful for working on Pages that should not be published immediately. You will work with CMS fields, collection items, or collection lists while keeping the content editable in Framer.

Lesson details

Use Draft Pages for work that should stay out of the published site, CMS Pages for layouts driven by collection items, and locale versions for translated content. Choose the page type based on how the URL and content should be created rather than how the page looks.

Check the path, publishing state, and locale before sharing a preview. A draft can still contain sensitive work, and a CMS layout change can affect every item that uses the same detail page.

Check the rendered list or detail page as well as the CMS table. A correct field value can still wrap, crop, or disappear when its binding meets the final layout.

Frequently asked questions
How do I use Draft Pages, CMS Pages, and locales in Framer?

Learn how to use Draft Pages, CMS Pages, and locales in Framer. Drafts are helpful for working on Pages that should not be published immediately. You will work with CMS fields, collection items, or collection lists while keeping the content editable in Framer.

What does this lesson cover?

The lesson covers the settings and steps used to use Draft Pages, CMS Pages, and locales in Framer. See Page, CMS & Locale Drafts. Follow the demonstrated order in your project and review each change on the canvas before moving to the next step.

Does this workflow keep CMS content editable?

Yes. The workflow uses Framer CMS fields, items, references, or collection lists rather than flattening the content into a static page. Review the field mapping and each affected item after the change so editors can keep managing the content from the CMS.

Will CMS changes update collection pages?

CMS-backed collection lists and detail pages use the values stored in their connected fields. A field or item change can therefore appear wherever that content is bound. Review the list page, detail page, references, filters, and empty states after completing the workflow.

What should I review after I use Draft Pages, CMS Pages, and locales in Framer?

Review the exact pages and elements changed by the workflow. Confirm that copy, links, accessibility, responsive behavior, and interaction states still work as intended. Use preview for the final check and keep publishing separate from editing so you can fix problems before visitors see the update.