Web skins

ticketmatic gives you full control over the look and feel of the websales widgets through webskins a webskin consists of a html template and a css stylesheet and allows you to decide on the main structure of the widget pages you can, among others decide where the main 'content' block will be placed on the page add headers, footers, sidebars and images decide where the wizard navigation buttons (previous, next) will be placed you can style all aspects of the widgets build on the structured css that is used in all widgets (bootstrap based), for easy styling use custom fonts use scss variables the widgets are all fully responsive, so with minimal effort you can create web sales for all devices and screens multilanguage webskins are supported all text in the webskin is easily translatable getting started set up a new web skin go to the https //apps ticketmatic com/#!/settings/websalesskins in the settings app and click on + add to create a new web skin a default html template and css will be created html {{tm account name}} {{tm page title | translate}} {{tm events\[0] name}} {{tm event\[0] startts | date 'medium'}} {{content}} {{previous}} {{next}} © 2015 {{tm account name}} css // override variables here // the line below should always be present @import "style"; // override css classes here this default webskin is fully functional and is a good base to start customizing the css and html preview and testing environment while you are editing a web skin, you will see the preview pane on the right displaying your changes in realtime you can select the page size to see how your web skin behaves on tablet and phone screens you can select several screens to check how your web skin looks for the different widgets and pages the pages you find here are generated from an actual test account, so the generated html is identical to the html generated in the actual websales but, as the websales widgets are highly dynamic and the content in your account will be different than the content from the test account, the preview pages can never show 100% of the use cases so, while the preview will give you a good indication of how your web skin will look, it is advised to test your web skin with an actual websales widget before putting it in production customizing the css in the css, you will see a single @import "style"; statement this statement is required and will load the default variables and css styles you will notice that the styling is based on http //getbootstrap com/ , so if you are familiar with this, you should be able to get up and running quickly there are 2 main ways to customize the css https //app archbee com/docs/ks phzcjwi8f43fzmpows/ak0zbe5ivco4nb1rotthm#v4mtf https //app archbee com/docs/ks phzcjwi8f43fzmpows/ak0zbe5ivco4nb1rotthm#jjvgz 1\ define scss variables an easy way to customize a web skin is by defining values for (part of) the scss variables that are used throughout the standard stylesheets bootstrap defines a list of variables that can be used, for example $brand primary or $link color , and ticketmatic adds some ticketmatic specific variables like $tm header background try the example css below / color definitions \========================================================================== / $blue lighter #bcd6ea; $blue lightest #ecf3f7; $blue light #85b5d9; $blue #09b3df; $red #d54026; $red light #ec9f92; $brown #60220e; $white #fff; / bootstrap variable overrides \========================================================================== / $table bg accent lighten($blue light,20%); $brand primary $red; $well bg mix($blue light,$blue lightest,20%); $well border mix($blue light,$blue lightest,20%); $table border color $blue light; / ticketmatic specific variables \========================================================================== / $tm header background $white; $tm content background $blue lightest; $tm action buttons background $blue light; $tm btn previous #fff; $tm btn next #fff; $tm tfoothead top border $table border color; $tm tfoothead border $table border color; $tm cart total top border darken($table border color, 20%); $addtickets remove ticket count true; // seatingplan specific $tm seat selected #d9534f !default; $tm seat available #fff !default; $tm seat available stroke #8c96a5 !default; $tm seat unavailable #8c96a5 !default; $tm seat inactive lighten($tm seat unavailable, 20%) !default; @import "style"; you see that we first define some skin specific variables representing colors these variables are then used to overrule the standard values $brand primary $red; will set the brand primary color to $red or #d54026 you can also use sassscript in the css for example to modify a color using the lighten function $table bg accent lighten($blue light,20%); http //sass lang com/documentation/sass/script/functions html there is a long list of bootstrap variables that can be overruled http //getbootstrap com/customize/#less variables also some ticketmatic specific variables are set you can recognize these by the tm prefix these are the ticketmatic specific variables variable description $tm header background background color for the header $tm action buttons background background color for the content block $tm action buttons background background color for the action buttons $tm btn previous color for previous button $tm cart total top border $tm tfoothead top border $tm tfoothead border $addtickets remove ticket count boolean value indicating whether the ticket count should be shown in the addtickets widget $tm seat available seatingplan specific, color for a seat that is available $tm seat available stroke seatingplan specific, stroke color for a seat that is available $tm seat unavailable seatingplan specific, color for a seat that is unavailable $tm seat selected seatingplan specific, color for a seat that is selected $tm seat inactive seatingplan specific, color for a seat that is inactive $tm authentication background authentication widget background color $tm authentication logo authentication widget logo note that you should include the variables you want to customize before the @import "style"; command 2\ override the css classes to further customize the web skin, you can override the css classes used in the html the html used in the widgets is based on bootstrap and we try to apply the bootstrap conventions as much as possible in addition, we added a list of ticketmatic specific semantic css classes to the widgets for example body { background #c1d9ed url("/images/bg grad jpg") repeat top center; } tm wrapper header { background url(/images/shine png") no repeat top center; } this css will set a background image for the body, and an additional background image for the tm wrapper header you can use the developer tools of your favourite browser to inspect the html in the preview pane to find out the css classes used in the widgets note that you should include the classes you want to customize after the @import "style"; command customizing the html the html in a web skin contains all html structure inside the body tag, and can completely be customized you will notice a few placeholders in upper case {{content}} , {{previous}} and {{next}} these 3 placeholders should always be included in the html template by wrapping them in divs, you can position and style them any way you like {{content}} will be replaced by the actual widget content {{previous}} will be replaced by the wizard button previous {{next}} will be replaced by the wizard button next you will also notice other (lower case) placeholders like {{tm account name}} or {{tm page title}} these placeholders are interpreted at run time in the browser and are actually regular angularjs expressions these placeholders are optional and can be used by use to display dynamic information about the account, order or event in the skin we provide the following placeholders placeholder description tm account tm account id account id tm account name account name tm page tm page name the name of the page (= the identification) tm page title the language sensitive name of the current page tm page label a one word label for the current page (useful for titles) tm events tm events\[x] name event name tm events\[x] subtitle event subtitle tm events\[x] startts event startdate tm events\[x] endts event enddate tm events\[x] locationname event location tm events\[x] webremark event webremark tm events\[x] c customfield1 all event custom fields are also available tm order tm order nbroftickets number of tickets in the order tm order totalamount total amount for the order other tm year the current year (useful for copyright notices) tm currency symbol the currency symbol used use this with a currency filter to get correct monetary formatting tm returnurl a signed returnurl containing the orderid and contactid (if specified) the reason for the return is skin placeholders often used in combination with angularjs filters or directives some examples //put the event name in uppercase {{ tm events\[0] name | uppercase }} you can use https //docs angularjs org/api/ng/filter/date when formatting a date //format a date {{ tm events\[0] startts | date 'eee dd/mm hh\ ss'}} the https //docs angularjs org/api/ng/directive/ngif can for example be used to display the subtitle only when it is filled in \<h2 ng if="tm events\[0] subtitle">{{ tm events\[0] subtitle }}\</h2> //display the total amount in the correct currency {{ tm order totalamount | currency\ tm currency symbol }} https //docs angularjs org/guide/expression working with images you can use images in the html you can link to an external url (should always be https) or upload the image in the https //apps ticketmatic com/#!/settings/assets in the settings app and link internally if an image with the name logo png is uploaded in assets in the images folder it can be loaded in the webskin with the following html \<img src="images/logo png"/> using ticketmatic specific css classes in the html ticketmatic provides a few custom css classes that can be used in the html class description tm visible event if used on a div, the content inside the div will only be visible if an event is active for the current wizard tm hidden event if used on a div, the content inside the div will only be visible if an event is not active for the current wizard translating the web skin ticketmatic supports fully mulitlingual web skins click on translate in the top menu to access the translation module you will see that all default web skin strings are listed and can be translated or customised you can also translate text that you added yourself in the web skin you should annotate it with a translate attribute for example text to be translated and in order to make dynamic placeholders translatable, use the translate filter {{tm page title | translate}} web skin settings you can modify web skin settings on the settings tab setting description favicon the favicon to be used for the wizard you should refer to an icon in the assets here page title the page title to be used for the wizard you can use dynamic placeholders in the page title, for example {{tm page label }} {{tm account name}} google tag manager id an id (formatted like gtm xxxxxx) that activates a google tag manager container on websales docid 2mebiiry wtpnswdclji typekit id the id of your typekit account (if any) this enables you to use custom fonts facebook pixel id the facebook pixel id for user tracking