Builder for Developers

By default, there is a master / main branch. A user can create a branch and can select a publish point in the history or just edit the current branch in the editor. During deployment, we can assign a specific branch. If a page does not have that b...

Currently, on CMS data model entries, you can only change the locale picker one field at a time. It would be useful to be able to change to locale for all fields, much like what exists on the drag-and-drop visual editor.

CMS data models are contained within spaces, which is normally a good thing. However, in some cases, it would be useful to share CMS data among spaces, globally available. This could especially be useful for companies to share data and translation...

For CMS data models, the option, "Make Content Entry Title", only works for strings. It would be nice if it could also work for number types as well.

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...

Although inheriting state by default can often make it difficult to debug in situations where there are modals, pop-ups, or web components being used, other customers would still find this beneficial and time-saving. Perhaps the option could be av...

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