Statamic Blueprints and Fieldsets: Complete Setup Guide

Organizing Content Fields with Blueprints and Fieldsets

Imagine migrating a project from WordPress to Statamic and facing chaos from ACF fields. You need to define 50+ fields for different post types, many of which repeat—SEO titles, OG images, custom blocks. In Statamic, this is handled through Blueprints and Fieldsets. Without a clear schema, you'll spend days manually copying, and changing one rule requires edits in a dozen places. We'll show you how to set up a blueprint scheme without pain, with reuse and built-in validation.

Problems We Solve

Manual Field Duplication

Without Fieldsets, each field must be written in every Blueprint anew. This leads to errors: one place forgets required, another has the wrong character_limit. A Fieldset centralizes logic: change a rule and it applies everywhere. On a project with 6 collections, this cuts content editing time by 40%.

Complex Content Blocks

The standard text editor doesn't work for landing pages with modules: hero, benefits, pricing. Bard with custom sets allows a flexible structure without resorting to ACF-like solutions. We configure typical sets: slider, benefits grid, pricing table—each with its own field schema.

Incorrect Validation and SEO

Without a clear schema, it's easy to miss a required image or Canonical URL. We bake validation (required, image, character_limit) at the Fieldset stage—errors are prevented. This reduces content publishing bugs by 60%.

How to Import a Fieldset Without Conflicts?

Take a real case: an e-commerce site on Statamic. Needed collections: products, categories, reviews, pages. All share a common SEO set. Create a seo Fieldset:

# resources/fieldsets/seo.yaml
title: SEO
fields:
  - handle: title
    field:
      type: text
      display: SEO Title
      instructions: If empty, uses the main title
      character_limit: 70
  - handle: description
    field:
      type: textarea
      display: Meta Description
      character_limit: 160
  - handle: og_image
    field:
      type: assets
      container: assets
      max_files: 1
      display: OG Image
      instructions: 1200×630px
      validate: [image]
  - handle: canonical_url
    field:
      type: text
      display: Canonical URL
  - handle: noindex
    field:
      type: toggle
      display: Hide from search engines
      default: false

Import it into the product Blueprint with the prefix seo_ to avoid conflicts with the product's title and description:

# resources/blueprints/collections/products/product.yaml
sections:
  main:
    fields:
      - handle: title
        field:
          type: text
          required: true
      - handle: price
        field:
          type: text
          validate: numeric
  sidebar:
    fields:
      - import: seo
        prefix: seo_

For reviews, the same SEO set but without prefix because there are only two fields: title and body. Import without prefix:

- import: seo

Changing one Fieldset automatically updates all Blueprints importing it. Add a field og_type and it appears in both products and reviews. In WordPress, you'd need to edit 5 ACF templates. Statamic does it in seconds.

Why Use Custom Fieldsets Instead of Copying?

Besides saving time, Fieldsets provide a single point of control. You can extend a set, change a field type, or add validation and it immediately reflects in all entries. On projects with 20+ content types, this is the only way to maintain order.

Our Process for Setting Up Blueprints

1. Content analysis—collect all entry types, their fields, nested blocks, required attributes.
2. Fieldset design—identify repeating groups (SEO, metadata, contacts, sliders).
3. Implementation—create YAML schemas, configure Bard sets, validation, imports.
4. Testing—verify CP behavior, correct saving, validation.
5. Deploy and document—hand over access and instructions for adding fields.

Timeline and What's Included

Setting up 5–8 collections with reusable Fieldsets takes 1 to 2 days. Includes:

• Creating Blueprint for each content type.
• Developing Fieldsets for SEO, common blocks (gallery, files, tabs).
• Configuring custom Bard sets (slider, benefits, pricing).
• Field validation: required, format, limits.
• Testing in CP and frontend.
• Documentation for editing fields.

Comparison: Statamic Fieldsets vs WordPress ACF

Typical Mistakes and Their Consequences

Our experience: over 20 projects on Statamic, including e-commerce sites, news portals, and corporate websites. We guarantee that the blueprint scheme will be flexible and scalable.

sets:
  pricing:
    display: Pricing
    fields:
      - handle: title
        field:
          type: text
          display: Plan name
      - handle: price
        field:
          type: text
          display: Price
      - handle: features
        field:
          type: list
          display: Features
      - handle: highlighted
        field:
          type: toggle
          display: Highlight

Contact us to assess your project and propose the optimal field structure within one day. Get a consultation on migrating from other CMS to Statamic. Statamic Documentation

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
5. Content migration (if legacy) — automated loading via API or scripts.
6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

• Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
• Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
• Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
• Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
• Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

• Data schema and API documentation (Swagger/OpenAPI)
• Configured admin panel with access rights
• Editor training (2‑hour session)
• Test environment during development
• 1‑month warranty on bugs after launch
• Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.