Difference between revisions of "AppSuite:Theming"

(File structure)
(Replaced content with "The content on this page has moved to https://documentation.open-xchange.com/latest/ui/theming.html Note: Open-Xchange is in the process of migrating all its technical do...")
 
(129 intermediate revisions by 11 users not shown)
Line 1: Line 1:
In this article, you can learn how to create customized themes and use them to change the look of you appsuite installation.
+
The content on this page has moved to https://documentation.open-xchange.com/latest/ui/theming.html
  
== File structure ==
+
Note: Open-Xchange is in the process of migrating all its technical documentation to a new and improved documentation system (documentation.open-xchange.com). Please note as the migration takes place more information will be available on the new system and less on this system. Thank you for your understanding during this period of transition.
 
 
A theme basically consists of two files located in <code>$APPSUITE_ROOT/apps/themes/$YOUR_UNIQUE_THEME_NAME</code>. These files are described in this and the following sections.
 
 
 
=== definitions.less ===
 
 
 
This file can be used to override variables described in the "Variables" section of this article.
 
 
 
=== style.less ===
 
 
 
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.
 
 
 
== Variables ==
 
 
 
=== Basic ===
 
 
 
==== Font ====
 
 
 
{|
 
! Variable || Default || Description
 
|-
 
| @sansFontFamily      || "Helvetica Neue", Helvetica, Arial, sans-serif
 
|-
 
| @serifFontFamily      || Georgia, "Times New Roman", Times, serif
 
|-
 
| @monoFontFamily      || Monaco, Menlo, Consolas, "Courier New", monospace
 
|-
 
| @baseFontSize        || 14px
 
|-
 
| @baseFontFamily      || @sansFontFamily
 
|-
 
| @baseLineHeight      || 20px
 
|-
 
| @altFontFamily        || @serifFontFamily
 
|-
 
| @touchFontSize        || 15px
 
|-
 
| @headingsFontFamily  || inherit
 
|-
 
| @headingsFontWeight  || bold
 
|-
 
| @fontSizeLarge        || @baseFontSize * 1.25
 
|-
 
| @fontSizeSmall        || @baseFontSize * 0.85
 
|-
 
| @fontSizeMini        || @baseFontSize * 0.75
 
|}
 
 
 
==== Colors ====
 
 
 
{|
 
! Variable || Default || Description
 
|-
 
| @bodyBackground      || @white
 
|-
 
| @textColor            || @grayDark
 
|-
 
| @linkColor            || #08c
 
|-
 
| @linkColorHover      || darken(@linkColor, 15%)
 
|-
 
| @linkAccentColor      ||  #ffad00
 
|-
 
| @linkAccentColorHover || darken(@linkAccentColor, 15%)
 
|-
 
| @headingsColor        || inherit
 
|-
 
| @black                || #000
 
|-
 
| @grayDarker          || #222
 
|-
 
| @grayDark            || #333
 
|-
 
| @gray                || #555
 
|-
 
| @grayLight            || #aaa
 
|-
 
| @grayLighter          || #eee
 
|-
 
| @white                || #fff
 
|-
 
| @blue                || darken(#049cdb, 5%)
 
|-
 
| @blueDark            || #0064cd
 
|-
 
| @blueLight            || lighten(#049cdb, 25%)
 
|-
 
| @green                || #1A8D1A
 
|-
 
| @greenLight          || #92D050
 
|-
 
| @red                  || #cc0000
 
|-
 
| @yellow              || #F8E400
 
|-
 
| @orange              || #f89406
 
|-
 
| @pink                || #E01CD9
 
|-
 
| @purple              || #7E16CF
 
|-
 
|}
 
 
 
=== Foldertree ===
 
{|
 
! Variable || Default || Description
 
|-
 
| @foldertreeSidepanelBackground ||
 
|-
 
| @foldertreeSectionTitleColor ||
 
|-
 
| @foldertreeActiveLabelColor ||
 
|-
 
| @foldertreePassiveLabelColor ||
 
|-
 
| @foldertreeHoverBackground ||
 
|-
 
| @foldertreeSelectedBackground ||
 
|-
 
| @foldertreeCounterBadgeBackground ||
 
|-
 
| @foldertreeCounterBadgeColor ||
 
|}
 
 
 
== Mixins ==
 
 
 
== How to activate a theme during development ==
 
 
 
When creating a new theme, you don’t have it installed with your frontend. In this case you don’t want to go to a complete build of a theme and reinstall it for every change. The trick is to create your theme and overwrite the default theme with it. You can then use the [[AppSuite:appserver|appserver]] proxy to ship your own version of the UI.
 
 
 
To activate a theme on the backend, you have to add it to the <code>io.ox/core/settingsOptions//themes</code> list.
 
 
 
==== Example ====
 
 
 
Adding <pre>io.ox/core/settingsOptions//themes/unicorn=Friendship is Magic</pre> to <code>etc/settings/appsuite.properties</code> add a theme named <code>unicorn</code> with the name <code>Friendship is Magic</code> to the list of themes, a user can choose. Find the list in the <code>Settings -> Basic</code> view behind the option <code>Theme</code>.
 
 
 
== Best practice ==
 
 
 
== Caveats ==
 
 
 
[[Category:AppSuite]]
 
[[Category:UI]]
 

Latest revision as of 10:20, 22 May 2017

The content on this page has moved to https://documentation.open-xchange.com/latest/ui/theming.html

Note: Open-Xchange is in the process of migrating all its technical documentation to a new and improved documentation system (documentation.open-xchange.com). Please note as the migration takes place more information will be available on the new system and less on this system. Thank you for your understanding during this period of transition.