Morning and happy new year everyone,
I thought I would create an article to share how I go about keeping the content published on our Confluence site organised and relevant. I appreciate this method might not work for everyone but I'm hoping it will help some of you who are just starting out using the application.
Since using this practice we have saved money buying 3rd party tools and archived over 8,000+ pages since 2019. We have also reduced a lot of frustration by making it easier for people to locate content.
We have 1,800+ users and host over 350+ spaces ranging from team to project spaces. This can be a nightmare to maintain if you're expected to manage the application all alone.
First things first, I make sure each space has an owner who is responsible for making sure permissions and the content published on their space is up to date. This takes huge pressure off straight away. I track all our space owners using Excel and review this once a year. I make the space owner select a 2nd person who can take over their responsibilities if they ever go off work sick.
Having a space owner and giving them tasks will make it far easier when people start requesting access to their space. They need to be the ones to authorise and grant the access. This will cover your back if information ever falls in the wrong hands.
When a person requests a new project or team space, they must all follow the same page tree structure. This makes it easier for the senior management team and customers to find information. Don't let the page tree turn into a mess as this will just anger people. We don't allow anyone to create a page outside the page tree group. We call those uncategorised pages and we ask the authors to relocate them to a more suitable area. We did some requirements gathering and found that the below page tree works for us (yours might look different):
1, Meet the team
3, Processes (high level diagrams)
4, Procedures (roles and responsibilities)
5, User Guides (step by step instruction)
7, Training Matrix
9, Team Documents (restricted area for team members only)
10, Shared Documents (shared with all departments)
Each author has somewhere to publish their page and can decide to create sub page groups to organise their content even further.
This page tree is copied across from a template and can be moved across into a new team or project space in less then 5 minutes.
Each space front page must contain certain information to allow their customers to find what they need.
Team spaces must list out their services and links to key procedures. The front page also contains a search box that will only lookup content in their team space.
Project spaces must contain information about the project, summary, in scope, out scope, progress tracker and roadmap etc...
The final thing to help keep our environment clean, we make sure that each team and space owner regularly reviews their pages every few months. Pages which are no longer needed, are moved to section 11, Archive of their page tree.
Each month, I go through all the spaces to move out all the pages from their archive bin. This is moved across to the global archive space:
We have a global archive space for each year. After the 7th year we will export the first space to keep it on a secure file store.
Each page we archive is organised by team and grouped by the date we archive their unwanted pages. For example:
We put a date of when we archive team pages and ask anyone to complete an electric form if they want the information back.
**** As a rule, unfinished pages we delete, published pages which are no longer required archived ***
As I said before this method might not work for everyone but I hope it does help some of you who was as stuck and frustrated as I was about 3 years ago. Since implementing this method, I have seen a massive difference in activity.
To ensure space owners and page authors do what they are told, we typed up a procedure and got this signed off by the head of our department. We communicated this procedure to the wider business to ensure they are fully aware of their responsibility when using the site. We use this procedure as an excuse to escalate bad practices.
Hi, Confluence collaborators! As part of #Confluence-Collaboratory month, we’ve created a very special Mythsbusters segment, where we're dive into an interesting myth and uncover the truth behind i...
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