---
title: Store core content into reusable field schemas
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

### Store core content into reusable field schemas

While creating a content model or defining the data structure for a content type, you'll often identify that some fields or sets of fields repeat across different content types. For example, all product-related content types will have the same fields to hold _title_, _product description_, _product image_, and core _taxonomy_. Some product-specific fields are similar. Other content types used to promote these products might contain the same structure.

To manage these repetitions efficiently, we recommend using **reusable field schemas** that help you handle such [repeated fields ](https://docs.kentico.com/documentation/developers-and-admins/development/content-types/reusable-field-schemas.md) across different content types.

The following image shows the Kbank demo site's content types for storing products: **Account**, **Card**, and **Loan**.

![Example of reusable field schema](https://docs.kentico.com/docsassets/modules/store-content-in-reusable-schemas/cm-reusable-schema-fields-product-content-type.png "Example of reusable field schema")

All three product content types share two groups of schemas – the _Core content_ schema and _Financial data_ schema. While the _Financial data_ schema is relevant only to the products, the _Core content schema_ stores the same content as other content types in the Kbank demo site. For example, we show two more content types that share the same schema: **Featured content** and **Promotion**.

Note that each content type has dedicated fields relevant only to that specific content type, such as the Minimal inflow or account type in the _Product_ – _Account type_ field or the _External URL_ field in the _Featured content_. See [how to approach modeling taxonomies](https://docs.kentico.com/modules/content-modeling-guide/model-taxonomies.md) to learn more.

### Reusable field schemas from a data perspective

Unlike traditional fields, _reusable field schemas_ give your team flexibility. Both support the same data types, but the [reusable field schemas](https://docs.kentico.com/documentation/developers-and-admins/development/content-types/reusable-field-schemas.md) are stored in the [ContentItemCommonData](https://docs.kentico.com/documentation/developers-and-admins/api/content-item-api/content-item-database-structure.md) table, making them available to every content type. Any changes to a schema also immediately propagate across every content type that references it. However, developers need to ensure that these additional fields display content as intended in the code.

### Compose semantic content types with reusable field schemas and dedicated fields

_Reusable field schemas_ rarely constitute complete semantic content types independently, though they can be part of one. Rather than forcing them into semantic content types, use them to define the smallest minor reusable data structure you want to share across multiple content types and have editors input data intended for use across different channels. This will allow your team to maintain consistency in their data while avoiding redundant work.

### Functional reusable field schemas

_Reusable field schemas_ can store some core content of semantic content types and define functional data structures that different content types reuse. We've already mentioned the _financial data schema_, which editors work in any **Product** content type on the Kbank demo site.

![Financial data reusable field schema](https://docs.kentico.com/docsassets/modules/store-content-in-reusable-schemas/cm-guide-financial-data-schema.png "Financial data reusable field schema")

Similarly, you can define and use an **SEO schema** across every page content type.

![SEO fields in Kbank demo site](https://docs.kentico.com/docsassets/modules/store-content-in-reusable-schemas/cm-seo-reusable-field-schema.png "SEO fields in Kbank demo site")

To allow editors to add reusable parameters to URLs, developers can define a [UTM parameters](https://en.wikipedia.org/wiki/UTM_parameters) schema and assign it to different _call-to-action buttons_, _links_, or _email_ content types to store data they want to track into analytics tools.

Find out which data types Xperience comes with in [Data types](https://docs.kentico.com/documentation/developers-and-admins/customization/field-editor/data-types.md). To support additional data types, you can [add custom data types](https://docs.kentico.com/documentation/developers-and-admins/customization/field-editor/add-custom-data-types.md) to the out-of-the-box set.

### Semantic data in reusable field schemas

You'll identify data that repeats across different content types during a content audit. This might be a _heading_, some _summary text_, a _reference_ to an [asset](https://docs.kentico.com/guides/architecture/content-modeling/content-modeling-guide/store-files.md), or _tags_ from a specific [taxonomy collection](https://docs.kentico.com/documentation/developers-and-admins/configuration/taxonomies.md).

These schemas represent the **Core content** that many of your content types contain. Using a reusable field schema avoids the redundancy of defining similar fields across multiple content types. You can define the **Core content schema** and integrate this schema into other content types. Semantically, they don't specify a content type that you can find in the [schema.org](https://schema.org/). At the same time, they gather crucial information about the content the company produces, meaning they might be considered semantic.

See the _Core content schema_ shared across the products and articles on the Kbank demo site.

![Core content schema in Kbank demo site](https://docs.kentico.com/docsassets/modules/store-content-in-reusable-schemas/cm-guide-content-types-core-content-schema.png "Core content schema in Kbank demo site")

> **Tip:** When creating _field names_, we recommend combining the content type's _name_ with the _field name_, for example, _BenefitDescription_, _ArticleName_, or _ProductTitle_. Developers can access the field's values through _.Fields._ property, for example, _page.Fields.NewsTitle_. Determining the name of the type within the property name will ease some development situations. For instance, in SQL JOINs, you won't need aliases to disambiguate between columns from two or more tables, such as News _Title_ and Product _Title_.