menu-btn

Creating Blueprints

Creating Blueprints

Define a Team Members content type and a settings global

Let's create two blueprints: an entry blueprint for team members and a global blueprint for team page settings. Together, they will give us a complete content type with a backend form and configurable display options.

# Create the Team Member Blueprint

  1. In your theme's directory, create a blueprints folder if it doesn't exist.
  2. Create a new file at themes/mytheme/blueprints/team/member.yaml.
  3. Paste the following:
handle: Team\Member
type: entry
name: Team Member

fields:
    role:
        label: Role
        type: text
        span: auto
    email:
        label: Email Address
        type: text
        span: auto
        validation: email
    photo:
        label: Photo
        type: fileupload
        mode: image
        span: auto
    bio:
        label: Bio
        type: textarea
        size: small
        span: full

This blueprint defines a team member with a role, email address, photo, and short bio. Tailor automatically adds title and slug fields to every entry blueprint, so we don't need to define those.

You can organize blueprint files in any folder structure you like, such as blueprints/team/member.yaml, blueprints/member.yaml, or even blueprints/my-stuff/team-member.yaml. Tailor finds them by handle, not by file path.

# Create the Team Settings Global

Now create a global blueprint to control how the team page behaves. Create a new file at themes/mytheme/blueprints/team/settings.yaml:

handle: Team\Settings
type: global
name: Team Settings

fields:
    page_title:
        label: Page Title
        type: text
        default: Meet the Team
    introduction:
        label: Introduction
        type: textarea
        size: small
    show_photos:
        label: Show Profile Photos
        type: switch
        default: true
        comment: Toggle whether team member photos are displayed on the team page.
    per_page:
        label: Members Per Page
        type: number
        default: 6
        comment: How many team members to show per page before pagination kicks in.

This global provides settings we will use when building the frontend: the page title, an intro paragraph, a toggle for profile photos, and a pagination control.

# Run the Migration

After creating blueprints, you need to run a migration so Tailor can set up the database tables:

php artisan tailor:migrate

Or with DDEV:

ddev artisan tailor:migrate

This reads your blueprint files and creates the necessary database structure. Run this command every time you add or modify a blueprint.

You can also migrate blueprints from the Editor. When editing a blueprint file in the backend, click the Save & Migrate button to save your changes and run the migration in one step.

# Verify in the Backend

Log into the backend and look at the navigation. You should see new entries for Team Member and Team Settings under the Content menu. Click into each one to see the forms Tailor generated. They match the fields you defined, with no code written.

# Next Steps

Your blueprints are ready. Continue to Managing Entries to add some team members and customize how they appear in the backend.

For the complete blueprint reference, see Blueprints in the developer documentation.

← Managing Entries →