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.

Some context, I'm a consultant building programmatic SEO/AEO and content pipelines for client sites. I prefer Framer, but am hitting some blockers I don't have on Webflow (and have had some folks as me for that). I sync blog posts into the Framer CMS from markdown via the Server API (framer-api, addItems into a formattedText field). Getting content in works. But three things a human can do in the CMS editor are impossible once content arrives through the API. Edit entries after I push them. Managed-collection fields are read-only in the CMS UI. The userEditable option exists, but an editable field can no longer be written by the API, so there is no "API pushes, human edits after" mode. Update part of the body. formattedText is one write-only blob. To fix a single caption I re-push the entire article. For an automated pipeline that is real overhead, and in an LLM-driven workflow it also burns context re-sending content that did not change. I want partial body updates, targeting a block by a stable id, not replacing the whole field. Webflow lets me GET the body and PATCH it back; Framer's formattedText cannot be read back. Inline components and embeds. The editor can drop CMS Components and embeds into rich text. The API cannot. addItems has no way to carry either, so a synced pipeline is locked out of interactive widgets. Full parity would be a resolved FramerComponent tag in the body, as in Github framer/plugins issue #577. But even iframe-embed support alone would unblock most of this. Webflow already proves it works: its rich text API accepts embed blocks, so a pipeline can push a widget inline and have it render. Framer's formattedText drops anything that is not standard rich text. That first step alone would be a great unlock. Full workflow, for reference: https://www.signalroads.com/build-log/rock-content-pipeline

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

A

It'd be great to be able to upload both images and videos in one gallery. A nice feature would also be having these items clickable (either expand or redirected to a link). For example, I may want to upload short-form videos in a gallery and link them to their respective social media posts.

The CMS lets you sort collection items, but not group them. For large collections, this makes it hard to get a structured overview. Example: A “Blog Posts” collection with a “Category” option field. You can sort by date, but can’t group posts by category into distinct visual sections. Request: Add a “Group by” option in the CMS collection view. Selecting a field would organize items into collapsible groups with headers similar to Notion or Airtable.

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

Our goal is to set the communications team up so they can publish blogs and newsroom articles without the design team’s help. Because Framer pushes all page updates live at once, we need to be super coordinated to make sure in-progress work (outside of the CMS) does not accidentally get pushed live. If the CMS publishing was separate from the rest of the website, we would not need to worry about this.

Add an option to use whether a vector is set as a CMS condition, filter, or variable. Currently, this creates a lot of redundant manual toggles whose only purpose is to check whether an icon or vector has been added to a CMS item.