- Blueprints are stored in
- Blueprints configure the Panel layout of the site, pages, files and users.
- Create your own layouts with tabs, columns and sections.
The Panel layouts for
users all get their own blueprints. The blueprint folder is structured accordingly:
The start page (Dashboard) of the Panel is defined in the
When your project requires more elaborate setups, you can be the interface designer. You decide which features are needed for each type of page, file or user and how to arrange them in tabs, columns and sections.
With fields you can break up your content into digestable chunks and structure it according to your content model, rather than storing everything in a huge text field. You can add as many fields of different field types as you need.
Kirby comes with a blueprint query language that offers basically the same functionality as Kirby's PHP API with a simple dot notation.
You can store fields, sections, tabs and entire blueprint layouts in separate files so that they can be reused within your blueprints. If you want, you can even create a complete component system to apply to multiple projects.
For editors from various language backgrounds, you can translate blueprint titles, form field labels, section labels, help text, options, and more.
We have put together an extensive collection of example blueprints for typical setups like a blog, a shop, a project portfolio and more for you to use as a basis for your own.
Our reference has more in-depth documentation about blueprints and their different components.
To use special characters in labels etc., wrap the text in double quotes:
Make sure to only use alpha-numerical characters and underscores in field names. You cannot use dashes.