---
title: Glossary
---
> 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).
This glossary provides an overview of Xperience by Kentico terminology you may encounter when using the product or reading the documentation. The intended audience is all roles interacting with the system, from technical (developers, administrators) to business users (content editors, marketers).
You don't need to learn all these terms by heart, but you can use the tables below as a reference if you encounter a new phrase while working with the system. If you think an important term is missing from this reference, leave us feedback via the _Send us feedback_ button at the bottom of the page.
### Categories
## General
| Term | Description |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Administration | The Xperience administration interface is a graphical interface for Xperience functionality that allows you to set up and configure websites and manage their content. Users manage websites via _applications_ within the interface. In the background, the administration application accesses and modifies the database shared with the live site application. |
| Application | Applications group together features and related functionality. They display information related to the encapsulated functionality and enable related tasks and configuration. For example, the _Languages_ application allows you to manage and configure languages for the content of your project's channels. |
| Application dashboard | The application dashboard is the first page you see when signing in to the Xperience administration. The dashboard provides quick access to applications. Applications and objects on the dashboard have the form of tiles. You can return to the dashboard from any part of the system by clicking the Home icon in the administration header. |
| ASP.NET Core | ASP.NET Core is an open-source framework for building web applications. ASP.NET Core framework supports the MVC architecture and other modern approaches. |
| Code name | A code name refers to text that serves as a unique identifier of an object in Xperience. Most objects also have a Display name – human-readable text displayed in the administration. Code names for certain objects can be pre-filled by a value generated from the Display name or, alternatively, can be set manually. |
| Continuous Integration | [Continuous Integration](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/continuous-integration.md) allows users (usually developers) to serialize data from the database into XML files on the file system. These files can then be added to a source control system and used to synchronize database data between different Xperience instances. |
| Cookie level | The [cookie level](https://docs.kentico.com/documentation/developers-and-admins/data-protection/cookies.md) is a scale used to implement cookie policy in Xperience. The cookie level set for each visitor controls which cookies get stored in their browser, as different cookies used by the Xperience system require different cookie levels. |
| Dancing Goat | Dancing Goat is a sample website project that showcases the features of the Xperience platform. Suitable for evaluating or demonstrating the capabilities of the system. |
| Display name | A display name refers to the text displayed in the administration interface to identify an object or interface element. Most objects also have a Code name – a unique identifier for the object in the system. |
| Event log | The [event log](https://docs.kentico.com/documentation/developers-and-admins/configuration/event-log.md) is a monitoring and troubleshooting tool that can be accessed directly within the Xperience administration. It allows administrators to view important system events and errors, enabling quick identification and resolution of application issues.
The event log captures and displays data provided by general logging functionality, which is based on [.NET logging](https://learn.microsoft.com/en-us/dotnet/core/extensions/logging). Developers can adjust the verbosity of the logged information, perform logging in custom code, and integrate third-party logging or telemetry tools. See [Logging](https://docs.kentico.com/documentation/developers-and-admins/development/logging.md). |
| Live site application | An application that provides a presentation layer for the content managed by Xperience. |
| Notification | Messages that provide information to administration users about various events in the system. In the current version of Xperience by Kentico, [notifications](https://docs.kentico.com/documentation/developers-and-admins/configuration/notifications.md) are system emails providing information about user management events, such as [password reset emails](https://docs.kentico.com/documentation/developers-and-admins/configuration/users/user-management.md#reset-password) or [multi-factor authentication](https://docs.kentico.com/documentation/developers-and-admins/configuration/users/user-management.md#multi-factor-authentication), and about [workflow step changes](https://docs.kentico.com/documentation/developers-and-admins/configuration/workflows.md#workflow-notifications). |
| Notification email template | [Notification email templates](https://docs.kentico.com/documentation/developers-and-admins/configuration/notifications.md#notification-email-templates) define the overall layout of notifications and add fixed content, such as a header or footer. You can reuse a single template for any number of notifications. They contain [macros](https://docs.kentico.com/documentation/developers-and-admins/configuration/notifications.md#notification-template-macros) that serve as placeholders for certain elements, such as basic data types. Notification email templates serve a distinct purpose from [email templates](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/email-templates.md) related to [email channels](https://docs.kentico.com/documentation/business-users/digital-marketing/emails.md), focusing specifically on structuring and styling notification emails. |
| Private cloud | A term that encapsulates all forms of hosting other than Kentico's [SaaS](#saas) offering, for example:
Managed or unmanaged cloud hosting providers like Microsoft Azure, Amazon AWS, GCP, and DigitalOcean (on Windows or Linux).
Hybrid cloud combining public cloud and private hosting.
Fully private data center hosting on traditional VMs.
Used primarily in [hosting and deployment](https://docs.kentico.com/documentation/developers-and-admins/deployment/deploy-to-private-cloud.md)-related materials. |
## SaaS
| Term | Description |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| SaaS | Though _SaaS_ commonly stands for _Software-as-a-Service_, in the documentation, the term is generally used for Kentico's [Xperience by Kentico as SaaS](https://docs.kentico.com/documentation/developers-and-admins/saas.md) offering and the underlying cloud services that support the SaaS environment and deployed projects. The term is also used when discussing related topics such as:
Kentico-managed deployment environment for Xperience applications – SaaS environment
Xperience projects that are deployed to the SaaS environment – SaaS projects
Deployment of an Xperience project to a specific SaaS environment – SaaS deployment |
| Deployment environment | You can deploy your SaaS projects to various [SaaS environments](https://docs.kentico.com/documentation/developers-and-admins/deployment/deploy-to-the-saas-environment.md#deploy-the-package-to-another-deployment-environment). The available options include production (**STG**, **PROD**) and non-production (**QA**, **UAT**, custom) environments.
Each deployment environment holds a single isolated instance of your Xperience application. |
| Xperience Portal | [Xperience Portal](https://docs.kentico.com/documentation/developers-and-admins/saas/xperience-portal.md), available at [xperience-portal.com](https://xperience-portal.com), is a Kentico-managed application that enables you to access and manage your Xperience Portal projects. |
| Xperience Portal project | An Xperience Portal project enables you to access and manage Xperience applications deployed in the [SaaS environment](https://docs.kentico.com/documentation/developers-and-admins/deployment/deploy-to-the-saas-environment.md). |
## AI-powered tools and related vocabulary
| Term | Description |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| AIRA | [AIRA](https://docs.kentico.com/documentation/business-users/aira.md) is an AI-powered agent integrated into Xperience by Kentico. It helps users automate and streamline marketing and content management tasks. AIRA capabilities include [in-product guidance](https://docs.kentico.com/documentation/business-users/aira.md#aira-in-product-guidance) on features and best practices, [customer journey insights](https://docs.kentico.com/documentation/business-users/aira.md#customer-journey-insights), image processing features (focal point selection, description generation, and tag assignment), [content translations](https://docs.kentico.com/documentation/business-users/aira.md#aira-translations), [rich text refinements](https://docs.kentico.com/documentation/business-users/aira.md#rich-text-editor-refinements), and [content generation](https://docs.kentico.com/documentation/business-users/aira.md#content-generation-and-refinements).
Additionally, the [AIRA Agentic Marketing Suite](https://docs.kentico.com/documentation/business-users/aira/agentic-marketing-suite.md) provides further capabilities through dedicated agents, such as the [Content Strategist](https://docs.kentico.com/documentation/business-users/aira/agentic-marketing-suite.md#content-strategist) for content quality reviews, and the [Customer Journey Optimization Specialist](https://docs.kentico.com/documentation/business-users/aira/agentic-marketing-suite.md#customer-journey-optimization-specialist) for improving customer journey conversion rates. |
| Artifact | A saved output created or used by an AIRA agent. For the [Content Strategist](https://docs.kentico.com/documentation/business-users/aira/agentic-marketing-suite.md#content-strategist), the key artifact is your Content Strategy document. This document is the single source of truth for voice attributes, tone expectations by type of content, style rules, and target personas. The agent evaluates content against this document. If you don't have a Content Strategy yet, AIRA can guide you through creating one through a series of questions and answers within the [AIRA in-product guidance](https://docs.kentico.com/documentation/business-users/aira.md#aira-in-product-guidance). |
| Agent | An AI-driven specialist that operates within the Xperience by Kentico administration interface as part of the [AIRA Agentic Marketing Suite](https://docs.kentico.com/documentation/business-users/aira/agentic-marketing-suite.md). Each agent has its own area of expertise and a dedicated set of tools it can use to complete tasks. When you interact with [AIRA](https://docs.kentico.com/documentation/business-users/aira.md#aira-in-product-guidance), the system automatically selects the right agent based on your current context and prompt. |
| Documentation MCP server | A [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server provided by Kentico that allows AI agents to access up-to-date official documentation, including guides and API examples, directly within your IDE. The [Documentation MCP server](https://docs.kentico.com/documentation/developers-and-admins/installation/mcp-server.md) provides information on all areas of Xperience by Kentico (content management, digital marketing, digital commerce, etc.). It is compatible with all AI tools or IDEs that support MCP. |
| KentiCopilot | [KentiCopilot](https://docs.kentico.com/guides/development/kenticopilot.md) is an initiative to help developers effectively and responsibly adopt AI in developing Xperience by Kentico projects. It provides tools, features, and educational materials to accelerate development workflows. This includes [pre-configured skills and plugins](https://github.com/Kentico/xperience-by-kentico-kenticopilot) for AI coding assistants, best practices for AI-assisted development, and resources for tasks such as widget implementation, content migration, and content modeling. |
| Management MCP server | A [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server provided by Kentico that allows AI tools to discover and use a management API for querying, creating and editing objects in the system. The server makes it easy for AI tools to manage Xperience objects, such as content types, Page Builder components, and their configuration. It is available through the [@kentico/management-api-mcp](https://www.npmjs.com/package/@kentico/management-api-mcp) npm package.
See [Management MCP server](https://docs.kentico.com/documentation/developers-and-admins/api/management-api.md) for detailed information. |
## Content management
| Term | Description |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Website channel | [Website channels](https://docs.kentico.com/documentation/developers-and-admins/configuration/website-channel-management.md) encapsulate websites managed by Xperience. Each channel is an [independent entity](https://docs.kentico.com/documentation/developers-and-admins/configuration/website-channel-management/manage-multiple-websites.md) with its own domain name configuration and content management. Channels store content in pages and linked content items.
Every website channel has its own application in the Xperience administration, where content editors [create and edit pages](https://docs.kentico.com/documentation/business-users/website-content.md). |
| Content model | A [content model](https://alistapart.com/article/content-modelling-a-master-skill/) documents all the content that an organization produces. It should cover every piece of content used for your online presence: content used on your website, applications, different marketing channels, etc. |
| Content folder | A hierarchy of [content folders](https://docs.kentico.com/documentation/business-users/content-hub/content-hub-folders.md#content-folders) can be used to organize and efficiently navigate through content items in the _Content hub_ application. Content items are placed into content folders manually, and each item can only be located in one content folder. |
| Content type | [Content types](https://docs.kentico.com/documentation/developers-and-admins/development/content-types.md) define a blueprint for any piece of content that editors produce. Each content type defines a specific structure and fields for inputting and storing data.
Typical content type examples are articles, news, or product pages. Website structure can also contain content types that represent much smaller pieces of information, such as videos, addresses of offices, or user testimonials. These content types are often repeated in different places or contexts across the website, thus making the content reusable.
In Xperience, content types also enable page features of content items, such as content tree-based routing or Page Builder. |
| Content item | [Content items](https://docs.kentico.com/documentation/business-users/content-hub.md) are a universal and reusable way of working with content managed in the _Content hub_ application. Content items are pieces of structured content (text, images, other linked content items, etc.). Each content item is based on a content type, which specifies the fields and features of the content item. |
| Content item asset | [Content item assets](https://docs.kentico.com/documentation/business-users/content-hub/content-item-assets.md) are content items of certain content types that allow content editors to upload and store various types of files, for example, photos, pictures, sound files, videos, package files, presentations, or documents. You can reuse assets stored in the _Content hub_ throughout the system. |
| Content lock | A [content lock](https://docs.kentico.com/documentation/business-users/content-locking.md) prevents concurrent edits to a [page](https://docs.kentico.com/documentation/business-users/website-content.md), [content item](https://docs.kentico.com/documentation/business-users/content-hub/content-items.md), [headless item](https://docs.kentico.com/documentation/business-users/headless-content.md), or [email](https://docs.kentico.com/documentation/business-users/digital-marketing/emails.md). When content locking is [enabled](https://docs.kentico.com/documentation/developers-and-admins/configuration/content-locking-configuration.md#enable-content-locking), the system automatically locks an item when a user begins editing and releases the lock when the item is published, moved to another [workflow step](https://docs.kentico.com/documentation/developers-and-admins/configuration/workflows.md), or manually released. Only the user holding the lock can edit the item's content. Administrator and designated users can override the content lock when required. |
| Content reuse locator | Content reuse locator refers to a collection of features that help users track where [content items](https://docs.kentico.com/documentation/business-users/content-hub/content-items.md#track-usage-of-content-items), [pages](https://docs.kentico.com/documentation/business-users/website-content/track-page-usages.md) and [forms](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md#track-usage-of-forms) are displayed or otherwise used across your channels.
In the administration interface, the feature is available under the _Used in_ tab when viewing specific items. |
| Headless channel | [Headless channels](https://docs.kentico.com/documentation/developers-and-admins/configuration/headless-channel-management.md) encapsulate content that is intended to be served using HTTP requests and [GraphQL](https://graphql.org/). Such headless content can be displayed or otherwise consumed by various types of applications, services or websites (e.g., mobile apps, external websites, single-page applications running within Xperience, etc.).
Every headless channel has its own [GraphQL API endpoint](https://graphql.org/learn/serving-over-http/), which is secured by one or more API keys. Each channel also has its own application in the Xperience administration, where editors can [manage content](https://docs.kentico.com/documentation/business-users/headless-content.md) intended for headless distribution. |
| Headless content item | [Headless items](https://docs.kentico.com/documentation/business-users/headless-content.md) store content that is intended for distribution through a headless API ([GraphQL](https://graphql.org/)). The items may also reuse content from [Content hub](https://docs.kentico.com/documentation/business-users/content-hub.md) that is shared between all types of channels. |
| Item status | Each page, content item, headless item and email has a status that describes its current position within the content lifecycle. This can be a specific workflow step, another status such as **Untranslated** or **Unpublished**, or a sending status for [regular emails](https://docs.kentico.com/documentation/business-users/digital-marketing/emails/send-regular-emails-to-subscribers.md). |
| Language | [Languages](https://docs.kentico.com/documentation/developers-and-admins/configuration/languages.md) are system objects that enable content editors to create multilingual content. Once languages are configured in the _Languages_ application, content can be translated in the _Content hub_ or in channel applications.
Instances of content items (pages, emails, reusable content) translated into various languages are referred to as language variants of said content item. |
| Media library | [Media libraries](https://docs.kentico.com/documentation/business-users/media-libraries.md) allow you to store various types of files, for example, photos, pictures, sound files, videos, package files, presentations, or documents. You can reuse files stored in media libraries throughout the system.
**Note:** Support for media libraries ended on 24 July, 2026. The feature was hidden in the admin UI for projects that have no media libraries in the **August 2026** Refresh, and the feature and all associated APIs will be fully removed in the **September 2026** Refresh. It is strongly recommended to transition to using [content item assets](https://docs.kentico.com/documentation/business-users/content-hub/content-item-assets.md) for managing files within the system. See [Media library migration](https://docs.kentico.com/guides/architecture/media-libraries-migration-guidance.md) for instructions on how to migrate your media library files to [Content hub](https://docs.kentico.com/documentation/business-users/content-hub.md). |
| Microchannel | Microchannels represent channels which can only contain a limited number of content items of the specific channel type:
[Website channels](https://docs.kentico.com/documentation/developers-and-admins/configuration/website-channel-management.md) – at most **20** items within the channel's page tree, including both standard pages with URLs and other items like folders or navigation menu structure.
[Headless channels](https://docs.kentico.com/documentation/developers-and-admins/configuration/headless-channel-management.md) – at most **20** headless items.
[Email channels](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/email-channel-management.md) – at most **5** emails. The limit restricts the maximum number of email content items allowed in the microchannel, but not how many times these emails can be sent to recipients. Email microchannels are available in all license tiers (standard size email channels require the _Advanced_ license tier).
Individual microchannel items of any type can link an unlimited number of [reusable content items](https://docs.kentico.com/documentation/business-users/content-hub.md).
You can freely change between the _microchannel_ and _standard_ channel size of existing channels via the **General** tab. Additionally, changing _standard_ channels to _microchannels_ does not cause any data loss in case the converted channel exceeds microchannel limits. However, you will receive a license violation warning if the resulting channel or item count oversteps the limits of your license for that particular channel type. |
| Page | [Pages](https://docs.kentico.com/documentation/business-users/website-content.md) are a special type of content item created in a website channel. A page in the system usually corresponds to a page on your website. Pages can contain Page Builder content or structured content within their fields and can be accessed via a URL. |
| Smart folder | [Smart folders](https://docs.kentico.com/documentation/business-users/content-hub/content-hub-folders.md#smart-folders) provide a way for users to dynamically organize and filter content items in the _Content hub_ application. Developers can also [retrieve content from smart folders](https://docs.kentico.com/documentation/developers-and-admins/development/content-retrieval/retrieve-content-items.md#retrieve-content-items-from-smart-folders), which allows editors to control delivery of content that is displayed or otherwise used in channels (e.g., on the live website).
Each smart folder is based on a filtering condition, such as "items modified in the last 7 days", "items with the _Acme_ tag", etc. The condition is evaluated dynamically, so items move in and out of smart folders as their fields and metadata change. A single content item can belong into any number of smart folders. |
| System URL | System URLs are default URLs [generated from the page's position in the content tree](https://docs.kentico.com/documentation/developers-and-admins/development/routing/content-tree-based-routing.md) using the page's URL slug and URL slugs of the page's ancestors. |
| Rich text widget | The [Rich text widget](https://docs.kentico.com/documentation/business-users/rich-text-editor.md) allows editors to add styled content to Page Builder pages. |
| Tag | [Tags](https://docs.kentico.com/documentation/developers-and-admins/configuration/taxonomies.md) are keywords assigned to individual pieces of data. Tags can be assigned to individual pieces of content for multiple purposes including but not limited to modeling relationships, categorization, and organization and classification of data. Tags are defined in a hierarchical structure in a taxonomy. |
| Taxonomy | [Taxonomies](https://docs.kentico.com/documentation/developers-and-admins/configuration/taxonomies.md) are structured collections of tags that organize and categorize data into hierarchical relationships. Each taxonomy contains a hierarchical structure of related tags. Examples of taxonomies are clothing colors (white, black, blue...), car fuel types (petrol, diesel, hybrid...), and PC features (external GPU, disc drive, tower size...). |
| Translation queue | _Translation queue_ is a queue of items to be [translated using aira](https://docs.kentico.com/documentation/business-users/aira.md#aira-translations). The queue only contains items which were sent for translation in bulk, for example using [mass translation](https://docs.kentico.com/documentation/business-users/content-hub/content-items.md#mass-translating). Items which are being currently translated and items waiting in the queue can be viewed in the Translation queue application. |
| Vanity URL | [Vanity URLs](https://docs.kentico.com/documentation/business-users/website-content/manage-page-urls.md#edit-vanity-urls-of-pages) are alternative URLs that can be configured and customized by marketers. Vanity URLs allow marketers to specify short and recognizable URLs for marketing, sharing, and branding purposes. |
| Workflow | [Workflows](https://docs.kentico.com/documentation/developers-and-admins/configuration/workflows.md) allow you to customize the lifecycle of content types by adding custom workflow steps between the default **Draft** and **Published** steps. You can use workflows to set up content approval processes tailored specifically to your editing flow. |
| Workflow step | A step represents a specific phase within a workflow, which can include both custom steps and predefined steps such as **Draft** and **Published**. |
| Workspace | [Workspaces](https://docs.kentico.com/documentation/developers-and-admins/configuration/users/role-management/workspaces.md) allow you to create a designated environment within the system where workspace-scoped applications are grouped together. |
## Page Builder
| Term | Description |
| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Component | Page Builder components are the building blocks of the Page Builder interface. They include [widgets](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder/widgets-for-page-builder.md), [page templates](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder/page-templates-for-page-builder.md), [sections](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder/sections-for-page-builder.md), and [personalization condition types](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/content-personalization/develop-personalization-condition-types.md). |
| Component configuration properties | [Component properties](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder/widgets-for-page-builder/widget-properties.md) are variables that allow content editors to customize a component’s behavior or modify its content directly in the Page Builder interface. Developers define these properties when developing individual Page Builder components. |
| Editable area | [Editable areas](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder/create-pages-with-editable-areas.md) are the top-level layout elements that limit where the Page Builder interface is available. Developers define editable areas in the code of page or template views. |
| Editing component | The documentation uses the term [editing components](https://docs.kentico.com/documentation/developers-and-admins/customization/extend-the-administration-interface/ui-form-components/editing-components.md) when referring to UI form components used as editors for the values of other component properties. For example, a text input form component becomes an editing component when used to edit a widget property via the widget's configuration dialog. |
| Inline editor | [Inline editors](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder/widgets-for-page-builder/inline-editors-for-widget-properties.md) are interactive Page Builder elements that allow content editors to enter or select the values of widget properties within the output of the related widget. They can be used as an alternative to or in combination with the property configuration dialog. For example, inline editors can range from simple value inputs to more advanced options, such as file uploaders or text areas with rich formatting options. |
| Landing page | Landing pages are one of the primary use cases for Page Builder. Landing pages are created specifically for marketing purposes. They are places where potential customers get redirected after clicking a link in an email or on a social network. |
| Page Builder | Page Builder is a graphical interface for designing and editing pages in Xperience. It uses widgets, modular components [prepared by the developers](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder.md), and other features to set the page layout and content. |
| Page template | Page templates allow content editors to choose from predefined layouts for new pages. |
| Personalization condition | [Personalization conditions](https://docs.kentico.com/documentation/business-users/digital-marketing/widget-personalization.md) are a digital marketing feature supported by Page Builder widgets. The conditions allow editors to display different content per visitor. For example, you can show modified text or additional offers to visitors from a specific contact group. |
| Section | [Sections](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder/sections-for-page-builder.md) are reusable Page Builder components that determine where widget zones can be placed. Sections are fully customizable, and developers control each section's layout. In the Page Builder interface, content editors can choose which sections to add to a page and adjust the structure that way. A section may contain multiple widget zones. |
| Widget | [Widgets](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder/widgets-for-page-builder.md) are reusable Page Builder components that content editors and other non-technical users can easily manipulate. Widgets give non-technical users more flexibility when creating pages or adjusting existing content. |
| Widget zone | Widget zones are individual areas within a Page Builder section where content editors can place widgets. |
## Email Builder
| Term | Description |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Component | [Email Builder components](https://docs.kentico.com/documentation/developers-and-admins/development/builders/email-builder/develop-email-builder-components.md) are the building blocks used to create emails in the Email Builder interface.
Email Builder components are implemented using [ASP.NET Blazor](https://learn.microsoft.com/en-us/aspnet/core/blazor/) as [Razor components](https://learn.microsoft.com/en-us/aspnet/core/blazor/components/). |
| Editable area | [Editable areas](https://docs.kentico.com/documentation/developers-and-admins/development/builders/email-builder/develop-email-builder-components.md#editable-areas) are parts of email templates that can be edited using the Email Builder visual interface. Developers define editable areas in the markup of templates. |
| Editing component | The documentation uses the term [editing components](https://docs.kentico.com/documentation/developers-and-admins/customization/extend-the-administration-interface/ui-form-components/editing-components.md) when referring to UI form components used as editors for the values of other component properties. For example, a text input form component becomes an editing component when used to edit a widget property via the widget's configuration dialog. |
| Email Builder | Email Builder is a graphical interface for designing and editing [emails](https://docs.kentico.com/documentation/business-users/digital-marketing/emails.md) in Xperience. It uses modular components prepared by developers to set the email layout and content. |
| Inline editor | [Inline editors](https://docs.kentico.com/documentation/developers-and-admins/development/builders/email-builder/inline-editors-email-builder-widgets.md) are interactive Email Builder elements that allow content editors to enter or select the values of widget properties within the output of the related widget. They can be used as an alternative to or in combination with the property configuration dialog. For example, inline editors can range from simple value inputs to more advanced options, such as a rich text editor. |
| MJML | MJML (Mailjet Markup Language) is a framework for easily creating responsive emails. Every Xperience project can be configured to use either standard HTML or MJML markup for Email Builder components. You **cannot combine both markup types** for different components within a single project.
To learn more about the MJML markup language, see [MJML Guides](https://documentation.mjml.io/#mjml-guides). |
| Section | [Sections](https://docs.kentico.com/documentation/developers-and-admins/development/builders/email-builder/develop-email-builder-components.md#sections) are reusable Email Builder components that specify a layout for email content, typically containing one or more columns. Sections contain one or more widget zones where editors can add widgets in the Email Builder visual interface. |
| Template | [Templates](https://docs.kentico.com/documentation/developers-and-admins/development/builders/email-builder/develop-email-builder-components.md#templates) are the top-level Email Builder component that sets the email’s overall design, as well as any fixed content, such as a header and footer. Templates contain editable areas that can be edited in the Email Builder visual interface.
The system uses two types of email templates – the Email Builder templates described above, and [email templates](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/email-templates.md) that are created in the administration UI using HTML markup and macros. |
| Widget | [Widgets](https://docs.kentico.com/documentation/developers-and-admins/development/builders/email-builder/develop-email-builder-components.md#widgets) are reusable components that represent individual pieces of email content, such as text, images, CTA links, etc. Content editors and other non-technical users can easily work with widgets in the Email Builder visual interface. Widgets are placed into widget zones. |
| Widget zone | Widget zones are placed within [Email Builder sections](https://docs.kentico.com/documentation/developers-and-admins/development/builders/email-builder/develop-email-builder-components.md#sections), and allow content editors to insert widgets. Each zone can contain any number of widgets (depending on the design limitations of the parent template and section). |
## Form Builder
| Term | Description |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Form Builder | The Xperience [Form Builder](https://docs.kentico.com/documentation/developers-and-admins/development/builders/form-builder.md) offers an intuitive graphical editor that allows content creators and marketers to compose online forms. It is available on the _Form Builder_ tab of the _Forms_ application when [editing a form](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md). |
| Form component | [Form components](https://docs.kentico.com/documentation/developers-and-admins/development/builders/form-builder/form-components.md) are reusable elements used to create and edit forms in Form Builder. Each component represents a form input type, such as a text box or a group of radio buttons. Users can add, remove, or reorder individual form components and specify their properties via the form builder interface in the _Forms_ application. |
| Form section | [Form sections](https://docs.kentico.com/documentation/developers-and-admins/development/builders/form-builder/form-sections.md) define the layout of forms. They represent reusable pieces of markup that can store any number of form zones – areas where content editors can place form fields. |
| Form widget | The [form widget](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/display-forms-on-pages.md) is provided in Kentico Xperience by default. It allows editors to place forms into the content of pages that use Page Builder. The _Form_ widget can be found only when editing pages in the _Page Builder_ within a website channel application. |
| Validation rule | Validation rules restrict which values can be submitted into form fields. For example, validation rules can limit the maximum number of characters or the maximum numerical value a user can enter into a field. Editors can [add validation rules](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md#field-validation) when configuring individual fields in the Form Builder UI.
Developers can implement custom validation rules as described in [Form Builder validation rules](https://docs.kentico.com/documentation/developers-and-admins/development/builders/form-builder/form-builder-validation-rules.md). |
| Visibility condition | Visibility conditions control when and how form fields are displayed to users. The conditions are always based on the value of another field in the form. For example, a "Company name" field can be configured to only appear when users select "Business" in a preceding "Account type" field, keeping the form clean and relevant for individual users.
Editors can [add a visibility condition](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md#field-visibility) when configuring individual fields in the Form Builder UI. The system provides a set of visibility conditions for common scenarios. Development of custom conditions is currently not supported. |
## Digital marketing
| Term | Description |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Activity | [Activities](https://docs.kentico.com/documentation/business-users/digital-marketing/contact-activities.md) represent actions that website visitors perform on the live site. For example, the system logs activities when visitors view pages or submit forms. |
| Automation | [Automation](https://docs.kentico.com/documentation/business-users/digital-marketing/automation.md) allows you to set up processes that dynamically interact with your audience (contacts). Each process is triggered by a selected event, and consists of steps that perform marketing actions, such as sending emails, logging activities, or setting contact field values. Automation also supports steps that control the flow of contacts within the process – branching conditions and wait steps.
Developers can extend automation with [custom steps](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/automation-customization/automation-custom-steps.md) (actions and conditions) and [triggers](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/automation-customization/automation-custom-triggers.md) for project-specific logic, such as CRM synchronization, notifications, or starting processes from custom application events. |
| Campaign | [Campaigns](https://docs.kentico.com/documentation/business-users/digital-marketing/campaigns.md) provide a central location for creating, coordinating, running and evaluating marketing campaigns in Xperience by Kentico. They bring together all related content assets (pages, emails, forms, etc.), and use a [customer journey](https://docs.kentico.com/documentation/business-users/digital-marketing/customer-journeys.md) to represent the campaign's goals and expected path of the target audience.
The [Campaign Manager](https://docs.kentico.com/documentation/business-users/aira/agentic-marketing-suite.md#campaign-manager) agent helps marketers work efficiently by providing AI-assisted campaign planning, asset readiness checks, and performance evaluation. |
| Contact | [Contacts](https://docs.kentico.com/documentation/business-users/digital-marketing/contact-management.md) represent individual visitors who view your websites. Contacts include anonymous visitors and users who provide personal information by registering, filling in a form, subscribing, etc. The system automatically gathers data about contacts based on the actions and input of the associated visitors. |
| Contact group | [Contact groups](https://docs.kentico.com/documentation/business-users/digital-marketing/contact-groups.md) are segmentation units that enable you to sort contacts. The system populates groups automatically based on dynamically evaluated conditions. When [customer data platform](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/customer-data-platform.md) is enabled, [segments](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/customer-data-platform/segments.md) provide an alternative segmentation mechanism for profiles. |
| Customer journey | [Customer journeys](https://docs.kentico.com/documentation/business-users/digital-marketing/customer-journeys.md) map out how contacts interact with your content. You can define key stages in a journey, representing the sequence of steps a contact must complete to achieve a successful conversion and set conditions for their progression through the stages. |
| Email channel | [Email channels](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/email-channel-management.md) are a dedicated medium of communication between you and your audience. Each project may contain multiple email channels, focusing on different content strategies, languages and audience engagement techniques.
Every email channel has its own application in the Xperience administration, where marketers create and send emails.
Channels allow for clean separation of your organization's emails. The defining property of every email channel is a _sending domain_, which represents your company or brand, and is used in all _sender addresses_ for the channel's emails. |
| Email | The system allows marketers to create and send [emails](https://docs.kentico.com/documentation/business-users/digital-marketing/emails.md) with various different purposes, such as form autoresponders or regular emails sent to subscribed recipients.
Every email belongs under an email channel, and is based on an email content type and email template. |
| Email template | [Templates](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/email-templates.md) define the overall layout of emails and add fixed content, such as a header or footer. You can reuse a single template for any number of emails.
Templates contain macros that serve as placeholders for the fields of email content types, as well as system elements, such as a regular email's unsubscribe link URL.
The system uses two types of email templates – the macro-based email templates described above, and [Email Builder templates](https://docs.kentico.com/documentation/developers-and-admins/development/builders/email-builder/develop-email-builder-components.md#templates) which are prepared by developers in the project's code as Razor components. |
| Recipient list | A mailing list containing contacts who [opt in to receive regular emails](https://docs.kentico.com/documentation/business-users/digital-marketing/emails/send-regular-emails-to-subscribers.md). Marketers select a recipient list when sending out emails. |
### Customer data platform
| Term | Description |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Customer data platform | [Customer data platform](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/customer-data-platform.md) is a collection of features that expand, rework and improve the contact management functionality in Xperience by Kentico. Customer data platform is optional and needs to be enabled by developers. Switching back to a disabled state is not possible and migration of existing digital marketing data is currently not supported.
At this time, customer data platform is a preview feature with a [limited scope](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/customer-data-platform.md#supported-features). Many of the Xperience by Kentico digital marketing features are not supported yet. |
| Identity resolution | Identity resolution is the process of identifying profiles that represent the same person based on shared identifying information, such as an email address. When matching profiles are detected, the system automatically merges them into a single unified profile. Identity resolution rules are configured in the **Customer data management** application. See [Profile identity resolution and merging](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/customer-data-platform/identity-resolution.md). |
| Profile | Profiles fill the role of contacts when customer data platform is enabled. They represent people who view and interact with content through channels, for example, visitors of a website or email recipients.
Each profile connects all data, activities, and other information related to a person that is available throughout the system across entities like [registered members](https://docs.kentico.com/documentation/business-users/members.md) and [commerce customers](https://docs.kentico.com/documentation/business-users/manage-commerce-stores.md#manage-customers). The system can automatically merge profiles that represent the same person based on [identity resolution](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/customer-data-platform/identity-resolution.md) rules. |
| Segment | Segments are dynamic groupings of profiles based on defined conditions, which allow you to accurately target profiles in your marketing and personalization initiatives.
Segments are created and configured in the **Segments** application. See [Segments for profiles](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/customer-data-platform/segments.md). |
## Digital commerce
| Term | Description |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Catalog discount | [Catalog discounts](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/promotions/catalog-discounts.md) are [promotions](#glossary-promotion) that apply discounts to individual products during [price calculation](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/price-calculation.md). The system evaluates all applicable catalog discounts and automatically selects the best discount for each product. Only one catalog discount can apply per product (catalog discounts are not stackable). Catalog discounts can be applied automatically or require a [coupon code](#glossary-couponcode). |
| Checkout process | The [checkout process](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/checkout-process.md) is the workflow that guides customers from their [shopping cart](#glossary-shoppingcart) through to a completed [order](#glossary-order). In Xperience, the checkout process is fully implemented by developers, including the user interface, validation, and payment integration. Xperience provides core building blocks such as shopping cart management services and the [order creation service](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/checkout-process/order-creation.md). |
| Coupon code | [Coupon codes](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/promotions/coupon-codes.md) (also called discount codes) are an optional redemption requirement that can be configured for any [catalog discount](#glossary-catalogdiscount) or [order discount](#glossary-orderdiscount). When a [promotion](#glossary-promotion) requires a coupon code, the discount is only applied if the customer enters the matching code during [checkout](#glossary-checkoutprocess). Coupon codes are generic, multi-use, and case-insensitive — any customer can use them any number of times while the promotion is active. |
| Customer | [Customers](https://docs.kentico.com/documentation/business-users/manage-commerce-stores.md) represent individuals or entities that engage with your business, typically by purchasing products or services. The system tracks customer information, including shipping addresses and order history. Customers can be linked to [member](https://docs.kentico.com/documentation/business-users/members.md) accounts or exist as anonymous (guest) records matched by email. Customers are managed in the _Customers_ application. |
| Order | [Orders](https://docs.kentico.com/documentation/business-users/manage-commerce-stores.md) represent requests made by customers to purchase products or services. The system tracks order information, including product details, quantities, pricing, applied [promotions](#glossary-promotion), and customer data. Orders are managed in the _Orders_ application. |
| Order discount | [Order discounts](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/promotions/order-discounts.md) are [promotions](#glossary-promotion) that apply discounts to the entire order total during [price calculation](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/price-calculation.md). Order discounts are evaluated after [catalog discounts](#glossary-catalogdiscount) and can be combined with product-level promotions. Only one order discount can apply per order. Order discounts can be applied automatically or require a [coupon code](#glossary-couponcode). |
| Order status | [Order statuses](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/configure-order-statuses.md) represent stages in the lifecycle of an [order](#glossary-order) (_New_, _Payment received_, _Shipped_, _Delivered_, etc.). Order statuses are configured in the _Commerce configuration_ application, where you can define the status sequence and enable notifications for status changes. Notifications can be sent to the [customer](#glossary-customer) or to internal staff. |
| Payment method | [Payment methods](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/shipping-and-payment-methods.md) represent the payment options available to customers (e.g., credit card, bank transfer). Payment methods are configured in the _Commerce configuration_ application. Xperience doesn't include a built-in payment gateway — you integrate directly with your chosen payment provider's API. |
| Product catalog | The [product catalog](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/model-product-catalog.md) is a structured collection of products available for sale in your online store. Products are modeled as Xperience [content types](https://docs.kentico.com/documentation/developers-and-admins/development/content-types.md) and can be stored either as [reusable content items](https://docs.kentico.com/documentation/business-users/content-hub.md) in the _Content hub_ (ideal for multi-channel scenarios) or as [pages](https://docs.kentico.com/documentation/business-users/website-content.md) in a [website channel](https://docs.kentico.com/documentation/developers-and-admins/configuration/website-channel-management.md) (suitable when products need their own URLs). You can use [reusable field schemas](https://docs.kentico.com/documentation/developers-and-admins/development/content-types/reusable-field-schemas.md) for common product fields and [taxonomies](https://docs.kentico.com/documentation/developers-and-admins/configuration/taxonomies.md) for categorization. |
| Product variant | [Product variants](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/model-product-catalog.md#product-variants) represent variations of a parent product that differ in specific attributes (e.g., size or color). Variants are modeled as child content items of a parent product, holding only the fields that differ from the parent. In the [content hub](https://docs.kentico.com/documentation/business-users/content-hub.md), variants are linked to parents using a content selector field. In [website channels](https://docs.kentico.com/documentation/developers-and-admins/configuration/website-channel-management.md), variants are placed under the parent product in the content tree. |
| Promotion | [Promotions](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/promotions.md) allow you to offer discounts and special offers to your [customers](#glossary-customer). The system supports two types: [catalog discounts](#glossary-catalogdiscount) (product-level) and [order discounts](#glossary-orderdiscount) (order-level). When multiple promotions compete, the system automatically selects the best discount. Promotions are applied automatically or via [coupon codes](#glossary-couponcode) entered during checkout. Business users create and manage promotions in the _Promotions_ application. |
| Shipping method | [Shipping methods](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/shipping-and-payment-methods.md) represent the delivery options available to customers (e.g., standard shipping, express delivery). Shipping methods are configured in the _Commerce configuration_ application, where you set the method name, description, and price. To display shipping methods on the [storefront](#glossary-storefront), create dedicated [content types](https://docs.kentico.com/documentation/developers-and-admins/development/content-types.md) with customer-facing information. |
| Shopping cart | The [shopping cart](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/checkout-process.md#manage-shopping-cart-data) stores products that a [customer](#glossary-customer) intends to purchase. Shopping carts are persisted in the database. For anonymous visitors, the cart is identified by a browser cookie. For signed-in [members](https://docs.kentico.com/documentation/business-users/members.md), the cart is associated with the member account, ensuring consistent access across devices and sessions. Abandoned carts are automatically deleted after a configurable expiration period. |
| SKU | An SKU (Stock Keeping Unit) is a unique code used to identify and track a specific product or [product variant](#glossary-productvariant) in a store's inventory. In Xperience, an SKU field is typically defined as a [reusable field schema](https://docs.kentico.com/documentation/developers-and-admins/development/content-types/reusable-field-schemas.md) and included in [product content types](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/model-product-catalog.md). |
| Storefront | The storefront is the public-facing interface of your online store where [customers](#glossary-customer) browse and purchase products. In Xperience, the storefront is typically built as a [website channel](https://docs.kentico.com/documentation/developers-and-admins/configuration/website-channel-management.md) application. Developers implement the storefront's product listings, [shopping cart](#glossary-shoppingcart), and [checkout process](#glossary-checkoutprocess) as custom pages or widgets. |
## System customization and API
| Term | Description |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Configuration dialog | The configuration dialog is a modal dialog that allows content editors to configure components. Developers define what input elements (editing components) are used to edit individual properties. Content editors manage these properties (e.g., widget properties) in the element's configuration dialog. |
| Content item query | [Content item query](https://docs.kentico.com/documentation/developers-and-admins/api/content-item-api/content-item-query-api.md) is an API that enables developers to retrieve page and content item data from the database using fluent syntax. |
| Editing component | A specific use case for [UI form components](#glossary-uifc). The term applies to UI form components assigned to provide the editing interface for a property used to configure another administration element. For example, a date-time input form component can be set to edit a widget property in the Page Builder configuration dialog. |
| InfoProvider | [InfoProviders](https://docs.kentico.com/documentation/developers-and-admins/api/database-table-api.md) enable CRUD operations over objects managed by the system. |
| ObjectQuery | The [ObjectQuery API](https://docs.kentico.com/documentation/developers-and-admins/api/objectquery-api.md) provides an abstraction layer over the project's database. It enables developers to manipulate [object types](https://docs.kentico.com/documentation/developers-and-admins/customization/object-types.md) using a fluent API similar to LINQ. The API is directly used by InfoProvider classes. |
| Object type | [Object types](https://docs.kentico.com/documentation/developers-and-admins/customization/object-types.md) store metadata and configuration related to the system's database entities, such as users, contacts, and roles. |
| Object type data class | The [object-relational mapping (ORM) framework](https://docs.kentico.com/documentation/developers-and-admins/api/database-table-api.md) uses data classes to map database entities to objects. |
| Provider | Provider classes expose various management APIs usable when customizing the system. You can find different types of providers, such as info, email, or file system providers. |
| UI form components | All form elements in the Xperience administration are composed using [UI form components](https://docs.kentico.com/documentation/developers-and-admins/customization/extend-the-administration-interface/ui-form-components.md). Each component provides an input interface for one field in the form. UI form components are built using a different underlying technology than [Form Builder form components](#glossary-fbfc) and are not interchangeable. |
| UI page | UI page refers to an individual page in the [administration interface](https://docs.kentico.com/documentation/administration-interface-basics.md). Each page is accessible under a specific URL a provides discrete functionality (object listings, editing interfaces, settings, system information and statistics, etc.). UI pages derive their layout from templates in the [client application](https://docs.kentico.com/documentation/developers-and-admins/customization/extend-the-administration-interface.md) and their functionality from classes that represent them on the back end. To learn more about UI pages and their structure, see [UI pages](https://docs.kentico.com/documentation/developers-and-admins/customization/extend-the-administration-interface/ui-pages.md). |
| UI page command | [UI page commands](https://docs.kentico.com/documentation/developers-and-admins/customization/extend-the-administration-interface/ui-pages/ui-page-commands.md) enable the execution of arbitrary code on the server back end from within UI pages rendered by the client-side application. For example, page commands are used to handle interactive elements (buttons) or navigation. |
| UI page extender | [UI page extenders](https://docs.kentico.com/documentation/developers-and-admins/customization/extend-the-administration-interface/ui-pages/ui-page-extenders.md) allow you to modify the back-end definition of existing UI pages without directly editing their source code. You can use them to add new UI page commands, or change the initial configuration of the page's client properties. |
| Unit test | An [automated test](https://docs.kentico.com/documentation/developers-and-admins/customization/write-automated-tests.md) that runs without external resources (such as a database or network). Uses faked data provided by the CMS.Tests library. |
| Integration test | An [automated test](https://docs.kentico.com/documentation/developers-and-admins/customization/write-automated-tests/create-integration-tests.md) that connects to a real Xperience database via a connection string to verify behavior that depends on database interaction. |
| Isolated integration test | An [automated test](https://docs.kentico.com/documentation/developers-and-admins/customization/write-automated-tests/create-isolated-integration-tests.md) that automatically creates its own database instance before the test run and destroys it afterward. Suitable for tests that write data. |