Difference between revisions of "AppSuite:Theming"

m (Most relevant variables)
m (Most relevant variables)
Line 70: Line 70:
| @topbar-background || @topbarBackground || #3774A8 (blue)
| @topbar-background || @topbarBackground || #3774A8 (blue)
| --- || @topbarBackgroundAlt ||
| --- || @topbarBackgroundAlt || No longer used
| @topbar-launcher-color || @topbarLauncherColor || rgba(255, 255, 255, 0.70)
| @topbar-launcher-color || @topbarLauncherColor || rgba(255, 255, 255, 0.70)

Revision as of 18:48, 11 April 2014

API status: In Development


Abstract. In this article, you can learn how to create customized themes and use them to change the look of you appsuite installation.


Appsuite used LESS as dynamic stylesheet language. LESS extends CSS with dynamic behavior such as variables, mixins, operations and functions.

Please read LESS.JS documentation first.

Using less.js

If your theme depends on less.js, you will need one more step to make it work. Why? To accelerate the login, compilation of LessCSS files was moved from the login process in the browser to the installation process on the backend.

Backend packages for themes and any apps which ship .less files require the following changes:

1. Add "skipLess=1" to the build command in *.spec and in debian/rules:

  sh /opt/open-xchange-appsuite-dev/bin/build-appsuite app skipLess=1

2. Add %post and %postun sections to *.spec:

  if [ "$1" = 1 ]; then
  [ -x $UPDATE ] && $UPDATE
  [ -x $UPDATE ] && $UPDATE

For multiple binary packages, the %post and %postun sections should apply only to backend packages which contain .less files.

3. Add debian/postinst and debian/postrm containing the same content:

  [ -x $UPDATE ] && $UPDATE

For multiple binary packages, the postinst and postrm files should apply only to backend packages which contain .less files.

Note: Since 7.2.1, LessCSS files must have the file extension .less to be usable with the 'less' RequireJS plugin (module dependencies of the form 'less!filename.less'). Previously we were more lenient and dealt with .css, too.

File structure

A theme basically consists of two files located in apps/themes/THEME_ID/. These files are described in this and the following sections.

THEME_ID is a unique identifier for your theme, which is not visible to users. By convention, it is best derived from a domain name you control, e.g. com.example.prettytheme.


This file can be used to override variables described in the "Variables" section of this article.


This file can be used to define any CSS you like. Before doing this, check, if there really is no variable that can be used to achieve the same thing.

Referencing paths

Since 7.2.1, all URLs are relative to the source .less file in which they are contained. This means that unless a theme changes an image it does not need to include that image anymore.

Old themes must be updated if they change an image from the default theme: All styles from the default theme which refer to a changed image must be overwritten in the custom theme. This way the URLs resolve to the new image.


Naming of the variables should be straight forward. Variables containing the word Background will always refer to the background color. Variables containing Color will refer to the foreground color of an element, like color of a font. Hover in most cases means "hovered" elements. Selected relates to the currently selected item. Elements that are supposed to catch the users eye can use the Highlight class and the variable contains this word.

Variables are defined in variables.less from twitter-bootstrap and our default definitions.less. Variables that are defined in definitions.less always override variables from bootstrap's variables.less


Most relevant variables

Variable (7.6.x) Variable (7.4.x) Default (7.6.x)
@topbar-background @topbarBackground #3774A8 (blue)
--- @topbarBackgroundAlt No longer used
@topbar-launcher-color @topbarLauncherColor rgba(255, 255, 255, 0.70)
@topbar-launcher-color-hover @topbarLauncherColor-hover #fff
@topbar-launcher-color-active @topbarLauncherColorActive #fff
@topbar-launcher-background-hover @topbarLauncherBackgroundHover rgba(0, 0, 0, 0.30)
@topbar-launcher-background-active @topbarLauncherBackgroundActive rgba(0, 0, 0, 0.20);
@topbar-icon-color @topbarIconColor #fff
@selected-background @selectedBackground #428BCA (blue)
@contact-picture-radius @contactPictureRadius 50%

The most significant visual change is achieved by changing the following variables:

  • @topbar-background (top navigation bar)
  • @selected-background (selection background color in list views and folder tree)
  • @link-color (almost all hyperlinks)


Variable (7.6.x) Variable (7.4.x) Default (7.6.x)
@font-family-sans-serif @sansFontFamily "Helvetica Neue", Helvetica, Arial, sans-serif
@font-family-serif @serifFontFamily Georgia, "Times New Roman", Times, serif
@font-family-monospace @monoFontFamily Monaco, Menlo, Consolas, "Courier New", monospace
@font-size-base @baseFontSize 14px
@line-height-base @baseLineHeight 1.428571429; // 20/14
@font-size-touch @touchFontSize 15px
@headings-font-family @headingsFontFamily inherit
@headings-font-weight @headingsFontWeight 500
@font-size-large @fontSizeLarge ceil((@font-size-base * 1.25)); // ~18px
@font-size-small @fontSizeSmall ceil((@font-size-base * 0.85)); // ~12px
@vgrid-font-size @vgridFontSize 13px


Variable (7.6.x) Variable (7.4.x) Default (7.6.x)
@background @bodyBackground #fff
@text-color @textColor @gray-dark
@link-color @linkColor @brand-primary
@link-hover-color @linkColorHover darken(@link-color, 15%)
@link-accent-color @linkAccentColor #ffad00
@badge-color @badgeColor @white
@badge-bg @badgeBackground #aaa
@headings-color @headingsColor inherit
@black @black #000
@gray-darker @grayDarker #222
@gray-dark @grayDark #333
@gray @gray #555
@gray-light @grayLight #999
@gray-lighter @grayLighter #eee
@white @white #fff
@blue @blue darken(#049cdb, 5%)
@blue-dark @blueDark #0064cd
@blue-light @blueLight lighten(#049cdb, 25%)
@green @green #1A8D1A
@green-light @greenLight #92D050
@red @red #cc0000
@yellow @yellow #F8E400
@orange @orange #f89406
@pink @pink #E01CD9
@purple @purple #7E16CF


Variable (7.6.x) Variable (7.4.x) Default (7.6.x)
@border-radius-base @baseBorderRadius 4px
@border-radius-large @borderRadiusLarge 6px
@border-radius-small @borderRadiusSmall 3px


Used where pagination is done, for example in the Calendar weekview, each week is on one "page"; one can switch the week using a pagination widget styled with these variables.

Variable (7.6.x) Variable (7.4.x) Default (7.6.x)
@pagination-bg @paginationBackground #fff
@pagination-border @paginationBorder #ddd
@pagination-active-bg @paginationActiveBackground @brand-primary


Variable (7.6.x) Variable (7.4.x) Default (7.6.x)
@btn-primary-background @btnPrimaryBackground @link-color
@btn-primary-background-highlinght @btnPrimaryBackgroundHighlight darken(@btn-primary-background, 10%);
@btn-info-background @btnInfoBackground #5bc0de
@btn-info-background-highlight @btnInfoBackgroundHighlight #2f96b4
@btn-success-background @btnSuccessBackground #62c462
@btn-success-background-highlight @btnSuccessBackgroundHighlight #51a351
@btn-warning-background @btnWarningBackground lighten(@orange, 15%)
@btn-warning-background-highlight @btnWarningBackgroundHighlight @orange
@btn-danger-background @btnDangerBackground #ee5f5b
@btn-danger-background-danger-highlight @btnDangerBackgroundHighlight #bd362f
@btn-inverse-background @btnInverseBackground #444
@btn-inverse-background-highlight @btnInverseBackgroundHighlight @gray-darker


Variable (7.6.x) Variable (7.4.x) Default (7.6.x)
@dropdown-bg @dropdownBackground #fff
@dropdown-border @dropdownBorder rgba(0,0,0,.15)
@dropdown-divider-bg @dropdownDividerTop #e5e5e5
@dropdown-divider-bg @dropdownDividerBottom #e5e5e5
@dropdown-link-color @dropdownLinkColor @gray-dark
@dropdown-link-hover-color @dropdownLinkColorHover darken(@gray-dark, 5%)
@dropdown-link-active-color @dropdownLinkColorActive @component-active-color
@dropdown-link-active-bg @dropdownLinkBackgroundActive @component-active-bg
@dropdown-link-hover-bg @dropdownLinkBackgroundHover #f5f5f5


Variable (7.6.x) Variable (7.4.x) Default (7.6.x) Description
@foldertree-sidepane-background @foldertreeSidepanelBackground #f5f5f5
@foldertee-section-title-color @foldertreeSectionTitleColor #888 Color for sectiontitles in foldertree (like "Public" folders)
@foldertree-active-label-color @foldertreeActiveLabelColor #333 Active means, user can perform an action on this item
@foldertree-passive-label-color @foldertreePassiveLabelColor @hc-gray Passive means, user can not perform any action with this item
@foldertree-hover-background @foldertreeHoverBackground rgba(0, 0, 0, 0.05)
@foldertree-selected-background @foldertreeSelectedBackground rgba(0, 0, 0, 0.10)
@foldertree-badge-background @foldertreeBadgeBackground @bagde-bg see #Colors for definition of @badge-bg
@foldertree-badge-color @foldertreeBadgeColor @badge-color see #Colors for definition of @badge-color



Variable (7.6.x) Variable (7.4.x) Default (7.6.x) Description
@appointment-reserved @appointmentReserved #08c /* blue */ Appointment status color
@appointment-temporary @appointmentTemporary #ffbb00 /* yellow */ Appointment status color
@appointment-absent @appointmentAbsent #913f3f /* red */ Appointment status color
@appointment-free @appointmentFree #8eb360 /* green */ Appointment status color
@appointment-private @appointmentPrivate #555 /* gray */ Appointment status color
@appointment-declined-font @appointmentDeclinedFont #888 /* dark gray */ Font color for declined Appointments
@appointment-unconfirmed-alpha @appointmentUnconfirmedAlpha 0.4 Transparency value for unconfirmed Appointments
@appointment-declined-alpha @appointmentDeclinedAlpha 0.3 Transparency value for declined Appointments
@appointment-hover-pct @appointmentHoverPct 15% Percentage increase of the dark pigment content on hover effect

Week View

Variable (7.6.x) Variable (7.4.x) Default (7.6.x) Description
@weekview-appointment-lasso @weekviewAppointmentLasso #aeaeff Lasso frame color
@weekview-day-in @weekviewDayIn #fff /* white */ Default background color in week view
@weekview-day-out @weekviewDayOut #e0e0e0 /* grey */ Background color outside of the mean working time
@weekview-timeline @weekviewTimeline rgba(243, 15, 170, 0.4) Color of the Line indicating the current time
@weekview-time-width @weekviewTimeWith 58px With of the time labels on the left side
@calendar-toolbar-height @calendarToolbarHeight 47px Height of the control toolbar

Month View

Variable (7.6.x) Variable (7.4.x) Default (7.6.x) Description
@monthview-appointment-out @monthviewAppointmentOut #aaa /* light gray */ Color of appointments, which are not in focus
@monthview-today @monthviewToday #daefff /* light blue */ Background color of the current day

Area names

The variables sometimes refer to common areas. To identify which area is located where, see the following annotated screenshots.

Mail application

Launchpad application

One of the most common theme changes which requires editing style.css is changing the logo in the top right corner. The logo is displayed as the background image for an element with the ID io-ox-top-logo-small. A theme can therefore change the size and URL of the image:

#io-ox-top-logo-small {
    width: 60px;
    height: 22px;
    margin: 8px 13px 0 13px;
    background-image: url(mylogo.png);

The file mylogo.png is expected to be in the same directory as style.css. If you want to place the image somewhere else, then use a relative path in url().

Remember that images in OX App Suite are served by the web server and not by the application server. This means that images need to be packaged separately (for dedicated web servers) and installed in /var/www/appsuite/ (or similar, depending on the target platform) instead of /opt/open-xchange/appsuite/. Direct support for multiple packages is coming in version 7.4.1. Until then, use the build system from the develop branch to initialize the packaging if your theme contains images.


In LESS, it is possible to include a bunch of properties from one ruleset into another ruleset. So say we have the following class:


.border-radius(@radius: 0px) {
    -webkit-border-radius: @radius;
    -moz-border-radius: @radius;
    -ms-border-radius: @radius;
    border-radius: @radius;

#menu a {
  color: #111;

Read LESS Mixins

global OX Mixins

they can be found at definitions.less

Mixin Sample Description
.box-sizing(@boxmodel) .box-sizing(border-box)
.user-select(@select) .user-select(none)
.border-radius(@radius) .border-radius(3px)
.box-shadow(@shadow) .box-shadow(3px)
.vertical-gradient(@startColor, @endColor) .vertical-gradient(#888, #555)
.radial-gradient(@color1, @color2, @color3) .radial-gradient(#111, #222, #333)
.transition(@transition) .transition(background-color 0.2s linear)
.animation(@animation) .animation(slidein 300ms)
.animation-name(@name) .animation-name(slideright)
.ellipsis .ellipsis
.overflow(@type) .overflow(hidden)
.overflow-x(@type) .overflow-x(hidden)
.overflow-y(@type) .overflow-y(hidden)
.backface-visibility(@type) .backface-visibility(hidden)

How to activate a theme during development

When creating a new theme, you will want to test changes quickly without building packages reinstalling them. The trick is to use appserver.

  1. First, you need to add the theme to the list of available themes on the backend. Simply create a new file in /opt/open-xchange/etc/settings/ with the extension .properties and add a line for your theme to it: <pre<noinclude></noinclude>>io.ox/core/settingOptions//themes/ID=Theme Name</pre<noinclude></noinclude>> Replace ID by the identifier (directory name) of your theme, and Theme Name by the human-readable name which should appear in the UI.
  2. The server needs to be restarted to read the new settings.
  3. Now, you can use appserver (with a local web server if your theme includes images) to get your theme in combination with the UI which is already installed on the backend.
  4. Finally, activate your theme the list in the Settings -> Basic view behind the option Theme.

In case you also want to access the same backend without appserver while your theme is selected, that theme (or at least some empty .less files) should be also installed on the backend to avoid errors. To just use an empty theme, run the following as root:

touch /opt/open-xchange/appsuite/apps/themes/ID/definitions.less
touch /opt/open-xchange/appsuite/apps/themes/ID/style.less

The value of ID here must be the same as in your .properties file.

Favicons and mobile homescreen icons

Note: This chapter is not about changing AppSuite icons which are used in the application like the brand on the upper right.

This documentation applies for AppSuite v.7.4.2

AppSuite ships with a standard set of icons containing a

  1. favicon
  2. set of touch icons which are mainly used by mobile Safari on iOS

These icons are used as default for all devices and browsers as long as you don't deliver your own icons with your theme.


All major browsers support the use of a favicon. The favicon is a pixel image with the size of 16x16 (32x32) and the "ico" file ending. (see Wikipedia Favicon for details).

You should provide your custom favicon within your custom theme. If you do not add a custom favicon to your theme the global OX default will be used. The default icon is located under apps/themes/icons/default on the web server.

Attention: Safari and Internet Explorer do not support dynamic changes to the favicon for a webpage. This means, the default icon will be shown even if a custom favicon is provided within a custom theme. To enable the right favicon for a theme on Safari and IE, the overall standard favicon.ico located under apps/themes/icons/default on the web server must be replaced with a custom version.

Apple touch icons

iOS devices (iPhone/iPad/iPod) support so called "Webclips". Webclips are bookmarks to websites or webapps which provide a App Icon that is shown on the iOS homescreen. AppSuite offers full support for Webclips by providing all needed App icons, splashscreens and full screen support. If a user uses the "Add to homescreen" button on his iOS device, a Webclip is created, taking the right icon for his current device. Most devices need custom resolutions of the Webclip icon in the png format.

  • iPhone 3: 57 x 57 px
  • iPhone 4 retina: 114x114 px
  • iPhone iPhone 5 retina: 120 x 120 px
  • iPad: 72 x 72 px
  • iPad (iOS 7): 76 x 76px
  • iPad retina: 144 x 144 px
  • iPad retina (iOS 7): 152 x 152 px

Furthermore a fullscreen Webclip App will show a splashscreen, a jpg file that is displayed on startup during app load. There are currently three different resolutions as jpg files available. Note: Splashscreens must be JPG files

  • iPhone: 320 x 460 px
  • iPhone 4: 640 x 920 px
  • iPhone 5: 640 x 1096 px

Note: We do not provide splashscreens for iPad

This list may change with Apple's iOS updates. We recommend providing all of this resolutions when customizing the Webclip icons and splashscreens, even if some iOS devices use the next best resolution for an icon if a certain file is missing.

Providing custom icons

To provide custom Webclip icons locate the following path in the AppSuite installation on your web server:


This folder contains all OX default icons for Webclips icons and splashscreens. Use these as samples for your own versions.

A clean installation will have all our default icons in the "default" directory. To customize the icons we recommend using our default icons as samples and save your customized version in your theme. Note: The filename has to be the same as in the default folder. Otherwise the fallback will be applied and the default icons will be used. If more advanced rewriting is needed one should edit the contents of the .htaccess file located under apps/themes

Theming the login page

The login page is a little bit special. If you don’t use the form login and provide your own login page, you might want to theme the login page, too. Learn how to do this here.

Providing domain based login themes

If you have a multibrand installation and you want to deliver not only custom themes but also custom login-themes this can be done via Apache mod_rewrite. You can do so by a domain-based rewrite rule to deliver custom themes to a user based on the URI he's using. The needed config file .htaccess is located under apps/themes

# Sample config for domain based login theme
RewriteCond %{HTTP_HOST} ^www\.domain\.com$
RewriteCond %{REQUEST_FILENAME} -f
RewriteRule ^login/(.*)$ domain_com_logintheme/$1 [L]

Best practice

To be really safe, it’s best to only define your own values for the variables shown above. If this really breaks anything, we consider this a bug, please report it [1] in our bugzilla.

Of course, using CSS in style.less file to define your own styles is also possible. Make sure to test your style in such cases more carefully. It is most likely safe to change minor things using this file, but if you plan to change any positions of larger elements, this might break the complete design. So please be careful when overwriting the default CSS rules.


Responsive design



It is not recommended to change the size of elements or their position. If you really want to do so, please check on all devices and in all browsers and make sure you didn’t break anything. You even have to be careful when changing the font, because this might have effects on positioning, too.

As mentioned before, changing colors should be safe.