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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,424
Community Members
 
Community Events
176
Community Groups

Best Governance advice

Hello Everyone,

We have just started building our Confluence site. We would be using a phased approach (few teams at a time). Our ultimate goal is to make it an organization wide Wiki / Intranet. Based on your experience, what are some of the things we should consider or take care to build a solid foundation and avoid growing pain? Looking forward to hearing from Gurus here. 

1 comment

Some things to think about

How will users search for info when your sight gets big and be able to find things. Maybe start with an agreed taxonomy labelling system for pages so you can limit the searches by labels.

Remember attachments such as pdfs and ppts don't search well and are not great at visibility on confluence.

Also consult your users about the information architecture. What might be intuitive to you might not be to another team.

Think carefully about page headings try to avoid duplication and say what the page is/does rather than something to abstract.

Think about how you want to keep things updated. Establish who can add new pages you don't want everyone having that power or you information architecture will crumble. 

Also establish some global templates early on to keep consistency between info pages for layout so you don't have so many layouts people don't know where to look at the page. Best to also run these templates past your users for feedback and make adjustments.

Don't work in isolation ask the team what they need. Try to establish the why things are needed rather than jumping to solutions first. 

Like # people like this

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events