Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 9
Next »
In this article we explain the differences between Refined for Confluence Cloud and Refined for Confluence Server DC to help you decide which would be best for your clients.
Refined for Confluence - What's the same on Cloud and Server?
Refined for Confluence Cloud, Server and DC for the most part function the same on Cloud and Server. The key features such as the theme editor, layout editor, site builder for site organization, site structure and content modules are the same across hostings. There are some differences we explain below.
Refined for Confluence - What are the differences on Cloud and Server?
Refined for Confluence Cloud | Refined for Confluence Server DC |
---|
Refined for Confluence Cloud is an app connected to Confluence. It reads the API’s from Confluence Cloud and pulls in the data. This means on Cloud you will always have the standard Confluence site, together with the Refined Confluence site. Whereas on Server you switch on or off Refined to activate it on Confluence.
| On Refined for Confluence Server and DC the app is installed onto Confluence. Refined sits on top of Confluence, like a skin that changes the structure, navigation and look and feel. This means you need to switch off Refined if you wish to go back to the standard Confluence. Whereas on Cloud the two exist in parallel.
|
| |
| |
| |
On Cloud we call the folders in the top navigation menu ‘pages’. Confluence spaces are organized into Refined ‘pages’. ‘Pages’ are the same thing as ‘categories’ on server. Each Refined ‘page’ that groups content in the top navigation menu has a page home. Unlike on server, you cannot deactivate the ‘page homes’ on Cloud. You can however make a ‘page’ or ‘page home’ a custom link to anywhere on the site. On Refined Cloud, you can create ‘pages’ and sub Refined ‘pages’ in the site builder. Both have ‘page homes’ (dashboard/layouts) by default. You cannot deactivate the page homes or sub page homes. On Refined Cloud it is best to think of page homes as pages to build custom content on rather than dashboards.
| On Server we call the folders in the top navigation menu ‘categories’. Confluence spaces are organized into Refined ‘categories’. ‘Categories’ are the same thing as ‘pages’ on Cloud. Each Refined ‘category’ that groups content in the top navigation has a category home (dashboard). On server, you can deactivate the ‘category homes’. Meaning when you click the category you will be shown the dropdown menu only, and not view a dashboard. On server, you can create categories and subcategories in the site builder. Both have dashboards by default. You can deactivate the category and subcategory dashboards. Subcategories are a good way to create a column feel. Customers often deactivate the dashboard on subcategories.
|
On Refined for Confluence Cloud page and space permissions rule. Permissions cannot be added to a Refined site or Refined page (a page is called a category on Server). However you can add view permissions to content sections in page layouts. On Cloud you can direct users to the right site by simply linking them the URL for a site.
| On Refined for Confluence Server/DC page and space permissions rule, but it’s also possible to add view permissions for sites and categories. See Manual Category Permissions. On Server you can set start sites for users. E.g., ‘employee user group’ can be set to start at the ‘intranet site’ when they login.
|
Refined for Confluence Cloud is not compatible with 3rd party apps and cannot yet render all items on a Confluence page (macros and markups). We are continually adding new support for new macros. Got a macro you really need rendered for a client? Get in touch with support.
| |
| |
| |