---
title: "Choosing a Craft CMS page builder: Matrix, Neo, Vizy or Canvas Studio"
description: "Compare custom Craft CMS builders, Matrix, Neo, Vizy and Canvas Studio. Explore developer setup, client editing, layout controls and reusable designs."
url: "https://canvasforcraft.com/journal/choosing-a-craft-cms-page-builder/"
---

A guide to page building

# Choosing a Craft CMS page builder: Matrix, Neo, Vizy or Canvas Studio

Consider Matrix for structured page sections, Neo for controlled block hierarchies, Vizy for rich text with embedded blocks, and Canvas Studio for visual page composition.

By [Bilal Harry Lindemann](https://lindemann.design/about/) · Published by [LindemannRock](https://lindemannrock.com/) · 5 October 2026 · Updated 6 October 2026

On this page

## Start with what your editors need to change

A search for a Craft CMS page builder brings together several different tools: native structured fields, nested block plugins, rich content editors and visual layout editors. They overlap, but they do not ask the same things of your authors or developers.

Start with a real task. Does an editor need to fill out a prescribed section, add a block inside an article, or change the arrangement of a page? That distinction is more useful than a checklist where every product simply gets a tick for “flexible content.”

### The tools and the builder you create with them

Matrix, Neo and Vizy can each form part of a custom builder. They provide fields and editing capabilities; the agency decides how to combine them with project-specific settings and templates. A native Matrix-and-Twig builder, with no Neo or Vizy involved, belongs to that same broader category.

There are two decisions to make: which foundations fit your content, and how much of the composition system your team wants to implement. [Compare Canvas with a custom Craft CMS builder](https://canvasforcraft.com/compare/custom-builder/) for the developer-work and client-experience perspective.

Craft CMS page-building approaches at a glance

| Approach | Best fit | Developer setup | Editor control | Reuse |
| --- | --- | --- | --- | --- |
| [Matrix](https://canvasforcraft.com/compare/matrix/) | Structured page sections. | Define entry types, fields and Twig output. | Edit and arrange entries; layout choices depend on your fields. | Reuse entry types and templates; copy entries. |
| [Neo](https://canvasforcraft.com/compare/neo/) | Controlled block hierarchies. | Define block types, child rules, fields and Twig output. | Arrange nested blocks within the rules your project sets. | Reuse fields and templates; copy blocks with children. |
| [Vizy](https://canvasforcraft.com/compare/vizy/) | Rich text with embedded blocks. | Configure the editor, block fields and rendering. | Write, format and arrange content with configured blocks. | Reuse Craft fields and block templates. |
| [Canvas Studio](https://canvasforcraft.com/#playground) | Visual page composition. | Configure a theme and integrate Canvas rendering with your site. | Compose modules and adjust layout and responsive settings. | Linked Components with local content; independent Static copies. |

“Best fit” describes the focus of each approach, not its limits. All four need project setup. Shared content and additional layout controls can also be built into a custom implementation.

These summaries draw on the [Matrix documentation](https://craftcms.com/docs/5.x/reference/field-types/matrix.html), [Neo’s repository](https://github.com/spicywebau/craft-neo) and [Vizy’s features](https://verbb.io/craft-plugins/vizy/features). The detailed comparisons explain where each approach fits.

## The real work is building the editing experience

A carefully built Craft site can already give editors substantial freedom. The recurring question for an agency is how much of that experience to design and maintain for each project.

### Content structure is only the beginning

Andrew Welch’s [content-builder article](https://nystudio107.com/blog/creating-a-content-builder-in-craft-cms) explains the established pattern: define content blocks and render each through a focused template. Published in 2017 and updated in 2019, it is useful context for the approach, rather than a reference for today’s Craft 5 API.

Foster Commerce’s [Measure Meant case study](https://www.fostercommerce.com/commerce-minded-post/flexible-craft-cms-page-builders-for-measure-meant) describes consolidating fragmented builders, adapting Twig partials and adding Neo-based column and style controls. The work improved the authors’ ability to assemble pages while retaining the site’s design.

### Good custom builders also solve reuse

Mutual’s [2026 approach](https://www.mutual.agency/blog/how-we-make-craft-cms-page-builders-in-2026) combines Matrix rows with CKEditor content, a visual picker, centrally reused content and independent template copies. It demonstrates that reuse and flexible page building are possible with a custom Craft implementation.

Canvas’s aim is to give teams a dedicated visual composition system for this work. Themes define the shared design choices. Editors compose with modules and responsive controls. Linked Components and Static copies distinguish a design that should remain shared from one that should become independent.

### The client has to understand the controls

Width, spacing, typography, background and alignment can each be a useful setting. Across nested sections and columns, they can also create long forms in which clients have to work out how individual choices affect the page. The quality of the labels, defaults, previews and field organization matters as much as the number of options.

Canvas brings those composition decisions into a visual editor. The practical test is whether authors can find the relevant control, understand its effect and carry the design across screen sizes. A well-designed custom builder may already serve its users well; evaluate the actual editing experience.

### Try the same brief in each approach

- **Create the section.** Put an image beside text and a button. Note which fields, templates and settings have to exist first.

- **Change the design.** Adjust proportions and spacing, then stack the section on smaller screens. Can the editor make those choices within the intended design rules?

- **Reuse it.** Put it on a second page with a different image and headline. Decide what should stay shared and what should remain local.

- **Maintain it.** Change the shared design later. Check which pages update, which content stays untouched and who owns that change.

Use this as an evaluation brief, not a speed benchmark. The right result depends on the content model, the editor’s responsibilities and the implementation you need to support.

## Matrix vs Neo vs Vizy: what changes for your team?

**For structured data, begin with the content model.**

If records need their own fields, relationships and queries, evaluate Craft’s native structures first. Page layout should not erase useful structure.

**For a tailored block hierarchy, evaluate the configuration work.**

Matrix and Neo can underpin a custom page builder. Compare the actual field setup, allowed arrangements and templates you would maintain.

**For writing with inline components, evaluate the authoring flow.**

Vizy and configured CKEditor workflows address this need. Test how authors insert and edit content while keeping an article readable.

**For changing visual compositions, evaluate Canvas.**

Canvas is aimed at teams that want layout controls, shared theme definitions and reusable designs within Craft, with less repeated work building the composition interface.

A project may use more than one approach. Keep a structured catalogue structured; give a campaign page the composition tools it needs. Craft can remain responsible for the wider site and its publishing workflow.

## Common questions

### Does Craft CMS have a page builder?

Craft provides content tools that developers use to build editing experiences. Matrix is a native foundation; plugins offer other approaches, including Neo’s block hierarchy, Vizy’s rich content editing and Canvas Studio’s visual composition.

### Will a visual builder remove the need for developers?

Canvas does not remove Craft setup, content modelling or template integration. Its focus is the repeated work of providing page-composition controls, so teams can spend more of their time on the site’s design and requirements.

### Should an existing site switch?

Only if the new workflow addresses a real limitation. Test representative pages, check how existing data would move and compare maintenance needs. A builder that already serves its editors well does not need replacing simply because another option exists.

## Sources & scope

This guide is written by Bilal Harry Lindemann and published by LindemannRock, the makers of Canvas Studio. Sources were reviewed on 5 October 2026. The linked agencies describe their own implementations; they are not presented as Canvas customers or endorsers.

- [Craft 5 Matrix documentation](https://craftcms.com/docs/5.x/reference/field-types/matrix.html)

- [Neo documentation](https://github.com/spicywebau/craft-neo)

- [Vizy features](https://verbb.io/craft-plugins/vizy/features)

- [nystudio107: Creating a Content Builder in Craft CMS](https://nystudio107.com/blog/creating-a-content-builder-in-craft-cms)

- [Foster Commerce: Measure Meant case study](https://www.fostercommerce.com/commerce-minded-post/flexible-craft-cms-page-builders-for-measure-meant)

- [Mutual: How we make Craft CMS page builders in 2026](https://www.mutual.agency/blog/how-we-make-craft-cms-page-builders-in-2026)

## About the author

Bilal Harry Lindemann is a designer, creative technologist and co-founder of LindemannRock. His work spans design leadership, research, design systems and software development, connecting strategy with hands-on delivery across brands, products and platforms.

[More about Bilal Harry Lindemann](https://lindemann.design/about/)

See the approach

## Build the page. Keep your design system.

Try the interactive examples of layouts, themes and reusable Components. Sign up for Canvas Studio launch updates.

[Explore Canvas Studio](https://canvasforcraft.com/#playground) [Get launch updates](https://canvasforcraft.com/#signup)