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
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.
Asset elements are placeholders for files. They can be limited to certain number of files or to files of certain size. Find how to work with media assets in Kontent.
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 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.
A content model is a representation of the content's structure (what the content consists of) and the relations between your content. It can represent all content within an organization or a subset of an organization's content that has typically a common purpose.
The structure is defined on multiple levels. It describes each content type, how content types are reused, whether they reuse some elements, and how elements are connected to each other. The relationships provide simple rules that indicate what is to be used where, when, and how many times.
Content reuse is using a single piece of content in multiple content items. Reusing content avoids its duplication so that there is only a single version of the content, wherever it appears. It's a benefit of a well-structured content model as it improves both efficiency and consistency.
Reused content can be both simple and complex. From content assets such as images, you can reuse chunks of texts up to reusing whole content items.
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:
- Overall direction for content:
- Roadmaps for content initiatives
- Business objectives that content supports
- High-level, tangible outcomes that content is expected to accomplish
- 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
- 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 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.
Content type snippet element
Content type snippet elements provide space for your content type snippets, which are collections of elements. You define a content type snippet separately and then you can add it to multiple content types. The same collection of elements will then be added to each content type. Each content type snippet can only be used once in a given content type.
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.
Date & time element
Date & time elements allow you to choose a specific date and time. In the UI, the time in this element is displayed and interpreted as UTCOpens in a new window. Your app can, however, work with the time as if it was in any other timezone.
Elements are parts of content types that define what kind of content can be included. 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 taxonomy and content type snippets.
When working with content items, each element consists of a label and guidelines.
- Labels tell content creators how the elements are titled.
- Guidelines provide instructions throughout the production process. If you define them as a part of a content type, they will be displayed to contributors with each content item they fill in.
A guideline is a helpful instruction for your content creators. When creating a content type, you can put guidelines into a dedicated guidelines element or use guideline field in individual elements. Find more about the benefits of proper guidelines.
The guidelines in Kontent are purely internal. None of the users of your app or website will see them, only the people with access to your project in Kontent.
The homepage is the root content item of Web Spotlight projects. Technically, it's the only content item of the Homepage content type. Both are created automatically when Web Spotlight is activated in your project and cannot be deleted while Web Spotlight is active. You can change it however you desire, though.
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.
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.
Linked items element
Linked items elements help you link content together and create relationships, menus, and more. You can limit content types and the number of items that a contributor can assign. Check out the Subpages supporting element below as well.
Multiple choice element
Multiple choice elements let you to create a list of options (up to 250). You can choose whether the options show as radio buttons or checkboxes. Radio buttons allow selecting a single option only. Checkboxes allow selecting one or more options.
Number elements allow you to fill numeric values. For example, you can insert integers (like 0, 3, or -10), decimal numbers (like 3.14), and even scientific notations (like 2E8).
Pages are web pages within a website project with Web Spotlight. They contain navigation information so that they can be located somewhere in the website's page tree. For example, they specify their subpages or URL slug. The actual content can be stored either in them directly or linked in other content items based on your content model.
When Web Spotlight is activated in your project, the Page content type is created automatically so that you can start creating pages right away. Technically, they are content items so you can use any content type for pages.
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.
Rich text element
Rich text elements are suitable for both short and longer pieces of structured text. Formatting is limited to headings, paragraphs, lists, tables, strong text, text with emphasis and links.
The content in this element can be up to 100,000 characters long. and displays the number of characters it already contains. You can set a custom limit to a specific number of words or characters. Take a look at Rich text element shortcuts if you plan to use them.
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.
Subpages are child items of other pages in Web Spotlight projects. You can create them directly from Web Spotlight or you can use the Subpages element. The element becomes available when Web Spotlight is activated in your project.
Subpages elements specify the child pages of content items based on a given content type. They work similarly as the Linked items elements but their purpose is for establishing page tree navigation. This element is only available with Web Spotlight and can only be used once in a given content type.
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.
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:
- Create website navigation
- Create sitemaps
- Categorize content items or assets – tags, personas, brands, etc.
- Group content that should be released together
- Group content into subprojects
- Filter your content by taxonomy – in Kontent or in your app
Taxonomy elements allow you to add a taxonomy group to a specific content type. To make taxonomy elements work, you first need to create a taxonomy group.
Text elements are ideal for shorter pieces of textual content. For example, text element is a good choice for titles, keywords, basic guidelines, or even code samples.
The text in this element can be up to 100,000 characters long. You can set a custom limit to a specific number of words or characters. The element also displays the number of characters it already contains to help you fit within any such limit.
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.
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.
Web Spotlight is an additional featureOpens in a new window for Kontent focusing on website management. It adds a visible page tree of the website. From the page tree, you can create new pages as well as preview your changes directly in Kontent. This makes the authoring a much smoother experience for website content creators.
You have Web Spotlight activated in your project if there's an Web Spotlight icon in the Kontent app menu.
See all relevant materials for Web Spotlight to learn more.