Download the PHP package oblik/kirby-variables-field without Composer

kirby-variables-field

Kirby field that allows you to manage langauge variables via the panel. To do that, it uses kirby-variables to put those variables in YAML files so they're easy to work with.

⚠ Deprecated

You gain very little by putting variables in separate files and managing them differently to other fields. It's much easier to just use text fields. For details, check the deprecated oblik/kirby-variables package.

Installation

With Composer:

Usage

In a blueprint, simply add a new field and set its type to variables:

This will create an editor for all variables where you can add, remove, and sort them.

Note: This is a "fake" field and no actual value will be saved in the site/page txt file. All values are saved in the YAML files where the variables reside so it doesn't matter what field name you choose.

Options

variable

You can specify exactly which variable you want to be editable. For example, if you have this in bg.yml:

...and this in your blueprint:

...you'll get the following result:

In the case above, if you want editors to be able to add new entries in the greetings group, you can simply change:

...to:

This will show the variable editor instead.

editor

When you haven't set a specific variable to edit and the editor is shown, you can configure it:

This plugin uses the JSON editor Vue component provided by the kirby-json dependency. Read what blueprint options it has here.

KirbyTag

This plugin also comes with a KirbyTag called var. It simply outputs a variable with a fallback default value. For example, in en.yml:

In your content:

Result:

This is useful because editors now can both set and use variables in the panel, which gives them the option to avoid repeating themselves in the content.