You can connect any type of collection rows to regular pages using dynamic content. This allows the collection to function like the Content Library, but with a more flexible data structure, enabling you to create custom fields and use a wider range of data types than the Content Library.
A row can be configured for availability on a single page by using its URL, or set to be accessible on all pages by using _all_.
For those not familiar with collections, it's recommended to review the Collections Overview article first, as it provides important context for this topic.
For information on what dynamic content is and more, see Dynamic Content Overview.
To connect a collection to a regular row, two steps are required, which can be completed in any order (refer to their corresponding sections in this article for detailed information):
- Configure collection rows for regular pages.
- Enable collection for regular pages.
Note:
- A collection enabled for regular pages can also be used for a dynamic page. However, rows configured for regular pages will remain accessible as a dynamic page record. Any rows configured for regular pages will continue to use the set URL. For example, if a record is using _all_, its URL will be www.yoursite.com/dynamicpage/_all_.
- While _all_ applies to every page on the site, if a row specifies a specific page, it will take precedence.
Configure collection rows for regular pages
Step 1: create a collection (skip this step if the desired collection has already been made)
If you have not already created a collection, see the following documentation for instructions on how to create each type:
For more information, see Dynamic content - collections.
Step 2: configure collection rows for regular pages
When adding an existing page, only the sub-directory portion of the URL is required. For example, if the page URL is www.yoursite.com/about, simply use 'about'.
Internal collections
To configure collection rows for internal collections, modify the data in the Item column to either:
- _all_. Only one record can be set to _all_. Attempting to assign multiple records will result in only the first row changed being saved.
- The URL of the regular page where you would like the row's data to be available. A regular page's URL can only be assigned to one record. Attempting to assign a URL to multiple records will result in only the first row changed being saved.
External, Google Sheets, and Airtable collections
To configure collection rows for internal collections, modify the data in the Item column to either:
- Select the correlating field from the Page item URL drop down (if the collection had previously been set up, this step can be skipped).
- If necessary, navigate to the external collection and update the page item URL in relevant rows to _all_ or the desired existing page’s URL. Only the sub-directory portion of the URL is required. For example, if the page URL is www.yoursite.com/about, simply use 'about'.
If more than one row has an existing page’s URL or _all_, only the first record’s data will be available.
Manage collections for regular pages
Enable a collection for regular pages
After the collection is created, it needs to be enabled to connect to regular pages.
To enable a collection to connect to regular pages:
- In the side panel, click Content.
- Click Collections.
- Next to the desired external collection, click the three horizontal dot icon () and select Enable on Regular Pages.
Disable a collection for regular pages
- In the side panel, click Content.
- Click Collections.
- Next to the desired external collection, click the three horizontal dot icon () and select Disable on Regular Pages.
Connect page elements to collection rows
To connect a widget or canvas element (row and column backgrounds):
-
Right-click on the widget or element you want to connect, and select Connect to Data.
-
Select the desired data using the drop-down (only relevant data options are shown).
-
Select Done.
The Connected Data () icon appears on the widget or element indicating that it is connected.
Limitations
-
Rows must have unique page item URLs. For example, you cannot have two rows with a page item URL of “home”.
-
Multiple rows cannot have a page item URL of _all_. Currently, _all_ applies to all pages on the site, but if you have a specific page being referred to it will take precedence.
-
This is not supported for inline binding in the Text widget. If you need to connect a collection to a regular page using the Text widget, use regular data binding and not inline binding.