Communik.io : Site & App builder
communik.io

FEATURE / CMS

Give every entry its own page.Design the template once.

Structure recurring content in collections. Use the same records to render cards in a listing and details at individual URLs.

COLLECTION → TEMPLATE
Simplified view

WALKS COLLECTION

Forest walk
45 min
Garden loop
20 min

ONE DETAIL TEMPLATE

/walks/[slug]

/walks/forest-walk → 45 min

The slug selects the record. The same template displays the title and duration for each walk.

EXAMPLE

A guesthouse builds a guide to nearby walks

Each walk has a title, photo, duration and route notes. The agency builds a listing and a detail template. When the host adds a forest walk, the listing reads that record and its detail URL shows the matching content. The host maintains the information and the agency maintains the design.

01

Model two real entries first

Create title, slug, image, duration and rich-text fields. Add one short route and one longer route with an optional photo missing. This reveals which fields your template must handle.

02

Connect the list and the detail page

Repeat a card for each record in the listing. On the detail template, bind the URL parameter to the unique slug and connect the visible elements to their fields.

03

Test with varied records

Open two real URLs from the listing in staging. Check that titles and photos change, optional fields have a deliberate fallback, and no card points to an empty address.

INSIDE COMMUNIK

Connect a collection to a page.

The guide connects a detail template to the Escapades Alma collection.

Recording from the documentation · French interface.

Open the English documentation ↗
PRODUCT RECORDING

COLLECTION FIELDS

The fields behind each walk

Title and slug
Forest walk → /walks/forest-walk. Keep the slug unique and stable.
Duration and photo
Show them on the card and detail page. Plan a fallback if a photo is optional.
Directions
Keep the full route notes on the detail page, where visitors can read them at their own pace.
Communik — aperçu du modèle avec la fiche du jardin
The garden record displayed in the detail template. French interface. Open full size ↗

Practical questions

Do I need to create a page for every record?

One connected template can serve the detail URLs. Each URL identifies its record by the slug you map to the route.

Does connecting a page replace fixed text?

Connect the heading, image and other elements individually to their fields. Fixed labels such as “Duration” can stay in the template.

When is a collection worth using?

Use one when several items share a structure or need to appear in several places. A standalone campaign page can use regular blocks.

Put it to work on your next site.

Start for free →