# Framer adds a Content panel for rolling out locales in stages

> The November 2 update lets teams choose which pages, collections, and components to include, leave untranslated, or hide in each locale.

Canonical: https://stacktak.com/news/framer-localization-content-panel-opt-in
Author: Stacktak Editorial
Published: 2026-11-03T14:00:00Z
Modified: 2026-11-03T14:35:36Z

A new language version does not always need every page on its first day. Framer’s [November 2 localization update](https://www.framer.com/updates/localization-opt-in) adds a Content panel for deciding which parts of a site participate in each locale.

The panel brings pages, CMS collections, and components into one overview. Teams can include content, leave it untranslated, or hide it entirely. Preferences can apply to several items or across all locales, reducing the need to repeat the same content decision one item at a time.

## Start with the pages the team can support

When adding a locale, the team can choose whether to include all content by default or keep it untranslated. Framer’s example is a gradual launch: begin with the homepage and bring other pages into the localized experience later.

For a small editorial team, that could separate a translated product overview from a case-study archive that is still awaiting review. These are publishing-scope controls; the announcement does not establish the accuracy of any translation.

Before expanding a locale, check the actual visitor journey: the homepage, its navigation, and any linked CMS pages. A page-by-page rollout is useful when the included material forms a coherent route, with a clear decision about what remains visible while the rest is prepared.

## Source

[Framer — Localization Content Panel & Opt-In, November 2](https://www.framer.com/updates/localization-opt-in)