Model a reusable Product

When managing content on a website, we rely on specific content types. These content types serve as templates for creating various content items. This article will explore how to design content types specifically for financial products.

This article will guide you through designing content types for financial products in a way that promotes reusability and adaptability.

Not feeling like reading? Watch the article content in a short video instead.

You’ll learn how to:

  • Create content types that your team can use across various channels.
  • Make your content modeling decisions based on standards.
  • Break down a complex financial product into a reusable content type.

By the end of this article, you’ll be equipped with the knowledge to create compelling content by combining existing reusable content types.

Build for multichannel Xperience by Kentico

Xperience by Kentico provides a multichannel experience, which means you can reuse the same content stored in Xperience on websites, emails, applications, or other marketing channels. When your team needs to add a new channel to promote your services, you don’t need to start the content modeling process from scratch just to display your content in this new channel.

Multichannel Xperience by Kentico

Define content types from reusable pieces

From the beginning, you can design the content types representing significant content entities for your business as reusable and composable from smaller, reusable, and independent content types. These reusable content types will become building blocks that quickly adapt to changing requirements. When you adopt the mindset of building once and reusing everywhere, you can quickly adjust, make your reusable content available in a new channel, and save time and resources.

Simple graph of Product content type

Follow data modeling standards

When it comes to content modeling, it’s always better if you make your decisions based on standards or conventions.

For example, you can find inspiration for content types at Schema.org.

Start with typical content-type fields

In the context of a demo site like Kbank, which provides access to financial products or services, includes detailed information on the recommended fields for financial products.

Each product content type includes essential fields, such as:

  • a title,
  • a slogan or short description,
  • an associated product image,
  • a product description.

Editing product content item in Xperience

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 will 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 banner

Kbank call to action element with reusable image content type

Hero banner of a landing page

Kbank banner with reusable image content type

Promotional email

Promotional email with reusable image

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.

Product content type with reusable Asset content type

See other benefits you can get when you store your assets in a reusable content type.

Identify specific fields for financial services

Given the specificity of financial services, your product content type will include additional fields to store specific financial information, such as:

  • Annual Interest Rate,
  • Maximum Borrowing Amount,
  • Required Collateral,
  • Interest Rate,
  • Loan Duration.

These fields are consistent across all financial services on the website and provide a good case for using reusable field schemas.

Product content type graph showing financial product fields

Store financial data into Reusable field schemas

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. 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.

Find out more about reusable field schemas in the documentation.

Make benefits a separate content type

In any product promotion, it always helps when you can pinpoint the benefits the product brings to the customer.

Product benefits displayed in hero banner widget

From a content modeling perspective, the concept of benefits extends beyond the product. In general, your team might want to promote the company by listing what benefits customers get when they start working with you.

Company benefits displayed in a banner widget

You can create a Benefit content type to help you communicate product or company benefits.

Product content type with linked Benefits content type

Making the benefits a set of data, among other product data, opens new horizons. You will store specific benefits as an individual item, and then you can reuse them in other products. You can highlight particular benefits when promoting the product or your company across various channels, including the website, headless apps, and emails.

Product benefits displayed in a mobile app

Make product features reusable

Product features are little gems of information that, like keys, can unlock a product’s essential aspects in customers’ eyes. If you introduce product features in a way that customers easily understand, they become the secret sauce that makes the product tick.

Storing features into separate content types has two main benefits. First, you’re making your content more modular, thus reusable whenever needed.

Product with linked product features in a separate content type

Secondly, since the feature content type stores just data without any presentation information, you can easily show them in any way - for example, as tabular data.

Product features displayed in a table

Whether comparing features across a range of products, assessing their availability, or even weaving them into price calculators, well-modeled features will help you describe the product to your audience.

Product features in product comparator widget

Taxonomy

Finally, taxonomy. For example, you can create dedicated content types to model relationships between different categories of products and then group them accordingly.

Taxonomy created with a dedicated content type item

Product with linked content item

You’ve seen how you can break a complex financial product into a reusable content type, a composite of other content types.

Product content type in simple graph

Model content for financial services video

See how you can craft content types for financial products.

To sum up:

Making your content model modular and composable makes your content future-friendly. Now, you’re ready to create compelling content by combining existing reusable content types! Happy content modeling.