Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Solarize Theme

The Solarize Theme is for Grav CMS. It's a port of Solarize by Templated under its CCA 3.0 license.

The Grav port includes an additional Elements page as per many Templated themes, to allow you to identify gaps in the theme's styling. There are a few.



Installing the Solarize theme can be done in one of two ways. Our GPM (Grav Package Manager) installation method enables you to quickly and easily install the theme with a simple terminal command, while the manual method enables you to do so via a zip file.

GPM Installation (Preferred)

The simplest way to install this theme is via the Grav Package Manager (GPM) through your system's Terminal (also called the command line). From the root of your Grav install type:

bin/gpm install solarize

This will install the Solarize theme into your /user/themes directory within Grav. Its files can be found under /your/site/grav/user/themes/solarize.

This method will copy the sample pages provided in the _demo/pages folder to your user/pages folder so that the theme will work out of the box with placeholder content. The content is the same Ipsum lorem content provided in the original Templated theme.

Manual Installation

To install this theme, just download the zip version of this repository and unzip it under /your/site/grav/user/themes. Then, rename the folder to solarize. You can find these files either on GitHub or via

You should now have all the theme files under


NOTE: If you want to use and adapt the default Ipsum lorem content provided with the original theme, move the contents of _demo/pages into your grav installations's user/pages directory. This will ensure that the theme templates work out of the box.


As development for the Solarize theme continues, new versions may become available that add additional features and functionality, improve compatibility with newer Grav releases, and generally provide a better user experience. Updating Solarize is easy, and can be done through Grav's GPM system, as well as manually.

GPM Update (Preferred)

The simplest way to update this theme is via the Grav Package Manager (GPM). You can do this with this by navigating to the root directory of your Grav install using your system's Terminal (also called command line) and typing the following:

bin/gpm update solarize

This command will check your Grav install to see if your Solarize theme is due for an update. If a newer release is found, you will be asked whether or not you wish to update. To continue, type y and hit enter. The theme will automatically update and clear Grav's cache.

Manual Update

Manually updating Solarize is pretty simple. Here is what you will need to do to get this done:

  • Delete the your/site/user/themes/solarize directory.
  • Download the new version of the Solarize theme from either GitHub or
  • Unzip the zip file in your/site/user/themes and rename the resulting folder to solarize.
  • Clear the Grav cache. The simplest way to do this is by going to the root Grav directory in terminal and typing bin/grav clear-cache.

Note: Any changes you have made to any of the files listed under this directory will also be removed and replaced by the new set. Any files located elsewhere (for example a YAML settings file placed in user/config/themes) will remain intact.

Supported Page Templates

Deferred assets block support

As explained in the Grav blog, since Grav 1.5.10 deferred blocks are supported and it will be standard to invoke assets rendering using these in the near future. For the page templates included, this theme does not require deferred asset blocks, and invoking a deferred asset block will crash a site running an older version of Grav.

Since v0.1.3 of this theme, it is simple to override the base template so that you can use a deferred asset block. In a template that extends partials/base.html.twig, simply add a deferred block called assets. For example:

{% extends 'partials/base.html.twig' %}

{# for example, add a custom javascript file #}
{% block javascripts %}
  {% do assets.addJs('theme://js/site.js') }}
  {{ parent() }}
{% endblock %}

{# then override the default non-deferred assets block with a deferred block, and optionally alter it #}
{% block assets deferred %}
  {{ parent() }}
{% endblock %}

If several of your templates require a deferred asset block, either:

  • create a common shared partial template, say partials/extended-base.html.twig with similar contents to the example above, and change your template files so that they extend this rather than partials/base.html.twig; or
  • modify a copy of partials/base.html.twig.


If you want to set Solarize as the default theme, you can do so by following these steps:

  • Navigate to /your/site/grav/user/config.
  • Open the system.yaml file.
  • Change the theme: setting to theme: solarize.
  • Save your changes.
  • Clear the Grav cache. The simplest way to do this is by going to the root Grav directory in Terminal and typing bin/grav clear-cache.

Once this is done, you should be able to see the new theme on the frontend. Keep in mind any customizations made to the previous theme will not be reflected as all of the theme and templating information is now being pulled from the solarize folder.

Examples in the wild

There's only one contrived one now :(

Please let me know if you want yours included (hey, it's free publicity).