Degraded performance Customers may experience issues using Community search. Our team is investigating.
So, I am trying to work out how best to structure content in Confluence and if we need to start splitting things out more.
In the current & original structure we have created a team space for the IT Infrastructre Department, which contains all documentation for all Infrastructure related systems, project docs, KB articles and how to guides.
This seemed to work well for a while and originally made sense.
I am now wondering if we should be making better use of the spaces and move differnt systems to their own space. For example, have seperate spaces for VMware, SCCM, Exchange etc. and then general team space for generic KBs, how to guides etc.
The thinking would be if we had a project to move to Office 365, we would create a project space for that, which would then grow to contain tech documentation about design, how technical how-to guides and other Office 365 specific info.
How does everyone else structure their spaces?
Do you just dump most things in one based on team?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...
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!
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