Menu system

I have seen the menu/article/category/map-search-view system.
It's awsome! It rocks!
Things like this only happens when analysis digs deep enough to se the
abstract nature of data that rules underneath the specific article token,  a
token which so often confuse the mysterious "average user", and maybe even
more so the no less mysterious "average client". This client - whom I often
meet in the communication process when specifying needs and "wishlist
items" - often has one wishlist item which I would like to mention right
here. It's a specific type of menu!

AND NOW presenting the dhtml menu type:

This is the infamous nested pull-down-out layered menu coded in javascript
and css.

Will we ever have such a thing in this system?

When I consult with clients they want to make decisions about things they
think they understand. Menus is such a thing. Often they do not understand
the flexibility of the category system they get in a certain content
management system.Often they do not really appreciate the workflow - because
it's not hardcoded to reflect the workflow in their organisation.
But a menu! That is something they all feel they can have an opinion about.
And what's more: Most clients do not really understand that colour-palette
and width and height of areas on the screen - are easier to ajust than it is
to put in a whole different menu.
That's why I now try to have a "spare" menu design in my pocket, so that the
client can choose between more than one. Actually I decided to do this after
a client complained that they were told they had freedom of design, but when
it came to the menu - they only had one menu to choose between.
In order to retain this client I had to have a new menu system coded for the
CMS system. Not the way to make a profit.

Over and out

Gunnar