Possibility to create nodes within a content, but not displaid in the content tree (better a tab) : I have several projects where children nodes are related to the definition of it'sd parent (widgets, actions, ...), and not about content related to the parent node. It's annoying to get all those nodes and it's highly disturbing the end user, the editor, that is usually the customer that pays the bill :-)
Possibility to create custom tabs for a document type, with appropriate user controls to give higher user experience to edit content.
Possibility to add document types into a base content with a certain document type, to create a highly customizable content node => Related to layouts, widgets. For now using new layouts with new items needs a new document type, and most of the time, a delete, and reconstruction of your content.
Possibility to change a document type to another, even if we loose content (it's better then loosing content, children, and everything) -> especially if there is no warning when we delete a doctype, the minimal should not delete content and parents, but change it to the parent document type. This could heavily help developppers to win in some flexibility against the volatile minds of the customer :-)
Multiple sites, multiple domains, multiple languages, some cookie management to select the right branch, some relation management between pages of same language ?
My Wishlist!
is working on a reply...