A CMS should ideally provide three main functions for me.
- Store and retrieve information in a flexible manner.
- Ability to create a heirachical site structure for this information.
- Intelligent menu that stays "active" correctly in different sections.
Flexinode combined with taxonomy appears to fulfill the first request brilliantly.
My second request for a heirachy is currently partly possible. If I store my information as flexinodes (for the enormous flexibility it brings), I can of course create a structure for them by linking them to a menu, but it would also be nice to be able to link flexinodes as part of a book structure ... I don't think this is possible at the moment?
My third request of a menu that functions (stays "active") correctly, is fulfilled to an extent by the menu module. However, if I view a node that is not linked to any menu, then of course my menu fails to work (that is, to stay "active"). This is only possible at the moment manually through a php script that creates a menu by checking the url (that is, an aliased url) ... thus my script might say, if the url is "/biography/" then keep the "biography" tab active ... I can then view an unlinked node with a url containing "biography" and know that the tab will correctly display as active).
I think a properly functioning menu makes navigating a site far easier, especially for new visitors. It can be quite disconcerting for some people to visit, say, a forum, where as soon as they click on a post, the forum tab becomes inactive (Drupal.org avoids this problem by simply having tabs that are never "active", which in my opinion makes the tabs far less useful).