"Managing Confluence space content"-Part 2
Welcome back dear Confluence evangelists.
In this second article we will have a quick and good to know information about "Managing Confluence space content".
Good to know points:
Each space can have unlimited parent and child pages.
The pages are stored hierarchically in the space:
Space Directory ⬇️
Site spaces ⬇️
[ Space ⬇️]
Parent page ⬇️
Deleting a page in the Confluence moves it to the “space’s trash”.
**When a user chose to delete only the parent page leaving their child pages, then those child pages will move UP to the nearest parent page**
A deleted page when recovered is “restored as a child page” of Home page. The user needs to reorder the hierarchy.
Only a Space administrator can either “recover” the deleted pages or permanently delete the pages by purging from the trash.
A hidden page: When a page(s) is not linked to a parent and have no connecting links, then those pages can be called as “hidden pages”. These pages resides in the root of the space.
How to find the hidden pages?
In the space settings >> from the “hidden pages tab” in the manage pages section.
Labels will have an impact on the macros that have dynamic content. Hence, adding labels not just give your pages an organized look, but helps gives compatibility with Atlassian marketplace plugins built exclusively for enhancing the Confluence features.
Page templates: They are the “pre-defined pages with content”. These templates can be self made or provided by blueprints or Atlassian marketplace apps.
>> Page templates are used only for “creating one page”.
Blueprints: They are the “set of page templates” with added functionality.
>> When a user uses a blueprint for the first time, the Confluence creates an “index page and also a space shortcuts”.
>> Do you know that majority blueprints can be customized to do exactly what you want! >> add macros, change format, add/remove sections etc.
>> A blueprint can be promoted to all team members. When does, Confluence allows only at the “space level” but not at the “global level“.
Macros: In the Confluence pages, a macro can be accessed by using the slash ( / ) command.
>> They allow to add extra and meaningful functionality to the content.
>> Note: Page restrictions impacts the macros.
>> Administrators can check macros usage in the organization by navigating to -Macro usage page.
Labels: They also has an impact on the Macros. Some Macros needs to be configured in order to deal with the “content based labels”.
A good way to ensure the correct label is used is to “create page templates and build correct label” into the template.
As you start using Confluence in your organization, teams start using it leaps and bounds given the ease of usage and clean interface. So, Atlassian suggests team’s to assign a dedicated role called -“content manager” along with few guidelines. Know more of these guidelines in this official course.
Reference: Atlassian University topic