All ideas

I would like to be able to target on a component level instead of on a page level. This would give a lot more flexibility without having to maintain two, almost identical, pages. For example, if we apply translation for most of a page, but a speci...

When you click 'back' you go back only one step rather than totally back to the beginning of what you're doing. Eg in the folders, going back to the folder you're working on rather than back to the parent folders.

I think having a color field as the setting of environments and displaying it consistently as a small top bar or something else could really help avoiding human mistakes. It eliminates a mental load of being constantly aware of which env I am in a...

We have a section model called Product Details Tab which is conditionally rendered by the ProductType we pass to the Section Model. Given that there are multiple product types, the Content Entries List has gotten a little cluttered. It appears the...

You have to be kidding me. Stop making people pay for support. Just stop doing it.

When publishing, giving the user the ability to add a note to say what changes have been made (like a commit message) to easily see what changes someone made during a publish. ex. changed url from /test to /test1

Currently markdown tables renders as string. Please add support of markdown tables.

Currently when setting targeting, you can only target with an AND operator, it would be nice to allow for OR...some users need to target sections or promotions to multiple pages and it would be easier to not have to create duplicates for each URL ...

Currently when you create a model and add a list item you can name the list item with some name that will be applied to each item: adding a list named groups with a list items group will name each one group 1, group 2, group 3. It would be useful ...