Custom MODX template development with static elements and Vite ensures version control and rapid builds. Our team has delivered over 50 projects using this approach. For a corporate website or online store on MODX with dozens of chunks and templates, editing through the admin panel becomes a bottleneck. No change history, impossible to roll back, and version confusion in team work. Our approach — disk-stored elements and Vite — ensures revision control, rapid iteration, and clean code.
Why Storing Templates in the DB Slows Down Development
MODX stores templates and chunks in the database by default. For a single site this is acceptable, but in a team conflicts arise: who changed a chunk, how to roll back, how to sync with a repository? The solution is disk-based elements. You keep templates in the file system, and MODX syncs them with the DB on each request. This gives you version control via Git and the ability to do code reviews. According to MODX documentation, a static element is the recommended way for team development. Using this static element pattern, you avoid merge conflicts and streamline deployment. This approach leverages MODX's element resolver for efficient static-to-db mapping, eliminating synchronization overhead.
How Vite Speeds Up Frontend Build
Vite transpiles SCSS and JavaScript almost instantly, adds a hash to filenames for cache invalidation, and supports hot reload. On one e-commerce project with 20+ page types, we switched templates to disk-persisted elements and Vite. Build time dropped from 5 minutes to 2 seconds — that's 150 times faster than Webpack. Merge conflict errors decreased by 70%. Automation saved up to 40% on maintenance. Vite's tree-shaking mechanism eliminates dead CSS and JS code, reducing bundle sizes. The typical payback period for this solution is 3–6 months, with annual cost savings of $2000 to $5000 for a mid-size project. For a typical investment of $3000 to $5000, you gain rapid build times and change tracking.
What disk-stored elements give you
A static template is an HTML document with MODX placeholders stored on disk. It's not tied to the database, easily reusable across projects. We configure syncing so that when a file changes on the server, MODX automatically updates the element in the DB. This makes deployment 10 times faster compared to DB storage. Using xPDO and MIGX for structured data further optimizes performance. The MODX Revolution template becomes a version-controlled asset.
How to Set Up Vite for MODX
The config is minimal, as in the example below. It defines the JS entry point, output folders for CSS and JS, and a proxy for local development. Vite's Hot Module Replacement (HMR) speeds up frontend work.
// vite.config.js
export default {
build: {
outDir: 'assets',
rollupOptions: {
input: { app: 'src/js/main.js' },
output: {
assetFileNames: 'css/[name].[ext]',
entryFileNames: 'js/[name].js',
chunkFileNames: 'js/[name].js'
}
}
},
server: {
proxy: {
'/': 'http://localhost:3000'
}
}
};
Build Tools Comparison
| Tool |
Initial Speed |
Hot Reload |
SCSS Support |
Recommendation |
| Vite |
Instant |
Yes |
Yes |
Yes |
| Gulp |
2–3 sec |
No |
Yes |
No |
| Webpack |
5–10 sec |
Yes |
Yes |
No |
File Structure
Typical structure with sources in src/ and build in assets/:
assets/
├── css/
│ └── app.css # Compiled CSS
├── js/
│ └── app.js # Compiled JS
└── images/
└── logo.svg
src/ # Sources (Vite/SCSS)
├── scss/
│ ├── main.scss
│ ├── _variables.scss
│ └── components/
└── js/
└── main.js
Base Template (HTML skeleton)
<!DOCTYPE html>
<html lang="ru">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>[[*longtitle:default=`[[*pagetitle]]`]] — [[++site_name]]</title>
<meta name="description" content="[[*description:notempty=`[[*description]]`:default=`[[++site_tagline]]`]]">
[[++seo_canonical]]
<link rel="stylesheet" href="[[++assets_url]]css/app.css?v=[[++build_version]]">
<link rel="icon" href="[[++assets_url]]images/favicon.ico">
</head>
<body class="[[*class_key:is=`modWebLink`:then=`page-link`:else=`page`]]">
[[$header]]
<main id="main" class="site-main">
[[*content]]
</main>
[[$footer]]
<script src="[[++assets_url]]js/app.js?v=[[++build_version]]" defer></script>
[[- Debug: [[++debug:is=`1`:then=`[[!session]]`]] ]]
</body>
</html>
What's Included in Custom MODX Template Development
| Component |
Description |
| Template set |
Home, inner, blog, 404, and up to 12 additional page types |
| Static elements |
Sync templates with file system, Git repository |
| Vite build |
SCSS/JS compilation, cache busting, hot reload |
| TV parameters |
Configure extra fields for content managers |
| Documentation |
Structure description, template usage guide |
| Training and support |
Basic post-launch support, team training |
Process of Custom Template Development
-
Layout analysis: break the design into functional blocks (header, content, sidebar, footer).
-
Structure design: define TV parameters, style sheets, JS modules.
- Base template markup: HTML skeleton with placeholders, integration with pdoTools for menus and breadcrumbs.
-
Frontend build: Vite compiles SCSS and JS, adds hash to filenames for cache busting.
- Testing: check on all page types, including 404 and search results.
-
Deploy: upload to hosting, configure static element syncing.
How We Test the Template Before Delivery
Testing includes checking layout compliance in three browsers (Chrome, Firefox, Safari), mobile resolutions from 320px to 1920px, and Core Web Vitals analysis. We use Lighthouse and PageSpeed Insights: for each template we achieve LCP < 2.5 s, CLS < 0.1, INP < 200 ms. This guarantees high performance out of the box.
Timeline and Cost
Timeline: from 2–3 days for a simple set to 2–3 weeks for complex designs with 8+ page types. Cost is calculated individually after analyzing your project, with typical budgets ranging from $1500 for basic templates to $6000+ for enterprise setups. Maintenance savings from static elements up to 40% translate to $800 to $2000 per year. For a typical mid-size project, investment is $3000 to $5000. The investment yields a positive ROI through reduced maintenance overhead and faster deployment cycles. Want to bring order to your MODX templates? Contact us for a consultation and an accurate estimate. Order a custom MODX template with version control and fast builds.
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.
