Themes can be used to kick start your SilverStripe projects, can be stored outside of your application code and your application can provide multiple unique themes (i.e a mobile theme).
Head to the themes section of the addons site to check out the range of themes the community has built. Each theme has a page with links you can use to preview and download it. Themes are normally published and downloaded using Composer, but may be available as archive files as well.
If a theme has Composer support you can require it directly through
composer require author/theme_name [version]
[version] should be replaced with a version constraint if you know it, otherwise leave it blank to pull the latest version compatible with your project.
As you've added new files to your SilverStripe installation, make sure you clear the SilverStripe cache by appending
?flush=1 to your website URL (e.g http://yoursite.com/?flush=1).
After installing the files through either method, update the current theme in SilverStripe. This can be done by
SSViewer.themes setting in a config.yml
SilverStripe\View\SSViewer: themes: - theme_name - '$default'
There are a variety of ways in which you can specify a theme. The below describe the three main styles of syntax:
You can use the following to point to a theme or path within your root project:
themename-> A simple name with no slash represents a theme in the
/prefixed string will be treated as a direct filesystem path to a theme root.
$prefixed name will refer to a set of themes. By default only
$defaultset is configured, which represents all module roots with a
:syntax you can also specify themes relative to the given module:
myvendor/mymodule:sometheme- This will specify a standard theme within the given module. This will lookup the theme in the
themessubfolder within this module. E.g.
/vendor/myvendor/mymodule/themes/sometheme. Note: This syntax also works without the vendor prefix (
myvendor/mymodule:/some/path- Rather than looking in the themes subdir, look in the exact path within the root of the given module.
You can also specify a module root folder directly.
myvendor/mymodule- Points to the base folder of the given module.
mymodule:- Also points to the base folder of the given module, but without a vendor. The
:is necessary to distinguish this from a non-module theme.
Unpack the contents of the zip file you download into the
themes directory in your SilverStripe installation. The
theme should be accessible at
Developing your own theme
SilverStripe 4 has support for cascading themes, which will allow users to define multiple themes for a project. This means you can have a template defined in any theme, and have it continue to look back through the list of themes until a match it found.
To define extra themes simply add extra entries to the
SilverStripe\View\SSViewer.themes configuration array. You will probably always want to ensure that you include
'$default' in your list of themes to ensure that the base templates are used when required.
Submitting your theme to addons
If you want to submit your theme to the SilverStripe addons directory then check:
- You should ensure your templates are well structured, modular and commented so it's easy for other people to customise
- Templates should not contain text inside images and all images provided must be open source and not break any copyright or license laws. This includes any icons your template uses.
- Your theme contains a
composer.jsonfile specifying the theme name, author and license, and that it has
Once you've created your module and set up your Composer configuration, create a new repository and push your theme to a Git host such as GitHub.com.
The final step is to submit your theme to Packagist (the central Composer package repository). Once your theme is listed in Packagist, and has
"type": "silverstripe-theme" in its configuration, it will automatically be pulled into our addons listing site.