Our wiki provides client-facing documentation for our core product. We are now in the process of building a variant of the core product. This variant product will be given an entirely different branding, as though it belongs to a different company. We need to follow suite for the documentation.
The obvious solution would be to spin up a separate instance of Confuence. We would be able to define a distinct domain, logo, color scheme, etc.
Are there other, smarter solutions out there? Perhaps involving custom development (user macros), etc.?
Thanks in advance for any ideas! I can't find any guidance on this in the Confluence docs on on the web.
Jesse
Community moderators have prevented the ability to post new answers.
Hi Jesse,
we have created the Scroll Viewport add-on for these kind of use cases. It allows 100% custom designs/themes, different themes for different URLs/Domains, SEO-friendly URLs and more.
With Scroll Viewport you can create one or more viewports, which are registered at a custom URLs (make sure the domain names points to your Confluence server), and assign a theme to it. The themes can developed in HTML, CSS, JS (whatever you need), more info about that here: http://www.k15t.com/display/VPRT/Developers+Guide.
More Info:
Let me know if you have any questions.
-Stefan
Hi Stefan, That looks really interesting. We're currently trialling Confluence with an aim to whitelabel our documentation in-line with whitelabelling our software for resellers who don't want our branding, and it seems your ability to set different themes for different domains would achieve this. An extra question though, within the documentation we would normally refer to the name of the product, however we can't allow that name to be shown to customers of our whitelabelled resellers. In our current wiki we have a plugin which replaces {platform_name} with the whitelabelled name of the product. Is there any way of achieving similar functionality? Thanks, ChrisM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Take a look at this and see if it helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, Timothy. I hadn't realised that it's possible to control content visiblity via layouts. We generally use the show-if macro, which lets you do pretty much the same thing (hide/show content based on users, user groups, etc.). But layouts might be interesting to explore.
In addition to customising appearance and content, I'm interested in changing the domain, the login page. Any thoughts about whitelabeling at that level?
Thanks again,
Jesse
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.