CMS & dynamic content

A DragGo design can be data-driven — read its content from a collection instead of having it typed into the canvas.

Design one card and bind it to a Collection — DragGo renders one card per item.

What a collection is

A collection is a small table that lives in your project: fields are the columns, items are the rows. Blog posts, projects, team members, products — anything you have more than one of and do not want to design twice.

Open Collections in the editor to create one. Each collection has:

a name you read, and a slug that appears in URLs
fields, each with a type — text, rich text, image, date, number, boolean, option, link, colour, or a reference to another collection
items, each with its own slug, and its own SEO title, description and share image

Design one card, get them all

Drop a Collection element on the canvas, point it at one of your collections, and design a single card inside it. DragGo repeats that card for every item.

Select any text, image or link inside the card and bind it to a field. The canvas shows placeholder rows while you work; the published page shows yours.

A collection element can also paginate, search, or filter to items whose field matches a value — one collection can feed several different lists.

A page per item

Add a CMS page and point it at a collection, and publishing produces one page per item at /{collection}/{item} — a real, separate, indexable page, not a template that fills itself in with JavaScript.

Link to an item’s page by binding a link to Permalink.

What is empty stays empty

While you are designing, an empty collection shows a few placeholder rows so the list is not an empty box. Published pages never show those. A list with nothing in it publishes as nothing at all — invented names and prices on a live page are worse than a gap.

Conditional visibility

Show or hide an element based on a field’s value — a “Sold out” badge that only appears when the stock field is 0, a byline only where an author is set.

Selling from a collection

A collection with a price field is a catalogue. Add a Products grid, an Add to Cart button, a Cart and a Checkout, and the same rows you were listing become things people can buy — a product page is a CMS detail page.

See Selling from your site for the five field names the shop reads and how orders arrive.

On WordPress

The DragGo plugin binds to WordPress content instead: posts, custom post types, taxonomies, ACF groups, registered meta: fields, and WooCommerce products. Those bindings resolve in PHP at render time, so the output is still a clean, cacheable page.

Was this page helpful?