ProcessWire Corporate Sites: Fields to Deployment

A client needed a corporate portal with a multilingual structure in 12 languages, nested service categories, and access rights for three editor types. WordPress would have required installing ACF, WPML, and Custom Post Types plugins – 2–3 paid solutions. With ProcessWire — a free open-source CMS — we implemented everything using built-in tools: LanguageSupport, FieldtypePage, and template inheritance. In two weeks, the admin panel was ready, editors started populating content. Not a single paid extension — savings up to 40% compared to commercial CMS. We evaluate each project with a fixed estimate — no hidden payments. ProcessWire is an effective alternative to WordPress for projects with custom structure.

How ProcessWire handles non-standard data structures?

ProcessWire is ideal where content structure is unique. A service catalog with 30+ attributes, a multilingual site in 15 languages, a portal with non-linear page hierarchy — here it outshines WP and Drupal. The official ProcessWire documentation notes: "The API is built on the principle of simplicity: every call returns what you expect." In the admin panel, you create fields, group them into templates, and assign them to pages. No rigid content types, only your task.

Practical example: a client managed a network of clinics in 8 countries. Each clinic had its own set of services, prices, and doctors. On WordPress, we'd write custom post types and ACF — dozens of plugins. With ProcessWire, we got by with 4 templates and repeater fields. Content managers mastered the admin panel in an hour.

Why ProcessWire is 7 times faster than WordPress?

In tests with a selection of 1000 pages, ProcessWire returns a response in 20 ms, WordPress — 150 ms. The 7.5x difference is achieved due to the absence of heavy abstractions. ProcessWire does not load the entire engine for each request — only the needed modules.

Project architecture: templates and fields

Each template is a PHP file in /site/templates/. Markup, logic, and data are separated through controllers or _init.php/_main.php. Typical structure:

• /site/templates/_init.php — global variables, helpers
• /site/templates/_main.php — layout wrapper
• /site/templates/home.php — homepage
• /site/templates/services.php — service list
• /site/templates/service-item.php — details
• /site/templates/partials/nav.php, hero.php
• /site/modules/ — custom modules
• /site/config.php

Data access via the $pages API is concise:

$services = $pages->find("template=service-item, status=published, sort=sort, limit=12");
$results = $pages->find("template=service-item, title|body*=$q, limit=20");
$recent = $pages->find("template=news, date>=" . strtotime("-30 days") . ", sort=-date");
foreach ($page->related_cases as $case) {
    echo "<a href='{$case->url}'>{$case->title}</a>";
}
foreach ($page->features as $feature) {
    echo "<div class='feature'><h3>{$feature->headline}</h3><p>{$feature->text}</p></div>";
}

Multilingual out of the box

The modules LanguageSupport, LanguageSupportFields, LanguageSupportPageNames are enabled in the admin panel (documentation). Each text field gets language tabs. Switching in a template is one line:

$user->language = $languages->get("en");
echo $page->title; // English title

URLs are translated automatically: /ru/uslugi/ and /en/services/ — the same page.

What we solve?

Performance and caching

Caching via $cache API:

$nav = $cache->get("main-nav");
if (!$nav) {
    $nav = buildNav($pages);
    $cache->save("main-nav", $nav, 3600);
}

ProCache (paid module) generates static HTML and serves it directly via .htaccess — speed comparable to static sites. Invalidation occurs on events: when a page is modified, corresponding HTML files are regenerated. This keeps content up-to-date without performance loss.

Typical development timelines

Headless mode

ProcessWire as a headless CMS: the template returns JSON, the frontend (React/Next.js) fetches data via an endpoint. ProcessWire only handles content storage and delivery.

header("Content-Type: application/json");
$data = [];
foreach ($pages->find("template=product, limit=50") as $p) {
    $data[] = [
        "id"    => $p->id,
        "title" => $p->title,
        "slug"  => $p->name,
        "price" => $p->price,
        "image" => $p->image->httpUrl ?? null,
    ];
}
echo json_encode($data);

Development stages

1. Analysis — study business processes, collect requirements for fields and templates.
2. Design — create template architecture, configure admin panel.
3. Implementation — write custom modules, develop templates.
4. Testing — check access rights, loading speed, Core Web Vitals.
5. Deployment — set up caching, deliver documentation.

Common mistakes and how to avoid them

• Ignoring custom fields for data that doesn't fit the template — always use Fieldtype and Repeater instead of storing data in text fields as JSON.
• Lack of caching for repetitive requests — wrap queries in $cache->get() with a TTL.
• Incorrect permissions — test roles before launch: an editor should not see configuration templates.

What is included in the work

• Design of field and template architecture
• Admin panel setup tailored to business processes
• Writing custom PHP modules
• Integration with external services (1C, CRM, payment gateways)
• Testing and optimization of Core Web Vitals
• Editor training
• Access handover and documentation
• Fixed cost after preliminary analysis

Our experience and guarantees

We have been working with ProcessWire since version 2.x — over 5 years. During this time, we have completed 20+ projects: from simple corporate sites to headless portals with a load of up to a million requests per day. All work comes with a 12-month warranty.

Get a consultation on your project — we will send a commercial offer with a fixed cost within a day. Contact us to discuss details. Order a free preliminary architecture analysis — we will assess the complexity and propose the optimal solution.

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.