Skip to Content

Wiki source code of Skins

Version 13.6 by Sorin Burjan on 2011/04/13
Hide last authors
Raluca Stavro 1.1 1 {{velocity}}
2 $xwiki.ssx.use($doc.fullName)
3 {{/velocity}}
MariusButuc 11.1 4
5 (% class="floatinginfobox" %)
6 (((
Raluca Stavro 1.1 7 **Contents**
8
9 {{toc depth="3" start="2"/}}
10 )))
11
MariusButuc 11.1 12 = XWiki Skins =
13
hennejg 11.2 14 == How to create a new Skin ==
Sorin Burjan 13.3 15
Sorin Burjan 13.4 16 {{warning}}
17 To create a new Skin, you must have access to the server side of the XWiki Enterprise instance.
18 {{/warning}}
Sorin Burjan 13.3 19
Sorin Burjan 13.5 20 To create a new Skin, you have to create a new direcory inside the webapps/xwiki/skins folder and then add Velocity templates,CSS stylesheets, Javascript files and images inside it. For example, if you want to remove the logo from the header of the pages, follow these steps:
MariusButuc 11.1 21
Sorin Burjan 13.5 22 1. Inside the webapps/xwiki/skins folder, create a folder named myskin. Copy all files from webapps/xwiki/skins/colibri folder into your new skin directory.
23 1. Change the Skin at global or instance level and set it as myskin ( see [[this>>AdminGuide.Skins]] page for more informations about how to change the Skin )
Sorin Burjan 13.6 24 1. Open any page in view mode and you will notice that myskin layout is the same as the colibri layout (if the skin changes to albatross means that your theme wasn't used. Check the names of your skin directory. Note that skin names are case-sensitive)
Sorin Burjan 13.5 25 1. Change the global template:
26 1*. to remove the logo, modify the global.vm template under the new Skin and delete the line:(((
27 {{code language="html"}}
28 <img src="$!logourl" alt="Wiki Logo"/>
MariusButuc 11.1 29 {{/code}}
30 )))
Sorin Burjan 13.5 31 1. Save the template
Raluca Stavro 1.1 32
Sorin Burjan 13.5 33 Open any page in view mode and you will notice that the XWiki logo is not displayed anymore. Congratulations! You have created a new minimal XWiki Skin.
Sorin Burjan 13.4 34
hennejg 11.2 35 == How to override a Skin ==
Sorin Burjan 13.3 36
Sorin Burjan 13.4 37 {{warning}}
38 To change the Skin, the user must have administrating rights. In the case that you have these rights, make sure that you switch to the Advanced mode in your profile, to enable the advanced options on the top main menu.
39 {{/warning}}
Sorin Burjan 13.3 40
Raluca Stavro 1.1 41 An alternative for creating a new Skin is the possibility to override an existing Skin. The advantage of overriding an existing Skin is the fact that you don't need access to the server filesystem in order to modify the files used by the current Skin.
42 To override a Skin, you have to use the same document that is used to store the Skin.
hennejg 11.2 43 {{id name="5a"/}}
Sorin Burjan 13.4 44
hennejg 11.2 45 === A. Creating a Skin document ===
Sorin Burjan 13.3 46
Sorin Burjan 13.4 47 {{warning}}
48 You need to have the **advance edition mode** activated to access the object editor. Please refer to [[platform:Features.PageEditing]] for more information.
49 {{/warning}}
Sorin Burjan 13.3 50
Raluca Stavro 1.1 51 To create a new Skin document, follow these steps:
52
Sorin Burjan 13.4 53 |(% style="width: 60%; color: rgb(34, 34, 34);" %)(((
MariusButuc 11.1 54 1. create a new page - if there is the option (% class="sectionblockcodecolored" %)CREATE -> PAGE(%%) on the main menu, use it to create a page, or, if there is no such option, add the (% class="sectionblockcodecolored" %)New Page(%%) panel on the interface by following these steps:
55 1*. go to (% class="sectionblockcodecolored" %)Administration -> Panel Wizard
56 1*. select the (% class="sectionblockcodecolored" %)Tools(%%) category
57 1*. add the (% class="sectionblockcodecolored" %)New Page(%%) panel on the interface by using drag&drop
58 1*. click on (% class="sectionblockcodecolored" %)Save the new layout(%%) to save your changes
59 1*. open any page in view mode and
60 1*. use the (% class="sectionblockcodecolored" %)New Page(%%) panel to create a page
61 1. edit the document's objects ( if you are in (% class="sectionblockcodecolored" %)edit(%%) mode, use the right panel and choose the (% class="sectionblockcodecolored" %)Objects(%%) editor, or, if you are in (% class="sectionblockcodecolored" %)view(%%) mode, use the top-left menu: (% class="sectionblockcodecolored" %)EDIT{{html}}&nbsp;->&nbsp;{{/html}}OBJECTS(%%))
62 1. add an object of type (% class="sectionblockcodecolored" %)XWiki.XWikiSkins(%%) to the document (use the **ADD OBJECT** panel from the right and select the (% class="sectionblockcodecolored" %)XWiki.XWikiSkins(%%) class, then click on (% class="sectionblockcodecolored" %)ADD OBJECT FROM THIS CLASS(%%))
63 1. save the document
64 )))|(((
Sorin Burjan 13.4 65 [[[[image:4.png||style="border: 3px solid rgb(221, 221, 221);" width="100%"]]>>attach:4.png]]
MariusButuc 11.1 66 )))
67
Sorin Burjan 13.5 68 {{id name="5b"/}}
Sorin Burjan 13.4 69
hennejg 11.2 70 === B. Working with the (% class="sectionblockcodecolored" %)XWiki.XWikiSkins(%%) class ===
Sorin Burjan 13.4 71
MariusButuc 11.1 72 The base element in overriding a Skin is the (% class="sectionblockcodecolored" %)XWiki.XWikiSkins(%%) class ( http://localhost:8080/xwiki/bin/view/XWiki/XWikiSkins ). In order to modify the templates or the files used by a Skin, you have to work with the properties of this class.
Raluca Stavro 1.1 73 By default, the Skin class contains a set of properties that allows you to override some of the templates and files used by the Skin, and it also allows you to set the name of the logo displayed in the header of the interface.
MariusButuc 11.1 74 To override other templates or files, you have to add new properties to the Skin class. For example, if you want to override (% class="sectionblockcodecolored" %)myfile.vm(%%) ( or myfile.css, or myfile.js ), follow these steps:
75
Sorin Burjan 13.4 76 |(% style="width: 60%; color: rgb(34, 34, 34);" %)(((
MariusButuc 11.1 77 1. go to the (% class="sectionblockcodecolored" %)XWiki.XWikiSkins(%%) document
78 1. click on the (% class="sectionblockcodecolored" %)add or modify the class properties(%%) link
Raluca Stavro 1.1 79 ( or follow this link: http://localhost:8080/xwiki/bin/edit/XWiki/XWikiSkins?editor=class )
MariusButuc 11.1 80 1. from the **ADD PROPERTY** panel in the right, set the name of the property as being (% class="sectionblockcodecolored" %)myfile.vm(%%), choose the (% class="sectionblockcodecolored" %)TextArea(%%) type, and click on (% class="sectionblockcodecolored" %)Add
81 1. save the document
82 )))|(((
Sorin Burjan 13.4 83 [[[[image:5.png||style="border: 3px solid rgb(221, 221, 221);" width="100%"]]>>attach:5.png]]
MariusButuc 11.1 84 )))
Raluca Stavro 1.1 85
Sorin Burjan 13.5 86 {{id name="5c"/}}
Sorin Burjan 13.4 87
hennejg 11.2 88 === C. Using a Skin document ===
Sorin Burjan 13.4 89
Raluca Stavro 1.1 90 To use a Skin document, follow these steps:
MariusButuc 11.1 91
92 1. go to the (% class="sectionblockcodecolored" %)Skin(%%) property from inside the (% class="sectionblockcodecolored" %)Administration(%%) interface
93 1. set the value of the property as being the full name of the Skin document
94 1. save the preferences
Raluca Stavro 1.1 95
hennejg 11.2 96 {{id name="5d"/}}
Sorin Burjan 13.4 97
hennejg 11.2 98 === D. Overriding the Skin components ===
Sorin Burjan 13.4 99
MariusButuc 11.1 100 Let's add a "HELLO," before the username on the top right menu, not by modifying the (% class="sectionblockcodecolored" %)global.vm(%%) template on the server, but overriding it inside the Skin document. Follow these steps:
101
Raluca Stavro 12.1 102 ==== Method 1: By editing the XWiki.XWikiSkins properties on the Skin document ====
103
Sorin Burjan 13.4 104 |(% style="width: 60%; color: rgb(34, 34, 34); overflow-x: auto;" %)(((
MariusButuc 11.1 105 1. add a (% class="sectionblockcodecolored" %)TextArea(%%) property named (% class="sectionblockcodecolored" %)global.vm(%%) to the (% class="sectionblockcodecolored" %)XWiki.XWikiSkins(%%) class
106 1. edit the Skin document's objects ( use the top-left menu: (% class="sectionblockcodecolored" %)EDIT -> OBJECTS(%%) ) and open the properties of the (% class="sectionblockcodecolored" %)XWiki.XWikiSkins(%%) object
Sorin Burjan 13.4 107 1. copy the original content of the (% class="sectionblockcodecolored" %)global.vm(%%) template and paste it in the property field named (% class="sectionblockcodecolored" %)global.vm(%%); if you don't have access to the server filesystem, open the template by following one of these links:
MariusButuc 11.1 108 1*. http://localhost:8080/xwiki/skins/mybaseskin/global.vm ( where mybaseskin is the current Skin used in the Skin document ), or
109 1*. if the previous link is not valid, go to http://localhost:8080/xwiki/templates/global.vm
110 1. replace the following code:(((
111 {{code language="xml"}}
112 <a class="glink"
Raluca Stavro 1.1 113 href="$!xwiki.getURL($context.user, 'view')"
114 id="headeruser">
115 $!xwiki.getUserName($context.user, false)
MariusButuc 11.1 116 </a>
117 {{/code}}
118 )))with(((
119 {{code language="xml"}}
120 <a class="glink"
Raluca Stavro 1.1 121 href="$!xwiki.getURL($context.user, 'view')"
122 id="headeruser">
123 HELLO,
124 $!xwiki.getUserName($context.user, false)
MariusButuc 11.1 125 </a>
126 {{/code}}
127 )))
128 1. save the document
129 )))|(((
Sorin Burjan 13.4 130 [[[[image:6.png||style="border: 3px solid rgb(221, 221, 221);" width="100%"]]>>attach:6.png]]
MariusButuc 11.1 131 )))
Raluca Stavro 1.1 132
Raluca Stavro 12.1 133 ==== Method 2: By attaching files to the current Skin document ====
Sorin Burjan 13.4 134
135 1. create a copy of the global.vm template; if you don't have access to the server filesystem, open the template by following one of these links:
Raluca Stavro 12.1 136 1*. http://localhost:8080/xwiki/skins/mybaseskin/global.vm ( where mybaseskin is the current Skin used in the Skin document ), or
137 1*. if the previous link is not valid, go to http://localhost:8080/xwiki/templates/global.vm
138 1. replace the following code inside the copy of global.vm template:(((
139 {{code language="xml"}}
140 <a class="glink"
141 href="$!xwiki.getURL($context.user, 'view')"
142 id="headeruser">
143 $!xwiki.getUserName($context.user, false)
144 </a>
145 {{/code}}
146 )))with(((
147 {{code language="xml"}}
148 <a class="glink"
149 href="$!xwiki.getURL($context.user, 'view')"
150 id="headeruser">
151 HELLO,
152 $!xwiki.getUserName($context.user, false)
153 </a>
154 {{/code}}
155 )))
156 1. attach the copy of global.vm template to the current Skin document page
157
Raluca Stavro 1.1 158 Now, open any document in view mode and you will notice the nice "HELLO," before your username.
MariusButuc 11.1 159 Follow the same process in order to override (% class="sectionblockcodecolored" %)Javascript(%%) and (% class="sectionblockcodecolored" %){{html}}<acronym title="Cascading Style Sheets">CSS</acronym>{{/html}}(%%) files ( http://localhost:8080/xwiki/skins/colibri/myfile.css ).
Raluca Stavro 1.1 160
Marta Girdea 13.1 161 ==== 3. Overriding a skin resource ====
162
163 Just like templates, resource files such as images or css/js files can be overridden. To do that, the replacement must be attached to the Skin document, making sure it complies with the naming convention explained below. To find out the right name for your replacement resource, here is the trick:
Sorin Burjan 13.4 164
Marta Girdea 13.1 165 1. find the path on the filesystem of the resource to replace (you can easily obtain that information using development tools such as [[Firebug>>http://getfirebug.com/]]); for instance, let's say this path is either
Sorin Burjan 13.4 166 {{code}}/xwiki/resources/icons/silk/myicon.gif{{/code}}
Marta Girdea 13.1 167 for a resource found in the general resource directry, or
Sorin Burjan 13.4 168 {{code}}/xwiki/skins/colibri/myimage.png{{/code}}
Marta Girdea 13.1 169 if the resource is specific to a certain skin, in this case 'colibri'.
170 1. strip from this path everything from the beginning until 'resources/' or the name of the skin, included; in the previous examples, you will obtain in the first case
Sorin Burjan 13.4 171 {{code}}icons/silk/myicon.gif{{/code}}
Marta Girdea 13.1 172 and in the second case simply
Sorin Burjan 13.4 173 {{code}}myimage.png{{/code}}
Marta Girdea 13.1 174 1. in this path, replace '/' with '.'; after this operation, we will get {{code}}icons.silk.myicon.gif{{/code}} for the first image example, while the second one remains unchanged. **This is the name of the file corresponding to the resource that you need to attach to the Skin document in order to make the replacement**.
175 1. create a file named as explained above and attach it to your Skin
176
177 {{info}}
178 **Technical note**: This trick works for any resource whose URL is generated in the skin by the {{code}}$xwiki.getSkinFile(){{/code}}, {{code}}$xwiki.jsfx(){{/code}} or {{code}}$xwiki.ssfx(){{/code}} methods, for instance like this:
179
180 {{code language="none"}}
181 .infomessage {
182 background-image: url("$xwiki.getSkinFile('icons/silk/information.gif')");
183 }
184 {{/code}}
185
186 In this case, {{code}}$xwiki.getSkinFile('icons/silk/information.gif'){{/code}} will first search for an image called 'icons.silk.information.gif' attached to the configured Skin document, if any. If that image exists, it will generate its URL. Otherwise, it will continue to search for 'icons/silk/information.gif' in the base skins and finally in the general 'resources/' directory.
187 {{/info}}
188
189
Sorin Burjan 13.5 190 {{id name="5e"/}}
Sorin Burjan 13.4 191
hennejg 11.2 192 === E. Adding new components to the Skin ===
Sorin Burjan 13.4 193
MariusButuc 11.1 194 If you want to add new files to the skin, like (% class="sectionblockcodecolored" %){{html}}<acronym title="Cascading Style Sheets">CSS</acronym>{{/html}} (%%) or (% class="sectionblockcodecolored" %)Javascript(%%) files, you have two options:
Raluca Stavro 1.1 195
MariusButuc 11.1 196 * attach the files to the Skin document and reffer them by their URL, or
197 * add new properties to the (% class="sectionblockcodecolored" %)XWiki.XWikiSkins(%%) object from inside the Skin document, and refer them by their name
198
199 For example, if you want to add a new {{html}}<acronym title="Cascading Style Sheets">CSS</acronym>{{/html}} file to the Skin, named (% class="sectionblockcodecolored" %)mynewfile.css(%%), follow one of these set of steps:
200
Sorin Burjan 13.4 201 |(% style="width: 60%; color: rgb(34, 34, 34);" %)(((
MariusButuc 11.1 202 1. attach the {{html}}<acronym title="Cascading Style Sheets">CSS</acronym>{{/html}} file to the Skin document
203 1. override the stylesheets.vm template ( check the section [[D>>#5d]] to learn how to override a Skin component ), and add the reference to your file in the template:(((
204 {{code language="xml"}}
205 <link rel="stylesheet"
Raluca Stavro 1.1 206 type="text/css"
207 href="$xwiki.getSkinFile('mynewfile.css')"
MariusButuc 11.1 208 />
209 {{/code}}
210 )))
211 1. save the document
212 )))|(((
Sorin Burjan 13.4 213 [[[[image:7.png||style="border: 3px solid rgb(221, 221, 221);" width="100%"]]>>attach:7.png]]
MariusButuc 11.1 214 )))
Raluca Stavro 1.1 215
216 OR
217
Sorin Burjan 13.4 218 |(% style="width: 60%; color: rgb(34, 34, 34);" %)(((
MariusButuc 11.1 219 1. add a new property to the (% class="sectionblockcodecolored" %)XWiki.XWikiSkins(%%), name it (% class="sectionblockcodecolored" %)mynewfile.css(%%) ( check the section [[B>>#5b]] for more information about how to work with this class ), edit the Skin document's objects ( use the top-left menu: (% class="sectionblockcodecolored" %)EDIT -> OBJECTS(%%) ), and paste the {{html}}<acronym title="Cascading Style Sheets">CSS</acronym>{{/html}} code into the (% class="sectionblockcodecolored" %)mynewfile.css(%%) field
220 1. override the (% class="sectionblockcodecolored" %)style.css(%%) component ( see the section [[D>>#5d]] for more information about how to override a Skin compoment ) and add the following line to the content of the (% class="sectionblockcodecolored" %)style.css(%%) property:(((
221 {{code language="css"}}
222 @import "mynewfile.css";
223 {{/code}}
224 )))the important thing is to add a reference to the new component from a existing one; you must know most of the components content, so that you will take the best decision about which existing component will contain a reference to the new one
225 1. save the document
226 )))|(((
Sorin Burjan 13.4 227 [[[[image:8.png||style="border: 3px solid rgb(221, 221, 221);" width="100%"]]>>attach:8.png]]
MariusButuc 11.1 228 )))
229
Raluca Stavro 1.1 230 Open any document in view mode and you will notice that the stylesheet is now applied.
231
hennejg 11.2 232 {{id name="5f"/}}
Sorin Burjan 13.4 233
hennejg 11.2 234 === F. Using (% class="sectionblockcodecolored" %)images(%%) in a Skin document ===
Sorin Burjan 13.4 235
hennejg 11.2 236 {{id name="5f1"/}}
Sorin Burjan 13.4 237
hennejg 11.2 238 ==== 1. Changing the (% class="sectionblockcodecolored" %)logo(%%) ====
Sorin Burjan 13.4 239
MariusButuc 11.1 240 For example, if you want to add an image named (% class="sectionblockcodecolored" %)myimage.jpg(%%) as being the logo for the current Skin, follow these steps:
Raluca Stavro 1.1 241
MariusButuc 11.1 242 1. attach the image to the Skin document
243 1. edit the document's objects ( use the top-left menu: (% class="sectionblockcodecolored" %)EDIT -> OBJECTS(%%) )
244 1. use the (% class="sectionblockcodecolored" %)XWiki.XWikiSkins(%%) object and set the (% class="sectionblockcodecolored" %)Logo(%%) property as being the name of the attached image: (% class="sectionblockcodecolored" %)myimage.jpg
245 1. save the document
246
Raluca Stavro 1.1 247 Open any page in view mode and you will notice that the logo is now changed.
248
Sorin Burjan 13.5 249 {{id name="5f2"/}}
MariusButuc 11.1 250
251 ==== 2. Adding images to the Skin interface ====
252
253 To add images to the interface, attach them to the Skin document and use them in the {{html}}<acronym title="Cascading Style Sheets">CSS</acronym>{{/html}} code. For example, if you want to use (% class="sectionblockcodecolored" %)myimage.jpg(%%) as background image for the pages inside your XWiki Enterprise instance, follow these steps:
254
255 1. attach the image to the Skin document
Sorin Burjan 13.4 256 1. choose one of these actions:
MariusButuc 11.1 257 1*. add a new {{html}}<acronym title="Cascading Style Sheets">CSS</acronym>{{/html}} component to the Skin, name it (% class="sectionblockcodecolored" %)pagebackground.css(%%) and add a reference to it from the (% class="sectionblockcodecolored" %)style.css(%%) component ( see the section [[E>>#5e]] for more information about how to add new components to the Skin )
258 1*. override the (% class="sectionblockcodecolored" %)mybaseskin.css(%%) component ( where mybaseskin is the name of the current Skin - for example: (% class="sectionblockcodecolored" %)albatross.css(%%), (% class="sectionblockcodecolored" %)toucan.css(%%) or (% class="sectionblockcodecolored" %)colibri.css(%%) )
259 1. paste the following code inside the {{html}}<acronym title="Cascading Style Sheets">CSS</acronym>{{/html}} component:(((
260 {{code language="css"}}
261 body{
Raluca Stavro 1.1 262 background-image: url($xwiki.getSkinFile("myimage.jpg"));
MariusButuc 11.1 263 }
264 {{/code}}
265 )))
Raluca Stavro 1.1 266
267 Open any page in view mode and you will notice that the the background of the page contains your image.
268 Have fun taking advantage of the power of XWiki Skins!
269
MariusButuc 11.1 270 == More about XWiki Skins ==
271
Raluca Stavro 9.1 272 In order to find more about XWiki Skins, check the [[Skins Tutorial>>AdminGuide.Skins]] from inside the Admin Guide and the [[Skins Tutorial>>Features.Skins]] from inside the User Guide
273
MariusButuc 11.1 274 == Further reading ==
Raluca Stavro 1.1 275
MariusButuc 11.1 276 * the [[XWiki Data Model>>http://platform.xwiki.org/xwiki/bin/view/DevGuide/DataModel]]
Vincent Massol 12.2 277 * using the [[Skin Editor Application>>extensions:Extension.Skin Editor Application]]
MariusButuc 11.1 278 * [[edit only one object>>http://dev.xwiki.org/xwiki/bin/view/Drafts/EditOneObject]]

About

About

Support

Platform

User Guide

Admin Guide

Developer Guide

Projects

XWiki

Extensions

Other

Contribute

Status

Practices

Under the Hood

Get Involved

Get Connected