Skip to content
The OpenCms Apollo Template
Branch: branch_10_5_x
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
.settings/gradle Added Gradle settings. Nov 25, 2015
apollo-src Updated Apollo module version numbers to 10.5.1. Feb 19, 2017
org.opencms.apollo.template.disqus/resources Updated Apollo module version numbers to 10.5.1. Feb 19, 2017
org.opencms.apollo.template.event/resources Updated Apollo module version numbers to 10.5.1. Feb 19, 2017
org.opencms.apollo.template.imagegallery/resources Updated Apollo module version numbers to 10.5.1. Feb 19, 2017
org.opencms.apollo.template.imgur Updated Apollo module version numbers to 10.5.1. Feb 19, 2017
org.opencms.apollo.template.job/resources Updated Apollo module version numbers to 10.5.1. Feb 19, 2017
org.opencms.apollo.template.linksequence/resources Updated Apollo module version numbers to 10.5.1. Feb 19, 2017
org.opencms.apollo.template.shariff/resources Updated Apollo module version numbers to 10.5.1. Feb 19, 2017
org.opencms.apollo.theme/resources Updated Apollo module version numbers to 10.5.1. Feb 19, 2017
.gitignore Reorganized module structure. Apr 15, 2016
Gruntfile.js Added --mapscss option to grunt build. Jan 1, 2017 Updated Dec 1, 2016
build.gradle Reorganized module structure. Apr 15, 2016
dependencies.gradle Fixed changed dependency path. Jan 10, 2017
grunt-opencms-modules.js Fixed issue in css path generation - Grunt Build. Feb 2, 2017

The OpenCms Apollo Template

A full-featured, customizable, great looking responsive template for OpenCms

The Apollo Template for OpenCms is a complete, modular template for OpenCms. It is based on Boostrap and allows you to create even complex grid-layouts with drag&drop. It packs a ton of CSS features and JavaScript plugins that have carefully been integrated to be simple to use for the content manager. And it ships with all Java and SASS sources so you can fully customize it for your unique requirements.

Main Apollo features

  • Powerful content section element that can be formatted in many ways to place text, images or a combination thereof everywhere on a page.
  • Create simple or complex grid-layouts via drag & drop using the layout row element.
  • Slider module that allows the content manger to create simple or advanced slideshows.
  • Blog / News module that supports tags, all kind of sort options as well as archive display.
  • Form element that allows you to create even complex email forms without a single line of code.
  • Disqus comments function that can be placed on any page.
  • "Share with social media" element based on Shariff.
  • Image gallery module that optionally loads more images when the user scrolls.
  • Google Maps element, including API key support.
  • Contact / Person information element with hcard microformat generation.
  • Flexible content element that can be used to place any kind of HTML or JavaScript markup on a page.
  • Full featured search function with support for categories, facets and "did you mean" suggestions in case of misspellings.
  • Support for head menu and / or sidebar navigation.
  • Event / Calendar module.
  • FAQ module.
  • Job advertisement module.

Each of the above functionality can be placed on a web page using OpenCms unique drag & drop mechanism. Many of the elements include multiple format options and can create dozens of output variations.

For the technical minded here are some more background facts about Apollo:

  • SASS sources CSS gurus can style the complete HTML output with individual CSS-themes using Apollos SASS and Grunt infrastructure.
  • All minified Apollos Grunt build process minifies all CSS and JavaScript into a single file to give website visitors the best page loading performance.
  • Source maps provided Apollo provides full CSS and JavaScript source maps so you can view the all original sources when viewing the page in Chromes dev tools or Firebug.

The Apollo Template is shipped as demo website directly with the main OpenCms download. So if you have installed OpenCms you also have Apollo directly available.

More background information about the use of the elements of the Apollo Template is available in the OpenCms Documentation.

Customizing Apollo from source

The rest of this page deals explains the technical process of how to customize the template from source. This is required only if you require full control of all aspects of the HTML / CSS being generated.

Structure of the repository source files

This repository contains all the Apollo OpenCms modules. These are located in the folders starting with ./org.opencms.apollo. Here you find all JSP and Java sources. The structure of these folders is required by OpenCms.

The template's static resources, i.e., CSS, JavaScript, fonts and images are all bundled in the module org.opencms.apollo.theme. Here you find all CSS and JavaScript sources combined in one minified CSS file (per theme) and one minified JavaScript file.

The minified CSS and JavaScript files are generated from the resources under apollo-src.

Building the Apollo OpenCms modules

Apollos modules are built using Gradle. The interesting targets are:

  • dist_{module name} to build a single module (includes building the module's JAR if required)
  • jar_{module name} to build only a modules JAR
  • bindist to build all modules

The module org.opencms.apollo.template.democontents contains a complete web site built with the Apollo Template. It serves as demonstration of the various content elements that are part of the template.

The OpenCms Documentation has more details about the general process required to build general OpenCms modules. Here we want to focus on the special way the Apollo CSS / JavaScript sources are build.

Building the Apollo CSS and JavaScript

To customize the template, you can add or change files under apollo-src and then use SASS / Grunt to compile the sources and place the results in the org.opencms.apollo.theme module.

To create Apollos CSS and JavaScript resources from source, you need to setup a compile environment with SASS and Grunt. There are many articles available in the web on the details on how to setup such an environment, so we will provide only some brief details about the process here. We will assume that you have the basic environment already in place here.

Of course, you need to check out this repository first. Then run

sudo npm install

to install all dependencies required to compile the template's sources.

Once all dependencies are installed, you can trigger the compilation by running


in the repository's root folder. To get more detailed output, you can use the option -v.

After running grunt, the repository will have a new folder ./build/grunt/ with three sub-folders. The sub-folder 03_final/ contains the final CSS and JavaScript resources that you can copy to the org.opencms.apollo.theme module. The result has to be copied to the folder /system/modules/org.opencms.apollo.theme/resources/.

You can also set the environment variable OCMOUNTS to point to a folder where the compilation result should be copied to. The intention is to mount the VFS of the OpenCms installation you develop on and set OCMOUNTS to point to the mount point. Then the CSS and JavaScript sources are updated automatically in the installation and you can see your changes in action.

The Grunt infrastructure of the template is special in the way that we have split our Gruntfile.js into several subfiles. The include grunt-opencms-modules.js registers the main Grunt tasks, and then loads several Gruntparts.js files that add CSS, SCSS, JavaScript or static resources that are processed for the output.

Customizing Apollos CSS

The Apollo Template uses CSS themes. In OpenCms you can configure which theme to use by setting the property apollo.theme. By default, the themes style-blue and style-red are available.

Our Grunt process generates exactly one minified CSS file (with source map) for each theme.

Both themes (red and blue) available by default are minimal in the way that they only define the mandatory variables $main-theme, $main-theme-hover and $main-theme-additional. Moreover, they import all common style files located under ./apollo-src/scss/.

To write your own theme, add an .scss file in the folder ./apollo-src/scss-themes/, e.g., style-custom.scss.

Important: To get your theme compiled by Apollos Grunt build process, you must add it in the file ./apollo-src/css-themes/Gruntparts.js in the export.themes array.

The simplest adjustment to do in your theme is to change the color values of $main-theme, $main-theme-hover and $main-theme-additional, but you can overwrite any of the variables defined in one of the .scss files under ./apollo-src/scss/. Of course, you can also add your own variables and style definitions.

Customizing Apollos JavaScript

Our Grunt process generates exactly one minified JavaScript file (with source map) that is shared by all generated CSS themes.

You can add your own JavaScript by adding a file script-*.js to the folder ./apollo-src/js. Of course, you can also modify the files found there according to your requirements.

Customizing Apollos plugins

Apollo uses several Plugins. A plugin usually consists of a collection of CSS, JavaScript and static resources such as images.

Our Grunt process automatically adds the plugin CSS sources to each generated CSS theme and the plugin JavaScript sources to the generated JavaScript file. Also the required static resources are copied to the output folder.

The most important plugins used by Apollo are Bootstrap, jQuery and Font Awesome. These have their own folders in the top level of the project. All other plugins are located in the ./pluginsfolder.


The Apollo template is copyright (c) by Alkacon Software GmbH & Co. KG

This template is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This template is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.

See for the full text of the GNU Affero General Public License.

You can’t perform that action at this time.