What is the most effective way to label

Martim Schnack June 4, 2014

We want to create the documentation for our business units, departments, products, and projects inside of Confluence. There are several pages that is hard to define the right place to go, because they could belong to several places. For example: documentation about the code for one project.. should it go to the project space or the engineering space?

Based on our research, there is no right answer. The right way of achieving this is by using labels, and referencing label in different places. So a page can be found through different ways.

What is the most effective way to create the labels, so they are easy to understand and extremely efficient? What are the "must have" labels that work pretty well that we should not forget?

Thanks!

1 answer

1 accepted

6 votes
Answer accepted
Deividi Luvison
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 6, 2014

That's a tricky question Martim :),

I'm a big fan of RPG's so let me try to come up with an analogy to suit the same end you are looking for. Let's say you have the following classes (projects):

  • Priest
  • Warrior
  • Mage

Based on that you would create main labels to define those

  • Divine Spell Caster
  • Combatant
  • Arcane Spell Caster

So if we have a new document on "how to survive a hand to hand combat for mages" that should have the following labels:

Arcane Spell Caster

Combatant

After sometime you will notice that your main projects will have subdivision, so you will see that your Warrior project can be an archer, a fighter or a Knight (all those can be considered combatants), then you will have sub labels:

  • Meele Combatant or fighter
  • Ranged Combatant or archer
  • Horse Combatant or Knight

In case you are not a fan of RPG's and the above sound madness :p, then try to think on a main label to define each one of your projects like Coding, Engineering, Sales, Support and etc. If you have a doc that falls in more than one category put two labels to define this doc or page.

Other kinds of useful labels are, "document", so if you have a document like a manual for a self hosted app label it as document and support, for instance.

Hope it helps.

Thanks and Regards,
David|Atlassian Support

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events