MIGX Setup for Complex Content in MODX

MIGX Setup for Complex Content in MODX

Picture this: a client asks to add a 'Our Projects' block to a landing page, with a logo, title, description, tech stack, and a link. Without MIGX, you'd create 5–6 separate TV parameters or store everything in one JSON field and then write a complex parser. Standard MODX TV parameters don't allow repeatable field groups — you have to duplicate TVs or use workarounds. The editor finds it inconvenient, the developer suffers. MIGX solves this in 15 minutes.

MIGX (Multi-Items Grid for MODX) is an Extra for creating repeatable field groups within a single TV parameter. It's analogous to Paragraphs in Drupal or repeaters in ACF/WordPress. The editor can add unlimited blocks of any structure: slides, advantages, steps, galleries, price lists. We set up MIGX turnkey — you get ready configurations and output templates. Over 5 years, we've set up MIGX on more than 50 projects—from landing pages to catalogs. Contact us for a consultation.

Problems We Solve

Standard MODX TV parameters are inadequate for structured repeated content. Common issues:

• TV proliferation: each field needs its own TV, leading to dozens of variables for a single block.
• Poor editor experience: adding new items requires cloning TVs or editing raw JSON.
• No sorting or validation out of the box: developers must implement custom solutions.

MIGX eliminates these problems by providing a single JSON-based TV with a grid interface for adding, editing, sorting, and deleting items.

How We Do It (Expertise Proof)

We use MIGX extensively. Our typical stack: MODX 2.x/3.x, MIGX 2.x, getImageList snippet, pdoTools for advanced cases. We design the data structure first, then create a MIGX configuration as a JSON object.

Example: Slider Configuration

{
  "formtabs": [
    {
      "caption": "Slide",
      "fields": [
        { "field": "image", "caption": "Image", "inputTV": "migx_image", "inputTVtype": "image" },
        { "field": "title", "caption": "Title", "inputTVtype": "text" },
        { "field": "subtitle", "caption": "Subtitle", "inputTVtype": "textarea" },
        { "field": "link", "caption": "Button Link", "inputTVtype": "url" },
        { "field": "btn_text", "caption": "Button Text", "inputTVtype": "text", "default": "Learn More" }
      ]
    }
  ],
  "columns": [
    { "header": "Image", "dataIndex": "image", "renderer": "this.renderImage", "width": 80 },
    { "header": "Title", "dataIndex": "title" }
  ],
  "actionbuttons": "add,edit,remove,moveup,movedown",
  "window_title": "Slide"
}

We then attach this configuration to a TV parameter (input type migxdb or migx). Output is handled by the getImageList snippet:

[[!getImageList?
    &tvname=`hero_slider`
    &docid=`[[*id]]`
    &tpl=`@INLINE
    <div class="slide" style="background-image:url([[+image]])">
        <h2>[[+title]]</h2>
        <p>[[+subtitle]]</p>
        <a href="[[+link]]" class="btn">[[+btn_text]]</a>
    </div>
    `
]]

Alternative methods include migxLoopCollection or pdoTools with pdoField, but getImageList is simpler and faster for most cases.

Comparison of Output Methods

In a recent project, we replaced 12 separate TV parameters with a single MIGX TV for a team member block, reducing template complexity and editor error.

Process and Estimation

We don't offer fixed pricing — each project is unique. Our process:

1. Data collection: understand the content types and editor needs.
2. Audit/analysis: review existing templates and suggest optimal structure.
3. Design: create MIGX configurations and output templates.
4. Estimation: provide a timeline and budget based on complexity.
5. Development: implement configurations, attach TVs, write snippets.
6. Testing: verify data integrity and output.
7. Launch: deploy and provide documentation.

Timeframes

Setting up a MIGX configuration for 3–5 block types typically takes 1–2 days. Complex nested structures or extensive custom rendering may extend this.

Common Mistake: Forgetting docid

Comparison: MIGX vs Standard TV Lists

MIGX reduces development time by 30–40% according to official MODX documentation.

What's Included in Turnkey MIGX Setup

We don't just install the Extra — we design the data structure, create configurations, attach TVs, write output templates, and optimize performance. You get:

• Up to 5 types of repeatable blocks (slider, advantages, team, price list, testimonials);
• Output templates with responsive layout;
• Documentation for editors;
• Consultation on content population.

Contact Us

To get a ready solution, contact us — we'll assess your project and offer a turnkey MIGX setup. Order MIGX setup now and accelerate development by 30%.

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.