• theme’s branding
• administration panel branding

Thanks to theme’s branding options, a user may specify:

• specify page’s logo
• specify theme’s footer content
• decide about displaying a framework logo under page’s footer

More information about branding options for a theme can be found in an entry devoted to a “Theme branding” tab in an administration panel.

Administration panel branding options allow to define:

• a logo displayed next to a theme’s name in an administration panel sidebar
• a logo visible over a log in form to an administration panel

More about branding options for an administration panel can be found in an entry devoted to “Back-end branding”  in an administration panel.

• displaying on subpages chosen,
• displaying on devices chosen,
• displaying for a group of users chosen,
• displaying with a widget style use chosen.

After switching on widget rules in theme’s advanced settings, under each widget, the following options should be displayed:

The most extensive options are those connected with a widget visibility on subpages chosen – after choosing an option to show a widget on pages chosen (or an option not showing a widget on pages chosen), such a panel will appear:

Then, you have to choose a page’s type to add, e.g. Category, and then give category ID:

After clicking “Add page” button, a page will appear on a list of pages chosen on which in our case a widget will be displayed:

Of course, it is possible to add more pages:

To make it clearer, , each page’s type is displayed with a different color. A page added can be removed by clicking a removing icon placed on the right side of each page.

In this way, you may set a widget so as to be shown on pages chosen or to be shown on all pages except the chosen ones.

Generally, widgets are shown on all pages.

An option of displaying a widget on devices chosen has five options to choose:

• All devices – a widget will be displayed everytwhere – on every device
• Desktop – a widget will be displayed only when neither a tablet.css file nor a mobile.css is loaded
• Tablets – a widget displays only when a tablet.css file will be loaded and, at the same time, a mobile.css file will not be loaded
• Smartphones – a widget will be displayed only when a mobile.css file will be loaded
• Tablets/Smartphones – a widget will be displayed when at least one file will be loaded: tablet.css or mobile.css.

Thanks to these settings, it is possible to limit significantly the amount of content displayed on devices with small screens.

An option of displaying widget for a chosen groups of users has four options to choose:

• All users – a widget will be displayed to all users
• Only guests – a widget will be displayed to not logged in users
• Only registered users – a widget will be displayed to logged in users only
• Only administrator – a widget will be displayed to administrators only

Thanks to this option, it is possible e.g. to display messages specified by using widgets for a group of users chosen.

The last optio from widget rules is an option for choosing a widget style – it causes appending to a widget main container an additional class giving styling specified by a user.

Widget styles are defined in widget.styles.json file and in CSS code – in this case in css/wp.extensions.css.

All additional subpages styles are placed in a main catalog in template.*.php files. GavernWP has the following subpages:

• template.archive.php – an archive page, in includes a list of recent posts, categories and a list of links to monthly archives.
• template.contact.php – a page with a contact form which allows to send an email to an email address specified in a WordPress configuration.
• template.fullwidth.php – a page’s layout without a sidebar.
• template.gallery.php – a page generating an animated gallery of images with a mechanism of attachments available in WordPress – it is enough to assign attachments to such a page that they will show as slides in a gallery. It is recommened to choose images with the same size.
• template.login.php – a page generating a login form for users – after logging in, it displays information about his/her username and a button to log out.
• template.tagcloud.php – a page generating a tag cloud of our website.

Main CSS styles of subpages are in a css/stuff.css file. However, you have to remember that some more extensive files of subpages may additionally load CSS and JavaScript files from css/templates/ and js/templates/.

In order to load additional files in this way, it is enough to specify the second parameter of a gk_load function (see: code of requesting a gk_load function in a template.gallery.php file).

All options connected with comments configuration can be set by using standard options in a WordPress administration panel (Settings > Discussion). Threads in comments are switched on thanks to “Enable threaded (nested) comments” and specifying maximal depth of nested comments in threads.

There are two files responsible for generating HTML code of comments, namely:

• comments.php – it includes a code which generates a comments list and a form of adding comments.
• gavern/helpers/helper.layout.fragments.php – in gavern_comment_template function, there is a code responsible for generating a code of a comment given.

CSS code responsible for a style of comments and a form of adding comments is in css/wp.css file.

At the moment, Social API supports four services:

• Facebook
• Google+
• Twitter
• Pinterest

Buttons for sharing are generally added under an entry. All contact data needed for sharing are loaded from entry content or from OpenGraph metatags.

Thanks to extensive configuration options, it is possible to adjust buttons look in accordance with available configuration parameters.

The most important thing is that the work of Social API can be limited to specific posts or switch off some posts from its work.

Switching on support for Open Search requires switching on one option in an administration panel in a tab of advanced settings. All other operations are made with GavernWP.

• tablet.css
• mobile.css

Thanks to options available in an administration panel, it is possible to specify when these styles will be loaded.

Two column layout (if a column is switched on) is loaded when tablet.css file is not loaded.

At the moment of reaching maximum width for tablet.css file, page’s layout is changed into one column and the column itself is placed before or after page’s main content.

Additionally, in widget positions like top or bottom1/2/3, modules from three column layout are changed into one column  layout.

After loading mobile.css file there is one column layout used everywhere.

A very important improvement is a possibility of specifying whether a module will be loaded in tablet or mobile mode. More information can be found in Widget Rules entry.

• style family
• styles included in style family given

The whole configuration is included in styles.json file:

[{
"family": "color",

"family_desc": "Theme color",

"family_tooltip": "You can select one of the theme colors",

"styles": [

{

"name": "Color I",

"value": "color1",

"file": "style1.css"

},

{

"name": "Color II",

"value": "color2",

"file": "style2.css"

}

]

}]

As you can see, it includes color style family which has two styles, namely: Color I and Color II.

In order to create new style family or a style for style family given, it is enough to create a next object in styles.json file and then create CSS files connected with a family given – in the case of color family, these are style1.css and style2.css files.

GavernWP will load CSS files of a style given in a head section – chosen in an administration panel or, if there is a tool for choosing user’s styles switched on, they will be loaded based on a Cookie file storing data about a style used by a user.

You have to remember that for each style family there is at least one CSS file loaded. Therefore, creating coexisting style families like:

• dark styles and light styles
• blue styles and green styles

is incorrect because at least one CSS style from each family will be loaded immediately. So the correct one is creating style families responsible for some elements of website styling, e.g. a separate family responsible for website coloring (colors) and a separate one for website background (patterns).

Generally, you have to care about particular style families in order not to overwrite one another.

• title
• entry description
• thumbnail connected with an entry

Thanks to it, an author of a post has better influence on the information displayed on social media services. It’s also worth remembering that in the case when fields connected with Open Graph will not be filled, then GavernWP will try to fill them automatically basing on the entry data.

Support for Open Graph is a great supplement for a Social API system implemented in GavernWP.

You may find files responsible for theme’s configuration in gavern/options/ catalog:

• fonts.json – a file which stores theme’s groups of fonts. By default, there are three main gropus created. In order to create a new group, it is enough to add a next object to the object table existing in this file.plik przechowujący grupy czcionek szablonu.
• menus.json – you will find space for menu used in a theme in this file. You have to remember that except adding a new object, you have to add PHP code generating menu data in theme’s code. It is also worth remembering that there could be one main menu (main field in menu object).
• opengraph.json – this file includes configuration of fields used in a block connected with metabox which is used for generating Open Graph data. We do not recommend to make any changes in it before you get acquainted with Open Graph tags implementation in GavernWP framework.
• styles.json – this file is used for generating additional theme’s styles. Except adding a new style, you have to remember about creating an additional CSS file which will be loaded while changing theme’s style.
• template.json – it is the most important configuration file. It includes information about a theme and it allows to switch off chosen elements of theme administration panel. It is NOT recommended to add new fields to this files because they will not be used without additional PHP code.
• widgets.json – a file including a list of all positions of widgets. Similarly to menus.json file, you have to remember that except adding a new widget position, you have to also add PHP code which generates it in a theme.
• widgets.styles.json – a file used for creating new widget styles. Thanks to its implementation, it allows to assign a style given to one widget type only or exclude some widget types from a style given.

In order to understand better JSON files format, we recommend to visit the official website of  this format.