You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I'm trying to define the ideal structure for a Confluence space for a company's digital documentation. My objective is to have a clear structure where the team working into the space know where to put a page when they need to create one.
I realise this is an IA question as much as it is a Confluence question.
I keep coming back to this statement on the one of the Atlassian Wiki pages "The key is to think of a space as the container that holds all the important stuff a team, group, or project needs to work"
Ideally the structure could apply across multiple companies, although I appreciate a one size fits all won't work perfectly in reality (but even so, having a base to start from wouldn't be a bad thing).
Some assumptions to consider:
This is where I've landed with a space structure. Does anyone have any advice, criticisms or thoughts on this?
Thank you in advance for your help!
One thing to consider is that you cannot have two pages in one space with the same name. For instance, for your websites, you have a sub page called Technical documentation on each. That will have to change to Technical documentation 1, Technical documentation 2 or something similar.
I would probably split off each website and each project as separate spaces, and keep the rest in a general space.
Also consider using the app Space Tree Creator. That way you could set up template spaces for new websites and projects, and create news spaces using these templates with one click. You can add parameters as well, to automatically fill in relevant data upon creation. We use this to create new spaces for subsidiaries.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.