ProcessWire Fields and Templates: Setup, Types, Optimization Tips

Fields and templates are the foundation of any ProcessWire project. Incorrect structure leads to patching holes: twisted relationships, duplicate data, slow N+1 queries. For example, in one project without proper FieldtypePage configuration, we had to run 15 queries instead of one, increasing TTFB by 400 ms. Designing fields pays off tenfold: development accelerates by 30–50%, and maintenance becomes simpler. We have accumulated experience on 15+ projects, and each time the right architecture saved the client at least 40 hours of initial work. Contact us for a consultation on your project.

Field Types: What to Choose for Each Task

A field defines the type and storage method. ProcessWire has over 20 built-in types. Below is a table of the most common ones:

FieldtypePage speeds up development by 5 times compared to direct SQL queries, and Repeater can replace up to 10 separate templates. Choosing the correct type reduces the number of fields by 20–30% and eliminates unnecessary tables.

Creating Fields and Typical Mistakes

Fields are created in Setup → Fields → Add New. The main thing is to set the Name (Latin, underscore) and Label correctly. A common mistake is using overly long machine names. Better review_date than data_otziva_klienta_v2.

Special attention to the FieldtypePage field. In its settings, be sure to:

• Dereference as: Page (single) or PageArray (multiple)
• Parent: restrict selection to children of a specific parent — prevents accidental connections
• Template filter: show only pages with the required template

// In code: single relation
echo $page->category->title;

// Multiple relation
foreach ($page->tags as $tag) {
    echo "<span class='tag'>{$tag->title}</span>";
}

Creating Templates: Step-by-Step

A template links fields to a PHP rendering file. The process:

1. Create a PHP file in /site/templates/
2. In Setup → Templates → Add New — ProcessWire will find the file automatically
3. Add needed fields on the Fields tab
4. Configure Access (permissions)
5. Configure URLs (allow/disallow child pages, URL suffix)

On the Advanced tab, there are key options:

• Page class — custom PHP class for pages of this template (enables custom methods like getFullName())
• Prepend/Append file — include _init.php and _main.php
• Cache time — cache template output for N seconds (for high-traffic pages)
• Allow page numbers — enable /page2, /page3 (for pagination)

Why Use Repeater Instead of Separate Templates?

Repeater allows editors to dynamically add/remove groups of fields. This is more flexible than creating separate templates for each block. Example: a "Benefits" block with fields icon, headline, text.

// Field features (Repeater)
foreach ($page->features as $feature) {
    echo "<div class='feature-card'>";
    echo "  <img src='{$feature->icon->url}' alt=''>";
    echo "  <h3>{$feature->headline}</h3>";
    echo "  <p>{$feature->text}</p>";
    echo "</div>";
}

RepeaterMatrix (paid ProFields module) goes further: it allows multiple block types in one field — akin to ACF Flexible Content. This is our choice for complex landing pages.

How to Export and Import Configuration?

Moving structure between environments is a common pain. We use the RockMigrations module: it describes fields and templates in PHP code like Laravel migrations. An alternative is JSON export via API:

php -r "
  require '/var/www/site/index.php';
  echo \$templates->get('product')->exportJSON();
" > product-template.json

Configuration can also be exported through Setup → Export/Import.

What’s Included in Our ProcessWire Setup Work?

• Content structure analysis — define entities and relationships
• Field and template design — considering performance and editor UX
• Implementation — creating fields, templates, migrations
• Testing — checking for N+1 queries, Core Web Vitals
• Deployment and documentation — hand over description and editor guide
• Warranty — 3 months of support after delivery

Our engineers are ProcessWire certified and have experience with projects of any complexity. Proper structure saves up to 30% on development time. Request an audit of your current structure — we’ll find bottlenecks and propose optimizations.

Approach Comparison: Fieldtype vs Manual Implementation

Using ProcessWire fields gives an advantage in speed and reliability. ProcessWire Documentation: Fieldtypes.

Properly configured fields and templates are the key to fast development and happy editors. If you have doubts about architecture, contact us — we’ll help.

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.