At present, our partners are not using the CI tool for deploying to development for numerous reasons - mostly related to the performance and functionality of the tool. The current state means that cloud deployments are slow and prone to risks such as loss of production data.

We want to introduce an additional enhancement of the CI tool for continuous deployment purposes. This improvement will reduce the risk of data loss during deployments, by adding the ability to choose to update what is new or what is existing.

What

• Separate options for append (create & update) and create only modes

Enable the possibility to add a custom field to a Node/Document to allow the development of additional features such as support for Sitemap, extra Navigation, custom Metadata, etc., which require storing custom page-related data.

In order to keep the current possibility for Marketers to quickly design Landing pages without worrying about filling in all the widget properties, but at the same time making sure they do not miss such properties before navigating away, Kentico Xperience will visually notify Marketers about such unfilled required properties.

This feature will enable developers to limit Page Selector to only allow selection of certain page types. This will remove the clutter for content editors and will help in avoiding errors. Developer will be able to set Page Selector to select:

• all page types (the current functionality)

• multiple page types (e.g.: Product Page, Product Accessory Page, Product Category Page)

• just one page type (e.g.: Employee Page)

Let's imagine a situation where content editor wants to display 3 most relevant pages in a widget - they will be shown as a thumbnail, title, description and URL. She opens the Page Selector in this widget and sifts through the content tree trying to find the most relevant pages of the right page type. In the end she might select a wrong resource, for example a page type lacking thumbnail or URL causing display errors.

Do you have a different scenario for this feature? Share it with us!

Kentico Xperience 13 offers Translations application for managing localization of content using translation services. This application works well with structured content (the Content tab in Pages) but does not take into account content in Page Builder Widgets like Rich text content.

After this improvement is complete, the content from any Page Builder Widget can be also included in the XLIFF export making it easy to send any page for a translation regardless of how the content was created.

To ensure customers creating new Kentico Xperience 13 projects are using supported versions of .NET and related dependencies we will update the Kentico Installation Manager (KIM) for Kentico Xperience 13 to create new projects using .NET 8 for ASP.NET Core based projects, with updated NuGet package versions.

Add a calendar component so that Marketers can add a date field to their forms with simple usability for site visitors, who are then less likely to abandon the form/page.

Content editors face significant challenges in efficiently assigning categories to a substantial volume of content within a content management system. The process is hindered by subjectivity and ambiguity in category/tag selection, time-consuming manual efforts due to the volume of content, inconsistency in tagging practices, a lack of contextual information, limited tagging options, complex taxonomies, and potential integration issues with existing systems. These difficulties impede the accurate organization and retrieval of content and lead to a substantial investment of time and resources.

Refresh 12 brings to Kentico 13 the possibility of using generative AI as a helper to assign relevant categories to pages. The AI looks at the page's structured content and can recommend appropriate categories based on the meaning of the text.

Refresh 12 offers the following features to achieve this:

• Category scoping: allows you to define which categories can be applied to a particular page type.

• Azure OpenAI integration: integrates the power of Azure OpenAI to enhance the AI capabilities.

• Category auto-selection: enables automatic selection of categories based on the content of a page

websitesAllow our customers to run their website without dependency on jQuery.

Basic support for WebP and SVG files to be able to see a preview of them in Media Library and insert them to content by using our WYSIWYG editors.

When working with widget properties in our Page Builder sometimes it makes sense to hide some fields related to the selection of some dropdown, radio button, or checkbox in order to make the form clean and understandable for the content editor.

Sometimes it is necessary to reload some select box and display another set of items related to the value of another field in the form.

Example

Specific example when it is necessary to reload Order By select box when the value of the Page Type select box is changed due to a different set of items in every Page Type.

As we are receiving feedback about some complications by using our product related to User Experience we would like to react to the most critical and recurring ones.

Areas, where we are going to start, are:

• Pages - Content tab

• Pages - Modal windows

• Media Libraries

When creating new web pages in Page Builder you can offer visitors related content, for example blog articles and similar products. Up to now, if you wanted to add several related pages, you needed a separate widget for each card. Adding multiple cards with related pages to a single widget needed a custom workaround.

Not all widgets are suitable for all places on your webpage. Some, such as header banners, are designed wide, some are narrow like cards. If an editor chooses a wrong widget for a zone, it doesn’t display correctly and looks like a bug. Luckily, editors don’t need to carry all the rules in their heads.

With Widget Zone Restrictions, developers can define which widgets are suitable for each zone. When building pages, you get only the suitable widgets offered. And when you drag-and-drop a widget to a different position, you see which zone it is allowed to sit in.

Imagine creating a landing page split into two columns in a 25:75 ratio. You’ve added widgets with content and then decided that the sidebar will look better on the right rather than the left. You changed the layout of the page, but until now, you had to move the widgets manually.

  With the new Widget Zone Names, developers can allocate a title to every zone. Then, the system remembers which zone each widget belongs to. In case an editor decides to swap the zones, the widgets automatically “follow” them to the new positions.

This gives you freedom to be creative with your page layout, try different options and choose the best one. Focus on the final look rather than manual work.

https://xperience.io/discover/blog/refresh-3-make-your-page-builder-even-more-powerful

Enable content editors to copy & paste widgets when using the Page builder. This way, it is faster to add several widgets with similar properties or move widgets across different pages.

Adding the possibility for a developer to add properties for sections in the form builder. This way, marketers can add headers, descriptions, or even dynamic layouts anywhere within a form.

This feature would allow you to set a custom alias for your cultures (such as "en" instead of "en-US", or "fr" instead of "fr-FR") and have this reflected for your website's URLs while using Automatic routing.

Making sure only the right message gets carried over.

The new combined index for Pages that can search across content fields as well as crawl the HTML will make it way easier to set up the search capabilities for your websites. Both for local and Azure search!

Debugging will allow you to monitor internal activity within the system in order to find and fix problems with performance or specific features. This time also in your ASP.NET Core MVC projects.

Cache tag helper provides better performance of websites under heavy load.

Kentico Xperience is very particular about visitor tracking and their data protection. There are cases however when Kentico Xperience websites tend to be too protective.

An example is logging activities for Newsletter subscription, Form submission, Purchase, ...

In certain scenarios, logging of such an activity could be performed even though cookies are not being stored and the visitor is not being tracked.

If enabled, these activities will be created and the system will therefore be capable of executing marketing automation processes or creating dynamic contact groups.

Please consult your use-case with an independent legal and/or privacy professional.

Kentico Xperience 13 will reintroduce linked pages functionality into MVC to cope with scenarios where a content editor needs to reuse content. The reusable content functionality will introduce solutions for menu building, home page modeling, and populating featured content.

The Automatic (or dynamic) routing is one of the essential features that are missing in Kentico 12. Kentico Xperience 13 will fill this gap with an automatic router module. This module will extend your custom routes with our dynamic behavior. Every page configured to use built-in dynamic routing will be granted with an automatically generated URL which adapts to every change in the content tree without any development effort. The customization model and multilingual support will be included.

Technologies like ASP .NET Core, ASP .NET Core MVC, MVC 5, and .NET Standard are all important parts of Kentico's technology future. In Kentico Xperience 13, we want to provide .NET Standard assemblies as a NuGet package. Development teams can use these assemblies in their .NET Standard and .NET Core applications. They can also use them to create custom .NET Standard libraries or ASP .NET Core and ASP .NET Core MVC applications connected with Kentico.

Technologies such as ASP .NET Core, ASP .NET Core MVC, MVC 5, and .NET Standard are all important parts of Kentico's technology future. In Kentico Xperience 13, we want to provide .NET Standard assemblies as a NuGet package. Development teams can use these assemblies in their .NET Standard and .NET Core applications. They can also use them to create custom .NET Standard libraries or ASP .NET Core and ASP .NET Core MVC applications connected with Kentico.

Technologies like ASP .NET Core, ASP .NET Core MVC, MVC 5, and .NET Standard are all important parts of Kentico's technology future. In Kentico Xperience 13, we want to provide .NET Standard assemblies as a NuGet package. Development teams can use these assemblies in their .NET Standard and .NET Core applications. They can also use them to create custom .NET Standard libraries or ASP .NET Core and ASP .NET Core MVC applications connected with Kentico.