All ideas

Customers often leverage section models to schedule content to publish to their site at a later date. However, when a customer needs to make a scheduled update to said content entry (ex. they want to change a few words in 24 hours) - the content r...

We frequently get requests for PR-like workflows (someone suggests a change, and someone else approves before publishing) Right now custom roles can be used for this use case, but a more first class feature flow could be very useful

We want to make it easy for our CMS users to follow their own design system - which exists in both outside and inside the scope of Builder - but without completely constraining them to it. Our clients have complex design systems with needs that ar...

You should be able to see a list of pages that currently have an instance of a symbol. The list would be links that will take you to the Visual Editor page for the page/model/section that is using the symbol, and navigate to where the symbol is pl...

In order to use the React component Builder Blocks more consistently and predictably in different contexts – especially styling, it would be useful to have the option to render it without the unavoidable span/div that it uses to wrap its child ele...

Currently styles are inherited from the desktop view. Some designers prefer to start building with a mobile view first so it would be nice to have the option for style inheritance to go the reverse direction - tablet and desktop inheriting from mo...

It would be great in the Content API, to be able to get the total amount of items in the return of the getAll method. That would allow us to be able to display a very common pagination pattern with numbered pages. At the moment, we do not know if ...

When looking at the Entries tab (content model and its associated entries), it's hard to decipher quickly what entry my team was last working on (if there isn't a set naming convention with a date, for ex). Today we can click into each entry and r...

The ability to collapse all layers to get a better understanding of the whole hierarchy. Similar to how VS Code allows for tree collapsing.

People schedule content and then assume when it'll go live it'll trigger a Gatsby build, but it doesn't