Skip navigation

Terminology

Use this glossary to find out more about what terms you'll see inside the Kentico Kontent app and documentation, and what they all mean. If you're interested in terms relating generally to content strategy and content operations, check out the Kentico content strategy glossaryOpens in a new window.

Table of contents

    Asset

    Assets are files included in your project. You can include any type of file you wish, with files such as images generating automatic previews inside Kentico Kontent. You can include assets within content items to display them outside of Kentico Kontent. Assets on their own do not count as items against your plan's limitsOpens in a new window – there are no limits on how many assets you can have in your projects as long as the storage doesn't exceed the Fair Use PolicyOpens in a new window.

    Component

    A component is a single-use piece of content added to a Rich text element. It allows you to practice component-based design when writing your content, for example, adding tweets or code examples to your articles. Similar to content items, the structure of a component is defined by its content type. Unlike content items, components are an integral part of their Rich text element. They don't have a separate workflow status and don't appear in your content inventory. See Structuring editorial articles with components for more details.

    Content item

    Content items are specific pieces of content based on a specific content type. The assigned content type defines what content is allowed in the given content item. If you're creating a series of articles, each one will be based on the Article content type, meaning each will have the same structure. But the content of each item can be as different as you wish. Content items can include assets, but assets do not count as items against your plan's limitsOpens in a new window.

    Each content item can have as many language variants as you have languages in your project. The item will have the same name for each language variant and will only count as 1 item against your plan's limitsOpens in a new window.

    Content strategy

    Content strategy provides a decision-making direction for all activities that are related to the publication of digital content. It ensures that the business objectives for content are aligned with audience needs. This way, your content will be effective at achieving expected outcomes. It focuses on three core areas:

    1. Overall direction for content:
      • Roadmaps for content initiatives
      • Business objectives that content supports
      • High-level, tangible outcomes that content is expected to accomplish
    2. The development of efficient and effective operational capabilities:
      • Allocation of staff resources and training
      • Development and refinement of processes and practices
      • Enhancement of technical capabilities and automation
    3. Guiding principles for how content is created:
      • Process and standards that are used when creating content
      • Ways of team collaboration
      • Practices ensuring that customer needs are addressed with content, such as research and testing 

    Content type

    Content types are like templates for your content. They define the structure for each piece of content so you know exactly what to include where. Each content type is made up of various elements that can defined to fit what you need in each template. So if you're defining articles that will appear both on a website and in a mobile app, you create an Article content type with separate elements for long and short texts. For each article, you then fill in the required content in a content item based on the Article content type.

    Content type snippet

    Content type snippets are collections of elements that can be included in multiple content types. Maybe you have some elements that you'd like to use in multiple templates, such as including metadata for SEO. You can create a single content type snippet to hold the metadata elements and include it in as many content types as you wish. Read more about using content type snippets.

    Custom element

    Custom elements are user-implemented elements that you define within content types. These elements let you add your own content editing features to Kentico Kontent projects and integrate Kentico Kontent with third party systems, such as Shopify and others. Read more about integrating with custom elements.

    Element

    Elements are parts of content types that define what kind of content can be included. You can set restrictions for each element in a content type. There are two categories of elements:

    • Content elements hold your content to be displayed, such as text and assets.
    • Supporting elements hold items that are not directly content for display, such as guidelines and content type snippets.

    See a list of all elements available.

    Language variant

    If your project has multiple languages set up, each content item can include variants for each language. The item has a single name for all variants and only the content in its content elements will change. So if you have an article called "On Roasts" translated into Spanish, it will appear as "On Roasts" in your Spanish content list in Kentico Kontent, even if you have localized its Title element to "En Asados". 

    If a content item has variants created for multiple languages, you can only delete the variant for one given language at a time and the item will return to a "Not translated" status. So if you have translated "On Roasts" from English into Spanish and then delete it from Spanish, the content item will still appear in both languages. Read more about localization in Kentico Kontent.

    Linked item

    You can link different content items together using linked items elements or by adding them to rich text elements. This lets you define relationships between your content. So if you have authors writing a variety of articles, you can create content items for the bio of each author and link to the Author item from each Article item. Read more and watch a video about linking content together.

    Project

    Your projects are the primary way to organize your content. You can use a single project to store all related content that you are trying to deliver across various channels (a website, a mobile app, an IoT device). The Project managers in a given project can set such details as the workflow and languages for that project.

    Role

    Roles are specific sets of capabilities for users in your projects. You can use roles to define permissions for your users to limit what they can do in your project. Roles are useful when defining a workflow and determining who can publish and unpublish content. Read more about using roles to set up a common production flow.

    Subscription

    Your subscription is the highest level of access to Kentico Kontent. Each user and each project must belong to a subscription. Each subscription must be on a planOpens in a new window, which defines the features of the subscription. Each subscription is run by subscription admins who can manage the subscription as well as all projects within the subscription.

    Taxonomy

    Taxonomies are a way to organize your content items and are helpful in many scenarios. You create hierarchical groups of taxonomy terms to label related content. For example:

    URL slug

    URL slugs allow you to define SEO-friendly text to general URLs for your content. Its value is generated automatically from a Text element. So you might have URL slugs set to be generated automatically from titles. If a given article has a title that doesn't fit well with search results, you can change the URL slug within the given content item. Read more about using URL slugs.

    User

    Users are specific people who have been invited to your project. This means people who will work with the content, not people who view the final product. Users who are not marked as inactive will count towards your plan's limitsOpens in a new window for each month that they are active. You can define permissions for users by assigning them a specific role.