Use Cases



Salesforce Commerce Cloud

This article uses a standardized XML output to generate a Custom content experience served with Commerce Cloud loaded from Zesty.io.

Building out the Content Experience

The first step is to build out the HTML, Javascript and CSS for the content experience you want to serve from your Commerce Cloud website. You can do this in any environment, including locally or within your Zesty.io instance.

Once built, configure the experience in Zesty.io for content editing by building out content models and fields to replace the dynamic pieces with Parsley references.

Starting the XML

The next step is to set up a custom XML endpoint within your Zesty.io instance. Within that paste in this XML code:

Content marked with single brackets, [], will be replaced with Parsley references.

Building out the content models.

To update this XML with dynamic content calls we need to build out the Content Models and fields to replace the variable content pieces in the XML.


First we need a top-level page group for the Folders. This content model needs six fields and it needs one entry for Root, which will act as a top-level indicator.

Field NameField Type
Display NameText
Online FlagYes/No
ParentOne to Many (Relate to: Folders, Display: Display Name)

Content Pages

Next we need to modify all the page type content models created in the first step for generating the content experience. These content models requires 5 fields for the Meta info and any additional fields specific to the html template being created. The 5 required fields are:

Field NameField Type
Display NameText
Online FlagYes/No
Searchable FlagYes/No
Folder ClassificationOne to Many (Relate to: Folders, Display: Display Name)

Updating the XML with Parsley

The next step is putting it all together in Zesty.io. We need to modify the XML to dynamically generate based on the entries available in the Content Models. The new XML Should look something like this.

Notice in this example, we are only generating a custom content experience based on one content model, called Standard Pages. Within the custom-attribute element we include the view file for this content model. The HTML markup for this custom element needs to be written on the standard_pages view file in order for it to be included in the XML. You will want to repeat the loop used for standard_pages in this example for each Content Model that generates a custom content experience.

Importing into Commerce Cloud

The final step is to prompt your Commerce Cloud account to crawl the Zesty.io XML endpoint from your instance. You will want to copy the endpoint URL and paste it into the content import field in Commerce Cloud and submit. This will prompt any new pages or folders to be created and any changes to existing content to be updated.

Connect with Content Experts

Book a free 15-minute consultation with a content expert. Discuss your application, pain points and requirements. Understand how Zesty's lower total cost of ownership, features, functionality can elevate your business by creating extraordinary digital experiences.

Trusted By

zesty customer logo Sonyzesty customer logo Rocket Leaguezesty customer logo Singlifezesty customer logo Acornszesty customer logo Phoenix Sunszesty customer logo Wattpadzesty customer logo Corner Shopzesty customer logo Bjs


zesty customer logo zesty customer logo zesty customer logo zesty customer logo

Enter your details to connect with a Content Expert

First Name

Last Name


Phone (optional)


Please tell us about your project (optional)