Feature Requests

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.

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

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.

I want to be able to select multiple CSM items and bulk edit any of the fields. This would override any existing values in those fields

It would be great if the Notion plugin could sync with local CMS collections. This would make it much easier to keep content updated inside Framer without manual copying.

It would be very useful if CMS filters could be applied based on the current date. For example, if I've got a Collection that contains upcoming events, I'd like to filter the list so that old events that have already happened are no longer displayed. Currently it's possible to set a filter based on the date, but the date value is static—meaning I'd have to come in every day and manually update it to the current date in order to hide old events. It would be awesome if the date could be set dynamically to "today" or "current date" to make this filtering automatic.

Currently, you can only attach 1 link to an image in Google Sheets and have it synced with framer. Gallery functionality is not supported, Framer will throw an error if you insert >1 link in a cell. Please add a capability other than add gallery of images in CSV or EVEN BETTER, make it so I can add images inside Framer CMS AFTER sync is complete. (All text/numbers data handled via CSV and all images are handled in Framer interface).

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

Currently, Framer collections allow sorting Date fields using “New → Old” or “Old → New.” While this works for strict chronological ordering, it does not support one of the most common real-world needs when working with dates: displaying items in order of proximity to today. The problem “Old → New” sorts dates from earliest to latest. However, this is not the same as showing the date that is closest to the current moment. Example Today is December 2025. My collection includes upcoming dates in January 2026: 02/01/2026 10/01/2026 Sorting Old → New gives: 02/01/2026 10/01/2026 This appears correct until past dates are also present. Mixed past + future dates 10/12/2025 (past) 21/09/2025 (past) 02/01/2026 (future) 10/01/2026 (future) Sorting Old → New results in: 21/09/2025 10/12/2025 02/01/2026 10/01/2026 This is not suitable when the priority is to surface dates that are upcoming, nearest, or most relevant right now. Past dates will always appear before future dates unless manually filtered out, which adds unnecessary overhead for editors. This limitation applies across many contexts: scheduled updates, launch dates, deadlines, expirations, content rotations, time-bound offers, and any scenario where the next relevant date matters more than absolute chronological position. Why a “Soonest” sorting mode is needed A proximity-based “Soonest” sort would: Automatically prioritize the date closest to today Push past dates below upcoming ones Remain correct even if content editors enter items out of order Remove the need for helper fields (e.g., “isUpcoming”, “isExpired”) Align with how most systems handle time-sensitive or relevance-based ordering This is a very common pattern when working with dates, regardless of the domain. Proposed solution Introduce a new sort mode for Date fields: Sort → Soonest Sorts items based on proximity to the current date, so the next relevant date appears first. Possible enhancements: Option: Allow a custom reference date (default = today) This would make Framer collections significantly more flexible for any scenario involving time-based relevance. Conclusion Chronological sorting alone is not sufficient for many real-world workflows involving dates. A native “Soonest” sorting mode would provide a simple, intuitive way to surface the next relevant item without requiring code components or manual data handling. It would benefit a wide range of use cases where dates represent relevance, priority, or upcoming changes.