File Structure

The Email Manager organizes email forms using Kirby’s conventions, separating configuration (Blueprints) and rendering (Templates).

Blueprint

Blueprints define the configuration for each email form and are stored in site/blueprints/emails. Each form requires its own YAML file, named according to the form (e.g., contact-form.yml).

Templates

Templates are stored in site/templates/emails. Each form has its own directory, named identically to its blueprint (e.g., contact-form/).

The mail.text.php file is required and defines the notification sent to the form recipient, such as the site administrator. If a reply.text.php file is present and the blueprint contains a defined email field, automated responses will also be sent to the form submitter.

Optional *.html.php files can be added for both mail and reply templates to provide richer formatting, but are not mandatory.

Only text templates are required. HTML templates are optional.

Example

site
- blueprints
  - emails
    contact-form.yml
- templates
  - emails
    contact-form
    mail.html.php
    mail.text.php
    reply.html.php
    reply.text.php

The naming convention ensures that Blueprints and Template directories are always clearly linked, allowing you to quickly locate and manage form-specific configurations and templates.

Each form’s blueprint and template directory must have the same name, ensuring a clear and consistent structure.