Create sites for different use cases
In version 6.0 of Refined for Confluence Data Center we introduced sites, making it possible to use content from one Confluence instance in several sites built on top of the instance. This opens op a whole range of new use cases for Confluence, such as intranets, knowledge bases, and documentation. It also improves performance for large/enterprise instances: as the content is divided into smaller chunks, it’s faster to fetch and render.
Collapse subcategories
Refined renders the category menu based on what the user is allowed to view. So when you have a high amount of categories, it may take a long time to calculate what to show in the menu. Collapsing subcategories helps you speed up this process.
| Expand | ||
|---|---|---|
| ||
When you enable the Collapse subcategories feature, Refined will render the top-level categories and allows the user to expand the categories they wish to explore. The spaces in the category are only fetched when the user decides to expand that category.
|
Cache management
When you have a large instance with many spaces or a lot of simultaneously active users, we recommend turning on the caching feature. This provides a number of benefits:
Fewer server requests.
Faster resource load times.
Great potential performance gain for large instances.
Smoother end user experience.
Always up-to-date.
| Expand | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
A small cache object is made available in the beginning of each page load, checking if the cached resources are up to date or if the administrator has made any changes to the cache management settings. This way the resources are still kept updated at all times. If a resource is cached, the user will read it locally without having to make any server requests. The resources are stored using the standardised Web Storage API, allowing for fast and efficient use across all major browsers. The cache system works with all supported browsers and versions. The cache management system is built with Web Storage.
|
Manual category permissions
Speed up sites with an exceptionally high amount of spaces by manually assigning category permissions to user groups.
| Note |
|---|
Because this approach involves manual work and upkeep, we only recommend it to customers whose Confluence instances have a complex structure, experience performance issues, or have users in many user groups. |
| Expand | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
When a user logs in, Refined calculates which categories should be visible. By default, users can view a category when they have permission to view a space inside the category. However, it is quicker to calculate this based on Manual Category Permissions than by iterating through all the spaces. Refined always respects Confluence permission settings in spaces: a user that is not allowed to see a space will not see the space even if they can see the category above it. Similarly, hiding a category containing a space will not hide the space to a user. If the user has the space’s URL or searches for it on the site, it will still show up if the space settings allow it.
|