Built on WIX Headless

Blog / product

Native Harmony CMS vs CMS for Harmony

· Harmony CMS vs CMS for Harmony

Native Harmony CMS vs CMS for Harmony

Wix Harmony ships a built-in CMS that connects design to collections without datasets. Wix’s own overview explains how that model works — and where it differs from Classic and Studio.

CMS for Harmony is a separate App Market app. It does not bind native Text, Image, or Button elements to CMS fields. It adds app widgets (Table, Repeater, Slideshow, Media Gallery, Calendar, Dynamic Page, and Form) when you need layouts and visitor tools the native path does not cover yet.

Use this guide to decide when native is enough and when the app fills a gap.

What native Harmony CMS does well

Per Wix’s Harmony CMS model:

If you need a simple card grid of text and images from one collection, native Harmony is often the right first step.

Where native Harmony CMS is limited today

Wix documents several Classic/Studio patterns that work differently — or are missing — in Harmony:

NeedNative Harmony CMS (today)CMS for Harmony
Visitor search & filters on one listNo visitor filter inputs; use separate Repeaters each with their own editor-side filterTable, Repeater, and Calendar with match conditions, ranges, fixed Choose-value filters, top or side layout
Dense inventory / directoryRepeater cards onlyTable widget with columns, sort, and filters
Month/week eventsNot a calendar layoutCalendar from DATE / DATETIME fields
Media galleriesGallery field type not in Harmony collectionsMedia Gallery widget + gallery fields on displays and forms
Reference / multi-reference fieldsNot included in Harmony field typesShow and filter related items; pick a Display field for labels
Address & Color displayLimited field set / no specialized layoutsAddress as text or map; Color as swatch, hex, or both
Collect into a collectionCMS links are display-only; use Wix Forms for captureForm widget writes into a connected collection (text, phone, Color, images, galleries)
Item detail layoutsItem pages with native elementsDynamic Page widget on a native collection page, with optional per-item SEO mapping
Classic & Studio sitesHarmony-specific CMS modelSame app widgets on Classic, Studio, and Harmony

Other native notes from Wix: no sandbox (saved collection changes affect live content unless you filter them out), collection order does not automatically drive the site (sort in Manage items), and Wix app collections (for example Stores) do not connect to Harmony Repeaters the same way.

How the two fit together

They are complementary, not competitors for the same binding model:

  1. Native owns design-system Repeaters and item pages when Text/Image/Button binding is enough.
  2. CMS for Harmony owns app widgets when you need tables, calendars, visitor filters, collection-backed forms, richer field types in the display, or the same toolkit outside Harmony.

“Cards” in our product means a Repeater layout — not a separate widget and not a claim that we replace Harmony’s native Repeater.

When to stay native

When to add CMS for Harmony

Quick start with the app

  1. Install CMS for Harmony from the App Market.
  2. Add a widget (start with Repeater or Table).
  3. Connect a collection and publish.
  4. Add search & filters, a Form, or Dynamic Pages when the site needs them.

Ready to try it on Harmony? Get a free starter site CMS for Harmony