A Confluence Space is simply the term that describes a container for related content. Think of a Space as a sub-site, or mini-site within Confluence. There are two types of Spaces. Personal Spaces for Confluence users to store their own work, and Site Spaces, which allow for collaboration, and joint authorship of documentation. Several Space templates are shipped with Confluence, to help you get started. For example, there are space templates designed for Team Collaboration, or for your Documentation or Knowledge Base needs. Space Templates provide basic starting points to help you get up and running faster. When you create your own Spaces, choose the closest match for your needs, and build what you need inside the space from there.
Confluence Space Templates
- The Blank Space template builds exactly that – an empty container. You can fill this Space with whatever types of Page content that you need, using the Create button inside the Space. For example, you could add File Lists to manage uploaded files, Meeting Notes, Product Requirements, standard Pages, Blogs for communication, or any of the many page templates available.
- Documentation Spaces are designed to help you create and organise documentation for your products or processes. This is a common task for many organisations, and this Template helps you to standardise this type of content.
- Knowledge Bases are great for creating self-help support or Frequently Asked Question sites. Their troubleshooting articles are easily created, and the space will organise these for you.
- The Team Space Template helps teams to collaborate, and gives them a Space to store their Team and Project Information. It includes a Blog for Communications. Each team can add whatever other Page content they require to fit their needs.
You can also create and store the specialised articles offered by Documentation, or Knowledge Base Spaces inside regular team spaces or blank spaces. Confluence is very flexible.
Making Confluence Work – Course Sample
Confluence Site Design Tips.
You can build a successful Confluence Site, containing many different Spaces, in several different ways. It basically gets down to the type, and quantity of information that you choose to combine inside any one Space. This will affect how many individual Spaces exist, inside your Space Directory. There is not necessarily always a right or wrong way to do this. But you will create different experiences, based on your choices. In this episode, we will explore some of the concepts for building a successful Confluence Site, and introduce Confluence Spaces.
Note: To access the ‘Create Space‘ button, and full ‘Space Tools‘ functions, requires Space Admin permissions.
The open structure of Confluence is one of its great strengths. However, this means that you can build your Confluence Site in several different ways. Each one will give a different experience to the end user. There are several things to consider, for example, how your teams interact, and what is the most logical way to organise your data. This may be through individual or combined spaces. Confluence allows you to store individual categories of information in completely separate spaces, such as team spaces, knowledge base spaces, or documentation spaces. However, it is a good idea to keep the end-user of Confluence in mind, as you design your structure.
One consideration is how much information you will actually store inside any one Space. Keep this simple, and think in terms of Big, Medium, or small chunks of information. Where you have large sets of related information, for example large Technical Manuals, Knowledge Bases, or Team spaces to help your Teams collaborate better, then you should probably create individual spaces to hold each of these data sets, separately. The alternative is to combine a wider range of related information into a single combined Space. This often happens with things such as Spaces designed to store Project information. This combines many related pieces of information, of different categories, into the same Space. Using a simple parent and child page-tree navigation structure, inside the Space, will separate different categories of information. This can give a better end-user experience to visitors.
You also have to take account of things like security, through Space Permissions, page restrictions, and whether you plan to offer access for anonymous visitors, to any of your spaces. Anonymous access allows visitors, for example, your customers, or colleagues from another area of your business, to access parts of your site without logging into Confluence, where they can open and read your documentation. An example of this is the Confluence Online Help System, which is stored in Confluence. This is kept in a separate Space, for security, and this space is open to internet visitors. Clarifying your needs first, then designing for these, often results in a better user experience, and a more logical structure for your Confluence site.
Take our Atlassian Confluence Training.