How to Set Up Wix Studio CMS: Dynamic Pages & Collections (2026)

If your site has more than ten pages of similar content — portfolio projects, case studies, products, properties, team members — you should not be building them by hand. Wix Studio's CMS handles all of that with collections, dynamic pages, and repeaters. This is the practical setup guide most "intro to Wix Studio" posts skip.

What the CMS Actually Does (And Why It Matters)

The Wix Studio CMS is a built-in database. You define a collection (think: a table with named columns), each row becomes an "item," and Wix can render those items two ways: as a list on any page (via a repeater or gallery), and as a single "dynamic page" with a unique URL per item.

The payoff is straightforward. Add a new portfolio project once in the CMS and you get the project card on the listings page, the full project page at its own SEO-friendly URL, related-project blocks, and any filtered views — all updated automatically. No copy-paste between pages, no broken links, no orphaned content.

For service businesses, agencies, and freelancers, this is the single feature that turns Wix Studio from a marketing-site builder into a real content system.

Step 1: Create the Collection

Open the CMS panel from the left rail in the Wix Studio editor. Add a new collection and choose "Multiple items" — this is what you want for any list-of-things use case. Name it something specific and lowercase-friendly like projects, case-studies, or team-members.

Add fields one at a time. For each, pick the right type:

• Text for titles, summaries, and short copy.

• Rich text for the long body of an article or project description.

• Image and Image gallery for hero images and additional media.

• Reference for links between collections (e.g., a project that references a client from another collection).

• Tags for multi-value categorisation like industries or skills.

• Date, Number, URL, and Boolean for everything else.

A common mistake: skipping the slug field. Wix auto-generates one from the title, but you want explicit control. Add a slug text field and fill it in yourself for every item — clean URLs matter for SEO and they outlive title changes.

Step 2: Add Items (or Import a CSV)

You can add items one by one in the CMS panel, but if you already have a list — even a quick Notion export or a Google Sheets table — use the CSV import. Match columns to fields, double-check the slug column, and import. For ten or more items this saves real time and avoids the typos that come with manual entry.

Before you connect the collection to a page, set the field-level permissions. For a public-facing portfolio, that's "Anyone." For lead-gen or members-only content, restrict it. This is also where you set the default sort order so newer items appear first.

Step 3: Build the Listings Page

Drop a Repeater onto the page where the items should appear. Inside the repeater, design one card the way you want all of them to look — image at the top, title, a short summary, a tag pill, a CTA link. Keep this card honest: if it doesn't look right with the longest title you have, fix it before connecting data.

Now connect the dataset. Add a dataset, point it at your collection, set the mode to "Read," and bind each element in the repeater to the matching field. The title text element binds to title, the image to coverImage, the CTA to the dynamic item page URL, and so on.

Set the dataset's items-per-page based on the layout. Twelve to twenty-four works for most portfolio grids. Add a "Load more" button or pagination once you exceed that.

Step 4: Create the Dynamic Item Page

This is the part that makes the CMS feel like a real system. Right-click the collection and choose "Add a dynamic item page." Wix creates a template page with a URL pattern like /projects/{slug}. Every item in the collection gets a page at its own URL automatically.

On the template, lay out the full single-item view — hero, body content, gallery, related items. Connect each element to the field on the current item. The same page renders differently for every record, and Google sees them as distinct, indexable pages.

A small detail with outsized impact: set the SEO title and meta description on the dynamic page using the item's fields, not a static template. Bind the page title to the title field and the meta description to the summary field. Every project then has unique metadata without you writing it twice.

Step 5: Add Filtering, Sorting, and Search

On the listings page, add filters by binding dropdowns or button groups to the dataset's filter API. Common filter dimensions: category, industry, year, status. For search, drop a text input, connect it to a "contains" filter on the title field, and you have an instant search box.

Sorting works the same way — a dropdown that changes the dataset's sort field between "Newest," "Oldest," or "A–Z." None of this requires Velo code for standard cases. Reach for code only when you need cross-collection joins, conditional logic, or computed fields.

Step 6: Connect Related Items and Cross-Links

Use Reference and Multi-Reference fields to link collections — a project referencing a client, or a case study referencing multiple services. On a single-item page, you can show a "More projects from this client" block by adding a second repeater filtered by the current item's reference field. This is how you turn a flat list into a connected content graph.

A Few Things Worth Getting Right

Set canonical URLs on dynamic pages so duplicate parameter variations don't split SEO equity. Index your filterable category pages — they're often strong long-tail landing pages. Keep field names short and stable; renaming them later breaks bindings across the site.

If you're building a portfolio, case-study library, or any catalogue-style site, the CMS is what makes it scale. The templates at studiorra.com/templates ship with collections and dynamic pages already wired up, so you can study a working setup before configuring your own.