Documenting Projects in Confluence

Within our organisation we could be running 65 projects or more at one time. Each project should contain their own decision logs, sprints, meeting notes, project scope, action logs, support document, etc...

Is it best to create a space for each project or is it better to list every project into a single space?

If we are to list every project into a single space I can see this quickly getting out of hand if our teams want to start giving their documents the same title. I can also see decision logs and meeting notes conflicting with each other. At the same time if we are to create a space for each project, this will overload our system with more spaces.

What do you think is the best solution?

2 comments

I'd recommend a space per project.

The number of pages will be the same, so we are only talking about the number of first level entry points to the wiki. You can label spaces to organize them and you could add additional pages as entry points for different audiences.

Spaces are handy if you for instance need to archive them, limit searches, or add access rights.

I agree with Robert, a space per project is most manageable.  Your users will understand it, as the concept is intuitive and enables them to think and see things in terms of "this project".  They're natural containers for projects in most cases.

I would not wory about having too many spaces.  Confluence handles it fine, as do users.  I've seen well performing Confluence systems which work great for the users with thousands of project spaces and then hundreds more spaces for non-project stuff. 

I've found that smaller projects are burdensome to require their individual Space.  It gives people far too many places to look to find information.  We've found a balance between project size and Confluence Spaces.  Thus, if I was managing 65 projects, perhaps only 30 would have their own space while the other 35 "small" projects would be under a more generic, category-driven, or team-centric Spaces.

In my opinion, if you create unnecessary spaces, it becomes harder to manage everything. If you use macros you will be able to create a friendly interface for your users. I think the only problem wih Confluence when building large projects is the menu. To compensate for the shortcomings of the navigation capabilities provided by confluence you could by a macro menu, but it can get expensive if you have a large group (each seat pays the fee). On the other hand, if you decide to do it in CSS you might run into other problems, such as security.

Comment

Log in or Join to comment
Community showcase
Bridget Sauer
Published Jan 29, 2018 in Confluence

Showcase: How LinkedIn does Content Lifecycle Management (12 Steps)

LinkedIn, the world's largest business network has an exceptionally large Confluence instance. In their case, large means millions of pages and thousands of spaces. In this Showcase, we're focusing i...

890 views 0 12
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot