Confluence offers the user a lot of different automation features centered on organizing content, like labels, sub-pages, excerpts, page properties etc.<\/p>\n
But these are only as good as the weakest link. If the user misspells or forgets a label, the page can no longer be easily accessed. Learn the Best Practices on how to avoid such situations.<\/p>\n<\/div>
If you\u2019re creating a page properties macro list or want to keep the same standard to your knowledge base, it\u2019s always good to use page templates instead of ever-creating new pages or copying it and adding labels manually.<\/p>\n
Any Space admin can set up the templates and make it visible to the editors. Moreover, you can pre-set labels in the template, so when you create a new knowledge base article, it has all the necessary labels to work. No more human errors in this matter!<\/p>\n<\/div><\/div><\/div><\/div><\/div>
If you want to make sure that your editors will use the template, use the create from template macro to create a simple buttons for them. This rule is almost universal \u2013 the simpler you\u2019ll make the content creation process, the more fool-proof it will be.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
As said before, try to rely on the Page Tree instead of creating a tangled spiders\u2019 web of links. This way you\u2019ll be able to leave all the navigation to the automation-friendly tools such as Children Display. Also, every time you need to add something as a link manually, use the short link, so it won\u2019t be affected when you change the page name.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
Don\u2019t rely on adding links manually to your pages. It will make your life difficult in the long run, as keeping everything up-to-date will become increasingly harder the more content you have in your Wiki. Instead of this, try using automatic macros like Children Display.<\/p>\n
You can define level of the child pages that will be displayed on a page, and has an additional advantage \u2013 it forces you to keep your page structure clean and tidy.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
This said, it\u2019s far better to use the automatic links whenever available. This of course doesn\u2019t apply to the web links at all, but when it comes to Confluence and Jira links, you always have an alternative. And why is it so important?<\/p>\n
With Confluence links, they become essentially unbreakable no matter if you change the page\u2019s name or move it anywhere. With Jira, the links are automatically created in the Jira issues and Confluence pages, which greatly helps with navigation afterwards.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
Unfortunately, the basic Confluence setup can get you only so far. If you need any further automatization from Confluence, you can try one of the great Confluence apps available on the Atlassian Marketplace.<\/p>\n