Feature Requests

Ability to publish specific CMS items and standalone pages (instead of the whole site)

It would be super useful to have support for variables, similar to what Figma offers. Being able to attach specified values to things like padding, gap, or basically anywhere that allows a numerical input would enable a lot of systematic structure that's currently not natively possible. It could work similarly to how text style sizing works, where its possible to define a size based on the breakpoint. Variables could allow for a layer of abstraction in defining consistent system-wide values, such as "padding-large" being set to 128px on desktop and 64px on mobile, for example. This would make updating values across all pages much easier.

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.

Allow users to password protect individual pages, rather than entire sites.

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.

It would be very practical to be able to add negative gap. Now the number can be only positive. There are many use cases... for example a 2-line heading. Now I need to deal with text layer height.

Provide the ability to create ephemeral branching of both CMS content and canvas/component changes. Enable editors to work on site changes in isolated scopes to avoid accidentally merging changes and inadvertently deploying something in error. Extend this concept such that multiple staging ephemeral staging environments can co-exist. Introduce advanced publishing features more akin to pull request reviews, whereby it's clear to see the comparison of one environment to another and accept changes between them. Extend this functionality to the publish workflow so deployers have confidence in what changes they are deploying and, crucially, what they are not. Take the guesswork out of the most critical parts of the software development lifecycle.

Add gradients to the Styles in the Assets panel.

When we need to create responsive variants with some functionality, variant count goes out of hand since we need to recreate the functionality for each breakpoint. If there was a way to control breakpoints in components separately from functionality, we would would dramatically reduce the number of variants and it would be much easier to update the functionality later once instead of having to remember to update it for all other breakpoints.

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