Feature Requests

I'd love for a slider, carousel or ticker component to be more dynamic with CMS content. At the moment they have to link to individual frames in order to create "slides", where I'd love for each slide to be an item in a Collection List from the CMS – this doesn't feel possible right now unless I'm missing something? This is so we could create dynamic carousels or slideshows from content in the CMS which can contain a variable amount of items in a collection list.

Ability to schedule a blog post or any other CMS content to only be published / taken off at a specific date

Nest CMS Blog Categories in a blog article URL /:category-slug/:blog-slug

With CMS databases, we would need Filters, sort and search to open up. If these are opened up as a base CMS component, it will help in not rebuilding it every single time. Attached some examples of basic and advanced filters that would be good to explore for components.

It would be extremely useful to have computed (formula-based) CMS columns that can be derived from existing fields within a collection. These columns would allow creators to define simple operations or functions on existing CMS data, without having to manually duplicate or update values. Examples • String operations If a collection has First Name and Last Name fields, creators should be able to define a Full Name field that automatically combines them (e.g. First Name + " " + Last Name). • Date calculations If a collection includes an Opening Date, creators should be able to generate a computed field like Days Since Opening, which dynamically calculates the number of days between the Opening Date and the current date. Why this matters • Reduces manual data entry and maintenance • Keeps CMS data consistent and single-source-of-truth • Enables more dynamic layouts, sorting, filtering, and conditional logic • Removes the need for workarounds using external tools or duplicated fields This would bring Framer’s CMS closer to a lightweight data model, unlocking more powerful use cases while keeping the system intuitive and no-code friendly.

Ability to publish specific CMS items and standalone pages (instead of the whole site), as well as scheduling deploys for a later date.

The updatedAt timestamp exists internally but isn't accessible via exports or the Plugin API. This prevents users from: Generating accurate sitemaps with last-modified dates Detecting which items changed since last sync Building efficient two-way integrations with external systems Request: Make updatedAt available as a read-only field in exports and getItems() . Use case: Users syncing Framer CMS with external applications need to know when items were last modified to avoid re-processing all data on every sync and to maintain accurate sitemaps.

Currently, CMS items rendered in a list cannot communicate with each other or detect outside clicks. This prevents common interaction patterns like automatically closing the open item when another one is clicked, or closing the active item when clicking outside of it. Use case: Portfolio company list (or FAQs, team members, etc.) where each CMS item can expand to show details. Users expect the previously opened item to automatically close, similar to an overlay behavior. Current limitation: Each CMS item is rendered independently, making it impossible to coordinate these interactions without detaching from CMS and manually rebuilding within a component with variants. Desired solution: Allow CMS items to have item-level interactions that can respond to clicks outside themselves and coordinate with other items in the same list, without losing the benefits of CMS-driven content.

I’m running into a CMS limitation when trying to show related content on CMS detail pages. Example: An "Activities" CMS collection with CMS detail pages A separate Reviews CMS collection Editors should be able to manage reviews in CMS and decide per "activity" which reviews appear Currently: Multi-reference fields can’t be rendered as CMS lists CMS template filters are static and can’t change based on the current CMS item Because of this, common patterns like reviews, testimonials, or related content per page require schema workarounds or code. Feature request: Support rendering multi-reference fields as CMS lists, or allow CMS list filters to reference the current CMS item. This would unlock many standard CMS use cases (reviews, testimonials, related posts) in a clean, no-code way. Thanks!

The ability to add iframes/embeds directly in the Formatted Text field of the CMS. Giving more control over adding things like Figma prototypes, etc