All ideas

When publishing a content, the author should be automatically assigned and the author details can be accessed on Content API.

It would be nice to be able to replicate database transactions with the write API, so that if a single action like updating a CMS data model fails, everything in the transaction will automatically rollback. This would prevent having to do manual c...

When connecting Data from Builder CMS Data Models (using Connect Data in the Data tab in the Visual Editor), the names are automatically generated using the name of the Data Model and then appending an incrementing digit (i.e. Pricing, Pricing 1, ...

Would be nice to have a way to setup colors to be used in Builder Editor, from the application code. Like we register Custom Components to be used, we should be able to setup Custom Colors in the same way. This would enforce usage of pre-defined c...

It would be nice for Builder to support GraphQL mutations for the write API, for instance.

Content Federation is a concept that marries multiple distinct APIs without having to duplicate the content. This would nice to be built into Builder.

It would be nice to have the ability to do complex relationships, which exist in ORMs, such as: One-to-one One-to-Many Many-to-Many One-Way Many-way Polymorphic Inverse

This is potentially an edge case, but I just had a need for it arise, so I thought I'd submit it. What I'd like to see is the ability to exclude targeting parameters like URL Path. Example: I have a Section (an Announcement Bar) that I'd like to s...

Sometimes you dont want to create a new Component or override and existing one, you only want to add some addtional styles to the "Basic Components" for example, you could add a margin-bottom: ... to the "Text Component"

You can use ref.ref inside content JS when using the React SDK to reference the DOM element for the content item, but this feature isn't provided for the other SDKs. This is a very useful feature when you want to manipulate the DOM for just the co...