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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

suggestions with spaces

hi all,

we have 2 differnt types of dcuments=support and application specific

i am new Confluence admin. we have confluence 5.10.

1) we have support documents that every IT user would use- we will break down the spaces by teams and each teams support docs will be subdivided into pages and subpages.

2)app docs-we intend to use it within our IT team which is subdivided into groups and each group has diffrent applications and each application has different projects.

diffrent IT groups can work on same project(like QA,developers & users). we want to have space & page structures set to make sense.

here are my thoughts for project docs. please let me know the advantages of using Structure 1 Vs Structure 2. im leaning towards 2.

   structure 1.JPGstructure2.JPG

1 comment

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 08, 2017

I'd think about the audience rather than the groups.  Who is going to be reading this documentation?  How is the end user likely to be understanding it?

As an example, let's say you've got a load of Financial traders who use trading applications.  They're not going to care, or even know what group owns what application.  When they need help with "Swaps and Options", they're going to look for that, not the team or group who maintains it.

You should build a structure for the consumers of the documentation.  Your developers are just as important, but as developers, they're more likely to be happy with a fragmented tree structure that works for the end user!

our end users would be all developers, manaers,senior management, QA team( for auditing ) and some business users. 


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events