Define product content types fields

Let’s use the Kbank demo site as an example. Kbank provides financial products or services. Schema.org) contains detailed information on the recommended fields for financial products.

Each product content type includes essential fields, such as:

• Title
• Slogan or short description
• Associated product image
• Product description.

At this point, you will likely realize that every semantic content type will contain this field combination. You have two options:

• Create these fields in every content type.
• Leverage reusable field schemas, define a collection of core fields, and reuse this core collection in every relevant content type.

Use reusable field schemas for core content across content types

Reusable field schemas allow you to avoid repetitive work. Instead of defining similar fields repeatedly for each content type, you create a schema of fields, such as title, description, image or different taxonomy fields as you can see in the image below.

Each schema defines a set of fields dedicated to a specific use case or scenario. You then add this schema to relevant content types as needed. Xperience reflects your changes to a schema, such as adding or removing, in all linked content types.

Creating the Core Content collection in the Product content type simplifies work for the Kbank team. For editors, it ensures consistency by using the same fields in order across all product and service content types. For developers, it standardizes properties, making it easier to build the presentation layer and saving time in the process. Additionally, the reusable field schema allows developers to create components more efficiently by reducing repetitive tasks.

Make the image reusable

Good-looking images give your marketing communication proper. Placed strategically, pictures or other visuals can spice up ongoing conversations in your customer’s head.

Your marketers rarely use images once; in many cases, they’ll want to reuse the visuals and frame the conversation into one visual context.

Call to action in content

Hero banner of a landing page

Promotional email

Use a dedicated Asset content type to store images and visuals. Your team can upload the file once and reuse it anywhere they need. And if they need to update the image, they’ll just do it once - and their update propagates into all channels and places that reference it.

The image shows a Product content type which contains fields like title, short description, asset/media and taxonomy. The asset/media field references a dedicated Asset content type with fields to store image title, alt text description, internal description, the media file itself, and a taxonomy.