Hi,
OK, this i think is a biggy in architectural terms, but here goes.

I think that it would be beneficial of the 'menu item' aspects of a document where thought of as an attribute of a document rather than a special type of document.

Why? Because i want to place documents like products, articles, clietns directly in the tree, and classify them as menu items, together with the page template used to render them and whether they appear in the navigation, site map etc.

This way, you don't have to add a Page (Menu Item) and then add a special documetn underneath which is then 'used' by the containing page to render it's content. This is not ideal as there are 2 content entities going through workflow, when really, the user only needs one.

This problem i believe led to the concept of editable regions, but although that feature saves a lot of time for unstructured content, it doesn't affect when you want to display hierarhical structued documents.

So, i am suggesting getting rid of the the cms.menuitem and allowing all documents to be menu items. This would do away with the concept of editable regions, and instead allow users to simply add documents to the tree.

A page template (and other properties) would be specified for any document that wanted to be a menu item.

Any documents in the tree which have been marked as menu items (whatever their type) could get a special little symbol or colour so you could clearly see which documents were participating in the site structure.

Furthermore, allowing all documetns the right to be a menu item means that ordering and display of tree menus becomes less restrictive, where currently to retain order you really can only use Page (Menu Item) document types.

I have to say i love Kentico, and hope to see this suggestion taken forward, although i can see it might be a fairly big change.