Duplicate Page Titles in Confluence for Everyone
Duplicate Page Titles in Wikis => $%#@!
In Confluence (as well as in other wikis) the title of a wiki page is directly coupled with the URL under which it can be accessed. This makes sense for wikis, as the wiki would not know which page to return if there are two pages with the same title.
However, not being able to name two pages with the same name in a documentation is a critical limitation for most documentation projects. For example, if you have an "Introduction" page for different parts of the documentation, this is simply not possible currently:
Sorry, no duplicate page titles in Confluence!
As a workaround you would have added a prefix and named one page "User Guide Introduction" and "Admin Guide Introduction".
Scroll Versions' Permalinks to the Rescue
Pretty soon after we started building Tools for wiki-based Documentation we understood that duplicate page titles is a must-have feature for documentation projects. And with Scroll Versions 1.0 we finally delivered a solution to that problem: Permalinks.
Defining a Permalink with Scroll Versions
Scroll Versions decouples the page title that is displayed in Confluence and exported pages from the URL (the "permalink"). By that it is possible to define freely page titles, and only the permalink needs to be unique. This also means that you can define multiple pages with the same name within one Confluence space as long as the permalink is unique.
As a result the page title is used anywhere on the UI (in the Scroll Exporters), only the URL uses the permalink:
Page Title vs. Permalink on the Confluence UI
Pretty neat, eh? (If you are interested in the details, have a look at our video on permalinks and duplicate page titles.)
Permalinks only, please!
Now, Scroll Versions comes with sophisticated version management, which you might not need to use in a normal wiki space (and therefore want to hide from normal wiki users). Fortunately, it is quite simple to tweak a space to leverage the permalink feature in Scroll Versions, but hide all other Scroll Version functionality.
After Scroll Versions has been installed on a Confluence system, it just requires two steps:
- Enable Scroll Versions in the space (under Browse > Scroll Versions) and enter confluence-users as doc-admins.
Hide the page info line and the menu entries in the the Tools menu (under Browse > Space Admin > Stylesheet) add the following CSS:
Please have a look at the Scroll Versions FAQ entry for a complete step-by-step explanation.
Update (Nov 9, 2012): In order to properly hide the infoline on the editor, you have to add
!important in the CSS code.
Document ManagementFree Templates: How to Export Your Confluence Content to Comply With DIN and ISO Standards