Smart View and technical innovations

The Base Layout generates the hreflang tags based on the languages available for a page, if the page is available in several languages.

The HtmlTokenizer used in Smart View Content Rendering has been revised internally to work more memory-efficiently.

JavaScript and CSS files are now delivered compressed in the Base Layout.
This compression can be deactivated in developer mode.
Configuration examples can be found in the Maven pom.xml files of the SDK.

In the form and survey editor add-on, JavaScript and CSS files are now delivered compressed.
This compression can be deactivated in developer mode.

The attribute loading="lazy" has been added to the Base Layouts templates for images.

The reports can now access resource bundles so that both their settings and their use are displayed locally.

The robots.txt can be stored in the "robots" data source in the system community.
Both a standard file and a domain-specific file are possible.

After a system start, the first calls of the layouts are often very slow.
To improve this, the Smart View layouts can now be called directly at the start without blocking the layout start.
The feature can be activated via the system setting cms-global-configuration.smartview.sendRequestToRootNodesBlockStart.

The start time of a site is saved in the site settings under site.lastStartTS.

An update from Spring 6.2 to Spring 7 is available.
Compared to the update to Spring 6.2, this update is less extensive, but existing Spring implementations should still be checked.

In the pirobase CMS API, StringBuffer has been replaced by StringBuilder on a large scale to reduce memory consumption.
This may have an impact on existing project implementations.

The quiz templates have been revised.
The main focus was on accessibility, the use of image variants, clearer wording and refactoring CSS and JS.