I shouldn't matter. You should have the ability to build a tree structure with your groups or not. Most wikis allow you to choose to add a child/subordinate page or a peer/lateral page. Then people would have the option to build a tree structure for some groups and not for others.

I agree - this is essential. Can you name any non-hierarchical document management system?

this is a absolute requirement for any enterprise-class wiki product. the lack of this feature is one of the main reasons why wiki's have fallen out of favor with many enterprises. I whole heartedly agree with this feature request. If you are concerned about scalability of the navigation, just create a hierarchical tree at the left instead of tabs at the top.

I actually like the current design, where wiki pages can be assigned to a user or to a group. If you implement a tree structure, please keep the current set up as an option too.

Carlin, my company needs a folder for each of the fifty states; each folder has at least 4 wiki pages, some states have as many as 25. Yes, I can use the search function, but cannot see at a glance what i have and what I don;t have by way of wiki pages.

Look at pbworks, formerly pbwiki, which my company uses now, and i maintain it religiously - over 100 pages now. I am exploring cubetree only becaause pbworks does not have all the other social tools and functions that appear in cubetree. right now, I can't even find the cubetree wiki page I just created for crying out load.