Dynamic Pages

Bind collection data to your pages for dynamic, data-driven content.

What Are Dynamic Pages?

Dynamic pages generate individual pages for each item in a collection. For example, a “Blog Posts” collection can automatically generate a page for each blog post.

Creating a Dynamic Page

1. Create a new page
2. In page settings, connect it to a collection
3. The page URL will include a dynamic slug from the collection

Binding Data

Once a page is connected to a collection, you can bind collection fields to elements:

1. Select an element on the canvas
2. In the right panel, find the Data Binding option
3. Choose the collection field to display

Text elements, images, links, and other elements can all be bound to collection data.

Format Presets

When you insert a date or number CMS variable into a text element, you can choose a display format. Click the variable badge to open a format selector with live previews.

Date formats include long and short date-time, 24-hour time, full and abbreviated weekday, US numeric (3/26/2026), EU slash (26/03/2026), EU dots (26.03.2026), ISO (2026-03-26), month/year, and time-only options. Date-only fields show only date formats (no time options).

Number formats include integer with grouping, decimal (1 or 2 places), plain without grouping, compact notation (e.g., 12K), and percentage.

Reference Field Links

When linking to a dynamic page, you can use a reference field to determine which item the link points to. For example, if a blog post has an author reference field, you can create a link that goes to that author’s dynamic page. Ycode resolves the reference at render time and generates the correct URL with the referenced item’s slug.

Collection Lists

To show multiple items on a single page (e.g., a blog listing), use a Collection List element. The collection list repeats its child layers for each item in the connected collection.

Setup

1. Add a Collection element to your page
2. Choose which collection to display
3. Design the layout for a single item — the design repeats for each item
4. Bind collection fields to elements inside the list

You can also right-click any block and select Convert to collection to quickly turn it into a collection list. The block’s existing children become the repeating template.

Sorting

Control the display order of items:

• None — Default database order
• Manual — Custom order set by drag-and-drop in the CMS
• Random — Shuffled on each page load
• By field — Sort by any field (e.g., date, name, price) in ascending or descending order

Filtering

Add filter conditions to show only items matching specific criteria. You can filter by any collection field using operators appropriate to the field type (text contains, number greater than, date is after, reference is one of, and more).

Filters use group-based logic: conditions within a group are combined with OR, and groups are combined with AND.

See Filtering & Sorting for the full list of operators and examples.

Pagination

For large collections, enable pagination to split items across pages:

• Pages mode shows previous/next navigation and page info
• Load More mode adds a button that appends the next batch

Set the items per page count to control batch size. Pagination respects filters — only matching items are counted.

Inverse References

Inverse references let you show related items from the opposite direction of a reference field. For example, if a “Books” collection has an author reference field pointing to “Authors”, you can place a collection list on an Author’s dynamic page that automatically shows all books by that author.

To set up an inverse reference:

1. Add a Collection element inside a dynamic page or within another collection list
2. In the Source dropdown, look for options labeled with the pattern: Collection Name (via field name)
3. Select the inverse reference source

Ycode automatically discovers these relationships based on existing reference and multi-reference fields in your collections. You do not need to create any additional fields.

Inverse references work with both single reference and multi-reference fields. They also support nesting — a collection list using an inverse reference can itself contain nested collection lists.