All ideas

In some cases, you might want to make a new change in a language, like English and apply that to all locales using English. For example: en-US, en-CA, en-MX, etc. It would be nice to have something built in to easily port all those changes in a si...

Similar to how page targeting is done, it would be nice to be able to do this for a container element, like a box — container-based targeting . The use-case is that there could be certain content that's only meant to be shown in certain locales. F...

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.

Similar to a database, it would be nice to have a UUID field for CMS data models

It'd be really nice if I could quickly/easily expand and collapse all layers at once, especially if I working on a large complex document.

First, the Copy to a Different Space functionality is really nice to have so I don't have to download/upload JSON, but it'd be even BETTER, if it would either ask or automatically copy any associated Symbols too. I know that may be a huge lift, bu...

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