Planning OA hierarchy for project w/ 200+ Spaces

Events happening in the community are now at Drupal community events on www.drupal.org.
kevin p davison's picture

A well-known, "very" high-tech university is considering OA for its extranet knowledge-base. This decision came after looking at TWiki. What I'm attempting to plan for is how to manage UI for 200+ "Spaces," as OA provides. And also if this goes beyond what OA intends for. But I think it's rather ideal still. What do you think?

Perhaps my problem is only how to theme a useful search/menu method for Spaces, and helping users rely on subscriptions to narrow down spaces only they would be exposed to. However, that "All Spaces" view is going to be massive without clever UI. When I look at Wikipedia, "At present, the following 1123 portals exist. Of these, 163 are Featured portals." They have this concept of "Portals," and only feature 163, with a subset of those (12) on the Main page only.

And of course, hoping to use this project to help contribute back to OA. Thanks!

Comments

Hi Quevin! OA can definitely

TetraMiller's picture

Hi Quevin!

OA can definitely handle your need of 200+ spaces. Coming from the perspective of an individual user, they will only be able to view the spaces they've subscribed to within their menu. In addition, if they happen to subscribe to a large majority of the 200+ spaces, they can "favorite" the ones they use most often, which will show up to the left of their full subscription left in the menu bar. (There is also additional page listings of the spaces they are subscribed to or can subscribe to. Please reference the screenshots below for examples.)

Screenshot of an example space page
Screenshot of an example menu of spaces

I'd be happy to chat with you about how best to go about creating this hierarchy and seeing how you choose to handle the UI.

Open Atrium

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week