uPortal Confluence Spaces Requirements
Needs and Goals
Content we need to organize in spaces
What sort of content does uPortal need to organize into Confluence spaces?
Goals of doing that organizing
What are we looking to accomplish with our uPortal-related Confluence spaces? What would make this organization a success? What desired outcome are we looking to bring about?
Technologies, tools, and approaches
What can we bring to bear on this problem?
Confluence Spaces
Separation of Confluence spaces provides:
- Ability to define a different look/skin/theme per space
- Namespacing – pages can have the same name in separate spaces
- Scoping – Spaces can have different permission and can be watched at the space granularity
- Navigation generation – spaces feel somewhat separate, have their own tables of content, have their own metadata and space browsing
One approach we can bring to bear on our Confluence-hosted content organization problem is to organize pages into spaces to take advantage of these features.