We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.
For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.
Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.
Enable drag and drop for PropertyList<T> in the editing experience
Would it be possible to enable drag & drop in the editing experience of property list similar to content areas. PropertyList are sometime favored in content type architecture as they take less editorial time to setup then blocks.
The CMS UI is mostly white, which can be straining on the eyes. I'm convinced that adding the option to switch to a dark themed interface would be greatly appreciated by a lot of users. The option could also be automatically configured based on br...
Title missing on images in the Text editing fields
The mouse-over titles are missing in images added in the Text editing fields. This is a normal feature on all CMS:s so it's strange that I can't see it. This would help me make more accessible web content.
Users would benefit from the ability to refresh their current view in the content tree without refreshing the browser.
Though we use sockets to provide some real-time communication, the content tree doesn't always reflect the most recent changes - particularly in folders in the asset pane or sub-items in the page tree.
To test, open two separate browsers and e...
Cludgy solution for finding content references (moving to trash)
If I want to find internal pages that link to a page, I usually click Move to Trash to get a list of internal references, and then Cancel. Grzegorz Wiecheć has made a nicer solution to this issue: https://gregwiechec.com/2015/06/displaying-related...
Improve possibilities to group larger quantities of items under the same node without affecting the URL segment
I want to be able to group content in "buckets" without affecting the URL. Container pages have been used, but this is not ideal since they add a URL segment and we want to try and avoid to remove this by tweaking into some central parts of routin...
Allow container pages that don't generate a URL segment
Some functionality cascades down the page tree, like approvals or permissions. Sometimes you want to group pages together so you can apply values and functionality to branches of pages, but these necessarily affects the URL, since any page generat...