Model product taxonomies

In Xperience, taxonomies allow editors to organize and categorize content efficiently. Using tags, which can be structured hierarchically, editors can apply multiple taxonomy groups to a single content type, creating a flexible way to manage information.

For example, the Kbank demo site contains different taxonomy groups. The goal of Products in Kbank is to show how you can use the taxonomy feature and support various scenarios.

• Core taxonomy: Provides semantic tags to further refine different content types into various topics and categories.
• Currencies taxonomy: Identifies the currency in which a financial service is available and helps global users understand their options.
• Regional Availability taxonomy: Specifies the countries where products or services are offered and supports the website’s localization.
• Financial Information taxonomy: Defines attributes for financial product features, such as eligibility criteria or availability.

These examples demonstrate how you can approach modeling product-specific taxonomies in Xperience to help editors structure content while maintaining consistency and scalability.

For example, you can create dedicated content types to model relationships between different product (and other content type) categories and then group them accordingly.

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

The image contains a comprehensive content model diagram for a Product – Account content type. It shows how the product content type comprises of taxonomies, reusable schemas, and related content types.

The Product – Account content type includes core schema fields such as title, short description, media, taxonomy, and product details, where media fields references a standalone Asset content type with fields for a title, alt text or media file, and taxonomy is built through the taxonomy feature.

Benefits and Product features are built through a reference to dedicated content types, where Benefits store data like description or icon, while Product features contain fields for a label, key, price, value or a dedicated taxonomy group that defines availability of each feature.

It also contains multiple financial fields like annual percentage rate, interest rate defined through reusable field schemas, and two fields that reference dedicated taxonomies – Currencies and Regional availability.

Finally, the product contains this product’s specific fields to store minimal inflow requirements, and overdraft limits.