If you need more explanation or have any other questions then please contact us.
Yes – You can still use wiki markup in ThemeBuilder. There’s an option in the panel editor to choose between storage format, wiki markup or plain html for each panel, and you can use the new macro insert and editor buttons in wiki markup mode as well.
You just need to remember that wiki markup in a skin has to be processed by Confluence so it can be displayed as html, and that makes it less efficient than rendering storage format. That extra processing time may be measured in milliseconds, but at the Enterprise level this can be a crucial detail, so we recommended using storage format as soon as you’re comfortable with it.
No – sorry, we tried really hard to make this happen and just couldn’t. Mainly because there isn’t an efficient way to allow full backwards compatibility with the new skin format. The power and flexibility in skins is such an advancement on previous ThemeBuilder versions that it would have impacted the product to allow old layouts to be imported. But we know this was going to be an issue with our loyal ThemeBuilder users so we created the new free Layout Exporter plugin to help you migrate your layout to ThemeBuilder.
With the layout exporter you’ll be able to export a theme builder layout into the new skin format, but there may still be some manual conversion needed if, for example, you have a theme that uses complex menu code or older deprecated macros.
The thing to bear in mind is that the Confluence 5 user interface has evolved to a point where these older designs really need to be reviewed and updated, to make sure you’re taking advantage of all the great new functionality in Confluence and ThemeBuilder.
No - the Layout Exporter plugin is completely free and can be downloaded from the Migrating from Theme Builder 4 to ThemeBuilder 5 page.
The new code used in ThemeBuilder to hold all the Confluence content together doesn’t have the same fixed table based framework that the previous Theme Builder used to rely on for content layout.
The ROOT skin recreates the standard Confluence 5 look to give you a familiar starting point for a new design, but because the whole page is now based on html divs, and not tables, you’re free to pull apart and rebuild a confluence page in any shape you like when you customise a skin.
Because the panel divs are positioned on the page only when that page is finally displayed in the browser, we can’t show a panel view that resembles the finished page. So now ThemeBuilder presents all panels in a list – where you can edit names and descriptions that will help you relate those panels to the correct areas on the finished page. The bonus here is that you are no longer limited by a fixed number and positioning of content panels. You can have as many panels as you want in a skin, nest those panels, and position them where you want with CSS.
We will also be working on a mobile skin to be released as part of the new Themes For Confluence product.
You can read more about flaglogic in our ThemeBuilder 5 Documentation.
Yes – For Licenses of 50 users or higher, the paid version of ThemeBuilder will include one year of helpdesk support, plus plugin maintenance and updates.
For Licenses of 10 and 15 users there will be community support forums, plus plugin maintenance and updates.
As the Carousel macro is a decorative item the images are added to the page as CSS backgrounds and therefore should not need alt tags. We have added an accessibility review of the Carousel into the ThemeBuilder roadmap so please contact us if this is an urgent issue for you.
Yes – if you have ThemeBuilder installed and a current license, you can use any of the included macros like the Carousel in any of your confluence pages.
Theme Builder 4 Documentation for Confluence 4 and earlier.
Please see our documentation for information on turning off google analytics : Turning off Google Analytics