The Timeline-plugin is for Grav CMS, and lets you create and manage timelines in an ordered, hierarchical fashion. Timelines can be nested within each other, minutely customized on a page-level, and further customized with your own templates and styles. A demo is available, and demo content can be found in /pages.
Installing the Timeline-plugin can be done in one of two ways. The GPM (Grav Package Manager) installation method enables you to quickly and easily install the plugin 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 plugin 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 timeline
This will install the Timeline-plugin into your
/user/plugins directory within Grav. Its files can be found under
To install this plugin, just download the zip version of this repository and unzip it under
/your/site/grav/user/plugins. Then, rename the folder to
timeline. You can find these files on GitHub or via GetGrav.org.
You should now have all the plugin files under
Before configuring this plugin, you should copy the
user/config/plugins/timeline.yaml and only edit that copy.
Here is the default configuration and an explanation of available options:
enabled: true language: en order: by: date dir: asc cache: native truncate: 100
Settings and Usage
||Enables or disables the plugin.|
|language||en||string (2)||Any two-letter (ISO-639-1) language code.|
||Orders pages according to date, title, or folder-name.|
||Order pages ascending or descending.|
||Where to store plugin's internal data.|
|truncate||100||int or boolean||Limits the amount of words in each note, to an integer or boolean state for default (100).|
Each timeline is structured with a Header (
timeline.md, Timeline-template) and Events (
timeline_event.md, Timeline Event-template). Headers are used as separators and can order their descendant Events, as well as contain normal fields such as
content. Events also render a formatted, localized
locale), as well as an
image. In addition, Events are cast as Linked Data with JSON-LD, wherein
region are used.
Sound confusing? It's much easier to do all this from the Admin-plugin: