Wized Docs

Appearance

Collections and Dynamic Pages ​

When working with custom sites that have CMS collections or dynamic pages with similar templates, you can optimize Wized's configurator functionality by creating a manifest.json file.

This helps Wized understand your site structure and detect attributes more efficiently.

Why Use a Manifest File? ​

1. Configurator optimization ​

If your custom site has multiple pages that share the same template and attributes (like blog posts, product pages, team member profiles, etc.), Wized needs to detect the attributes only once per collection instead of scanning every individual page. This significantly improves performance and reduces configuration time.

2. Page Events Functionality ​

This improves page events functionality, allowing you to set up events to run within a specific collection instead of globally across all pages.

Creating the Manifest File ​

Create a file named manifest.json in the root directory of your website with the following structure:

json
{
  "detailPages": {
    "team": "/detail_team",
    "blog": "/detail_blog",
    "products": "/product",
    "case-studies": "/case-study"
  }
}

Structure Explained ​

  • detailPages - An object containing your CMS collections or dynamic page types
  • Key (e.g., "team", "blog") - A unique identifier for your collection
  • Value (e.g., "/detail_team") - The URL path pattern or template page for that collection

How It Works ​

When Wized fetches pages from your sitemap, the manifest.json file tells the configurator:

  1. Which pages belong to the same collection
  2. That these pages share the same template and attributes
  3. To detect attributes only once per collection instead of for every page

For example, if you have 100 blog posts all using the /detail_blog template, Wized will:

  • Detect the attributes from one blog page
  • Apply the same attribute configuration to all other blog pages
  • Save time and improve configurator performance

Example Use Cases ​

Blog with Multiple Posts ​

json
{
  "detailPages": {
    "blog": "/blog-post"
  }
}

E-commerce Site with Products and Categories ​

json
{
  "detailPages": {
    "products": "/product",
    "categories": "/category"
  }
}

Multi-Collection Site ​

json
{
  "detailPages": {
    "blog": "/blog",
    "team": "/team-member",
    "portfolio": "/project",
    "services": "/service"
  }
}

Best Practices ​

  1. Place at root - Ensure manifest.json is in your website's root directory (e.g., https://yoursite.com/manifest.json)

  2. Match URL patterns - The path values should match the actual URL structure of your dynamic pages

  3. Keep it updated - Update the manifest when you add new collections or change URL structures

  4. Test the configuration - After adding the manifest, verify in the Wized configurator that your collections are detected correctly

  5. Use descriptive keys - Choose clear, meaningful names for your collection identifiers