You have a ready design, but integration with October CMS turns into a headache: N+1 queries when displaying records, hydration mismatch when using Vue.js, bloated CSS without tree-shaking. Every second of loading costs money — the first 3 seconds of LCP determine whether the user stays. We develop custom October CMS themes turnkey, solving these problems at the architecture level. 5+ years of experience and 30+ projects in the portfolio are not just numbers, but proven patterns for typical tasks: from blogs to corporate portals. Investment in a custom theme pays off within the first year by reducing server load and decreasing loading time. Our clients save up to 40% on revisions in the first year. Contact us for a consultation on your project.
What problems does a custom October CMS theme solve?
A custom theme eliminates N+1 queries, bloated CSS and JS, and caching issues. We optimize Core Web Vitals: LCP, CLS, INP. The result is 30–50% faster loading than ready-made themes. Additionally, proper Twig caching reduces server response time by 200–400 ms.
How is Vite integrated with October CMS?
Frontend build via Vite provides hot reload, minification, and automatic tree-shaking. The vite-plugin-october-cms-theme plugin integrates directly with the template system, accelerating development by 2–3 times compared to manual builds. Changes appear instantly via HMR, and final files receive hashes for cache invalidation. Compare: without Vite, a rebuild takes 10–15 seconds; with it, less than a second. Time savings on each development cycle is 80–90%, directly impacting the project budget.
npm install vite laravel-vite-plugin
What is included in custom theme development?
Custom theme development includes:
- Analysis of the design layout and preparation of the structure
- Creating theme.yaml with form fields for the editor
- Layout of layouts, pages, partials (pixel-perfect, responsive)
- Integration of components (blog, products, forms)
- Build via Vite with HMR, minification, and hashing
- Testing on desktop and mobile (LCP, CLS, INP check)
- Documentation on theme structure and training on component usage
- 1-month warranty support
Cost is calculated individually based on project complexity.
What is inside a custom theme?
A typical custom theme structure for October CMS includes:
- theme.yaml — metadata and form fields
- layouts/ — base templates (default.htm, minimal.htm)
- pages/ — site pages (index, about, blog)
- partials/ — reusable blocks (header, footer, nav, blog/)
- assets/ — styles, scripts, images
# theme.yaml
name: My Theme
description: Corporate theme for My Site
author: My Company
homepage: https://mycompany.com
code: mytheme
form:
fields:
primary_color:
label: Primary Color
type: colorpicker
default: '#1a56db'
logo:
label: Site Logo
type: mediafinder
mode: image
Fields from theme.yaml are accessible in the template via this.theme. This allows changing colors, logo, and other parameters without code edits — the editor can customize the appearance independently.
Layout and pages: how it works
The base layout loads styles and scripts, sets meta tags. Fields from this.page are used for unique title, description, and H1. October CMS components, such as blogPosts, automatically fetch records with pagination and caching.
description = "Default Layout"
==
<!DOCTYPE html>
<html lang="{{ this.site.locale ?? 'ru' }}">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>
{% if this.page.meta_title %}
{{ this.page.meta_title }} | {{ this.site.name }}
{% else %}
{{ this.page.title }} | {{ this.site.name }}
{% endif %}
</title>
<meta name="description" content="{{ this.page.meta_description }}">
{% styles %}
<link rel="stylesheet" href="{{ 'assets/css/app.css' | theme }}">
</head>
<body class="{{ this.page.layout_class }}">
{% partial 'header' %}
<main id="main">
{% page %}
</main>
{% partial 'footer' %}
{% scripts %}
<script src="{{ 'assets/js/app.js' | theme }}" defer></script>
</body>
</html>
Page with components: blog in 10 minutes
title = "Blog"
url = "/blog/:page?"
layout = "default"
is_hidden = 0
[blogPosts]
postsPerPage = 12
sortOrder = "published_at desc"
[blogCategories]
slug = "{{ :slug }}"
==
{% set currentPage = this.param.page ?? 1 %}
<section class="blog-header">
<h1>{{ this.page.title }}</h1>
</section>
<section class="blog-content">
<div class="posts-grid">
{% for post in blogPosts %}
{% partial 'blog/post-card' post=post %}
{% endfor %}
</div>
<aside class="sidebar">
<h3>Categories</h3>
<ul>
{% for cat in blogCategories %}
<li><a href="{{ cat.url }}">{{ cat.name }} ({{ cat.posts_count }})</a></li>
{% endfor %}
</ul>
</aside>
</section>
Why a custom theme is faster than a ready-made one?
Ready-made themes often contain excessive code, dead CSS and JS, which slows down loading. A custom theme lacks this: we include only necessary styles and scripts, use tree-shaking, and optimize images. As a result, pages load 30–50% faster.
Build tool comparison: Vite vs Webpack
| Criteria |
Vite |
Webpack |
| Cold start time |
< 1 s |
5–10 s |
| Hot module replacement |
Instant |
1–3 s delay |
| Tree-shaking |
Automatic |
Requires configuration |
| Minification |
Built-in via esbuild |
Via Terser |
| Configuration |
Minimal |
Complex |
Vite wins in speed and simplicity. We use it by default in our projects, reducing build time by 70%.
Typical mistakes when building on your own
- Ignoring Twig caching — page loads 200–400 ms slower.
- Missing partials for reusable blocks — code duplication and N+1 queries.
- Hand-made build instead of Vite — lengthy development, no tree-shaking.
Our process
- Analysis of the design layout — evaluate complexity, prepare estimate and timeline.
- Create theme.yaml and structure — define form fields, routes.
- Layout layouts, pages, partials — pixel-perfect, responsive.
- Integrate components — configure blog, products, forms.
- Build via Vite — HMR, minification, hashing.
- Test on desktop/mobile — check LCP, CLS, INP.
- Handoff and training — documentation, editor setup.
We use the current version of October CMS and stay updated with releases. Contact us for a consultation on your project. Order a custom theme development with a guaranteed result.
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.
| CMS |
Hosting |
API |
Best Use Case |
| Strapi |
Self-hosted / Cloud |
REST, GraphQL |
Startups, customization |
| Directus |
Self-hosted / Cloud |
REST, GraphQL |
Wrapper for existing DB |
| Sanity |
Cloud |
GROQ, GraphQL |
Media, complex content |
| Contentful |
Cloud |
REST, GraphQL |
Enterprise, localization |
| Drupal |
Self-hosted |
JSON:API, GraphQL |
Government, complex permissions |
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:
- Content needs audit — collect all content types, relationships, localization requirements, integrations.
- Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
- CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
- Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
- Content migration (if legacy) — automated loading via API or scripts.
- Testing — check API endpoints, regression, load testing, Core Web Vitals.
- 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:
| Project Type |
Timeline |
| Simple site on Strapi + Next.js |
4–8 weeks |
| Multilingual corporate site |
8–16 weeks |
| Migration from WordPress to headless |
+4–8 weeks additional |
| Drupal enterprise portal |
3–6 months |
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.
