Child pages
  • Theming
Skip to end of metadata
Go to start of metadata

CORE allows you to completely customise the look and feel of a conference.

TODO: explain concept of "CORE", "other content", and "navigation".

Custom layout

Let's assume that your conference has the abbreviation myconf.

1. Stylesheets, images, javascript

All of the publicly accessible files for your layout should be stored in a subdirectory of public/includes.
This folder must have the following structure:


You can start by copying the supplied 'democonf' folder:

cp -r public/includes-templates/democonf public/includes/myconf

2. (X)HTML templates

Copy the 'democonf' layout directory as a starting point:

cp -r application/layouts-templates/scripts/democonf application/layouts/scripts/myconf

3. Activate the layout

To to this, select the custom layout option for your conference in the conference manager.

Different navigation

It is possible to change the navigation buttons.

1. Configuration file

Create a navigation configuration file in application/config/navigation/.
The name should be <abbreviation>.php, so in this case that would be application/config/navigation/myconf.php.
You can start by copying the supplied democonf configuration file:

cp application/configs-templates/navigation/democonf.php application/configs/navigation/myconf.php

Your navigation file should always return an array. The syntax of the array elements can be found in the Zend docs.

2. Activate navigation

Select the custom navigation option in the conference manager.

The example config uses different content as well, so read on.

Extra content

For new content you need to add a new module.

You can copy the "webdemo" module:

cp -r application/modules-templates/webdemo application/modules/web

E-mail templates

CORE allows you to send automatically generated emails. For example, the submit feature allows you to send an email to all reviewers of certain papers. This e-mail is generated from two templates. A dynamic template which is generated by CORE and a static template which can contain text, like signature, disclaimers etc. The static e-mail template will be appended to the CORE generated e-mail template.
The name of the static e-mail template is always: abbreviation-<action>.phtml, so for example myconf-reviewers.phtml is located in: application/modules/core/views/emails/