Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Best practices for using Spaces VS Pages in Confluence?

Hi,

We're in the process of setting up an information structure in Confluence and have read about spaces, pages etc. I can see that in Atlassian's own Confluence they have a space directory with all product spaces and inside each of those a space for each version of a product.

http://confluence.atlassian.com/spacedirectory/view.action

Things that we realized were:

Option A (like they have it) - one space per product
Advantages
x RSS-feed is per space it seems (meaning one could sign up for only those products one is interested in)
x Can name a Page the same as in another Space (since the Page name is unique within a space)

Option B - one space for all products
Advantages
x The tree structure on the left is better - you can see all the products in the same tree, whereas in option A you of course only get one product's info in the tree since the tree seem to be space based

Are there any recommendations on what else to consider? How do you sort your information? I know labels can do a good job there but it seems it would be a good idea to decide beforehand what spaces structure to use.

2 answers

We designed our space (similar to Option A) so that different groups of people can find their relevant topics all in one space. For example we have RCP projects and Portal projects which have (uncreative named) spaces "Rich Client Platfrom" and "Portal". Their only real intersection is managed in the infrastructure, which has a seperate space.

This way people can skim through their own topics without finding lots of other stuff they don't need for their work and without hiding all but "their" topics, getting a tree for stuff they really use.

But it really depends on the amount of projects you have, the amount of people using Confluence and so on. It's just what seems to work fine for us.

This may come a little late, but we're hosting a webinar on how to create a sound information architecture in Confluence on December 9th 2014. You can read more and register here: http://bit.ly/11udV5U

This comes a bit late too... Are you still hosting information architecture webinars? Thanks, Maggie!

Oh boy, how I needed that webinar :.(

I think this may be it https://www.youtube.com/watch?v=pQ3zYH0LPNo

Brikit Webinar - Creating a Sound Information Architecture in Confluence 9 Dec 2014

Thanks for posting this, @Terry Wright

For those who are interested, here is a newer recording with additional insights about organizing content in Confluence: https://youtu.be/5iLmqdxzz3k

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence

Announcing Team Calendars in Confluence Data Center

Hi Community! We're thrilled to share that Team Calendars for Confluence is now a built-in feature for Confluence Data Center releases 7.11 and beyond.  A long time favorite,  Team Cale...

156 views 0 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you