Tintamarre Theme for the CMS Grav
Table of Contents:
See the Tintamarre Template live here
- Fully Responsive
- HTML5 and CSS3
- Contact Form
- Multilingual ready - (demo in
- Custom Error page
Basic Setup for a new Grav site
The simplest way to install Tintamarre Theme for Grav is to download and install the Tintamarre Skeleton package:
- Download Tintamarre Skeleton on Grav or the latest release on GitHub.
- Simply unzip the package into your web root folder.
- Point your browser at the folder, job done!
TIP: Check out the general Grav installation instructions for more details on this process.
Existing Grav site
Installing the Tintamarre Theme can be done in one of two ways. Via 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.
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 tintamarre
This will install the Tintamarre Theme into your
/user/themes directory within Grav. Its files can be found under
NOTE: for the Skeleton version, please see: Skeleton - TO COME
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
tintamarre. You can find these files on GitHub.
You should now have all the theme files under
As development for the Tintamarre 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 Grav 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 tintamarre
This command will check your Grav install to see if your Tintamarre 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.
Manually updating Agency is pretty simple. Here is what you will need to do to get this done:
- Delete the
- Download the new version of the Bootstrap Theme on GitHub.
- Unzip the zip file in
your/site/user/themesand rename the resulting folder to
- Clear the Grav cache. The simplest way to do this is by going to the root Grav directory in terminal and typing
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.
If you want to set Tintamarre as the default theme, you can do so by following these steps:
- Navigate to
- Open the system.yaml file.
- Change the
- 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
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 tintamarre folder.
You can find inside theme directory the folder
_demo where you can find the example contents for your site. If the theme is one-page layout copy all files inside
_demo/pages into your home page folder. For the other folders follow the same name.
You want to share your site build with Tintamarre? Feel free to add your site here...
Support & Bugs
- If you find bugs, please report them on here
- Grav by RocketTheme. Licensed under MIT
- Photos by MATsxm for IDIMweb.com. Licensed under BeerWare (see LICENSE)
- Inspired by the template Magister by Sergey Pozhilov
Note that @Sandra97 has never been involved in the CSS excepted for having killed few !important;