Creating a Content Record

This topic applies to

Applies to

SuiteCommerce Web Stores

Content records collect information about media and files you want to display. You then define delivery rules with the Content Delivery SuiteApp. The New Content Record is accessed when defining main body content for Landing Pages, or when defining Content Rules for either Landing Pages or Content Records as described in Using Content Delivery.

When creating a new Content Record, you select one of two types, Merchandising Rule or HTML.

Using a Merchandising Rule

Only previously defined Merchandising Rules are available for selection. Simply select the desired rule and then click Save. For details on defining Product Merchandising rules, refer to Product Merchandising.

Using HTML

You can use your own custom HTML elements to define the content displayed. HTML content can be defined for your record in one of two ways:

  • File: Select this to use an existing HTML file. This file must first be uploaded into the file cabinet. Although you can store these files anywhere in your file cabinet, it is recommended that you keep them with other website files in the folder at Web Site Hosting Files > Live Hosting Files.

  • Text Editor: Use the WYSIWYG editor to define the Content. Type your content in the Content field and using the built-in editor apply special formatting as desired.

Note

When the Type field is set to image, enter the url for the image. The url entered is an absolute path from your Live Hosting Files/site folder. This is normally the top images folder. For example /images/navbar.jpg.


You can also embed client-side JavaScript to add custom logic to your Content Delivery pages.

Note

If using jQuery methods in your logic you must use the jQuery prefix and not the $ prefix. For example, use jQuery(document).ready(function(){alert(”Hello World”);}); instead of $(document).ready(function(){alert(”Hello World”);});.


Important

Although you can add client-side JavaScript to Content Delivery records, you cannot reference external JavaScript libraries in Content Delivery records. External libraries must be referenced from the SSP application files or by using more comprehensive customization techniques.