If a collection is not visible on the frontend, review the following possible causes and corresponding verification steps.

1. Collection Layout Not Added in Page Builder

A collection will only be displayed if its corresponding layout or component has been added to the page in Page Builder.

Example:

If the homepage is configured with five collections, but only four collection layouts have been added in Page Builder, the fifth collection will not appear on the frontend.

Note: Ensure that the layout added in Page Builder matches the type of collection being rendered.

• If the collection contains stories, assign a Collection of Stories layout in Page Builder.
• If the collection contains other collections (a Collection of Collections), assign a Collection of Collections layout.

Using an incorrect layout type will prevent the collection content from rendering correctly on the frontend, even if the collection is configured properly in the CMS.

2. Collection Slug Mismatch

The collection slug configured in the CMS must match the slug requested by the frontend.

Possible Cause

• The frontend is requesting a collection using a different slug than the one configured in the CMS.

Verification

• Compare the collection slug in the CMS with the slug used in the frontend configuration or API request.
• Update the slug in either the CMS or the frontend configuration so that both values match.

3. No Stories Available in the Collection

A collection with no stories may not be rendered on the frontend.

This commonly occurs when:

• The collection is configured using the Manual Rule.
• No stories have been manually added to the collection.

Verification

• Open the collection and check the number of stories it contains.
• If the collection uses the Manual Rule, ensure that stories have been added manually.
• Verify that any newly added stories have been published.

4. Stories Excluded by Collection Settings

Collections can be configured to exclude stories from specific sections.

If all available stories belong to excluded sections, the collection may appear empty and will not be displayed on the frontend.

Verification

• Review the collection's inclusion and exclusion settings.
• Confirm that the required sections have not been excluded unintentionally.
• Remove any incorrect exclusions and republish the collection if necessary.

5. Collection Has Been Deleted

The collection may no longer exist in the CMS.

Verification

• Search for the collection in the CMS.
• Confirm that it has not been deleted or moved.
• If the collection has been deleted, recreate it or update any references pointing to it.

6. Section Not Linked or Assigned Correctly

Some collections rely on an associated section to display content.

If the linked section is missing, unpublished, or not configured correctly, the collection may not appear on the frontend.

Verification

• Verify that the correct section is assigned to the collection.
• Ensure the section is active and published.
• Review any section-to-collection mappings used by the frontend.

Note: If you need assistance with section-to-collection assignments, please contact [email protected].

Reviewing the above checklist will help identify and resolve the most common reasons why a collection may not appear on the frontend.