Search engine optimization is a critical part of the success of a site as this is the first step in attracting new users or customers. Then, once they are on the site you need to ensure they are being delivered with the content they expected. In Liferay DXP 7.3., there is now support to Open Graph. Open Graph provides a preview of how a page or piece of content will be presented on social media or google search results. This allows marketers to define tailored messaging for social media while previewing social media and search engine page representation.
Unfortunately, the work of SEO is not done when a user lands on a page. If they are being presented a 404 error, they will immediately exit creating a negative user experience and create a negative impact on a site’s SEO. There is now functionality to easily create redirection to avoid 404 errors. Liferay now includes lists of URLs that users have attempted to access and received a 404 error, allowing you to create redirects for those attempted pages as well. Finally, you now have the ability to view a list of friendly URLs that are being used and are able to delete them if no longer needed or restore them if needed again.
In the last few releases, there has been heavy investment made to provide the functionality to make it more intuitive for content and page authors to build pages and build content. In DXP 7.3., there have been some substantial improvements to the UI as well.
This release gives designers even greater flexibility by creating newly composed fragments and responsive layouts for any device. Those containers and grid fragments can be saved to allow new fragments to be created from any combination of fragments and widgets with no need for development. Grid fragments allow great control over the layout. Ex: split one row into rows and columns as needed. Grid fragments also allow support for different layouts for different devices.
DXP 7.3. has enhanced its ability to publish lists of content. Previously, you would use one of the most commonly used widgets, the Asset Publisher. In 7.3., Collections allow for the configuration of the Asset Publisher without the display settings. Collections allow lists of content to be manually or dynamically selected and presented to users. Once these Collections are created, they can be used in an Asset Publisher, the new Collection Display fragment, and through REST APIs for headless use cases. Collections can be personalized for any user segment. Collection Pages can be very quickly created to allow the display of a collection with no effort.
Collection Display fragments provide page authors with the capabilities to display dynamic content and easily display lists. Collection Display fragments also allow the display of Collections using one or more fragments. This functionality builds on the ability to map structured content fields to in-line editable zones which enables the reuse of fragments for multiple content structures.
The next major feature is a function called Asset Libraries. These enable a couple of key use cases. The first is if you are building a headless application, up till now you needed to access the content in the context of a site; which if you are building a headless application, the site context didn’t make sense. The second, is when you want to build dedicated libraries of content, to support a campaign for example, and you want that content to be accessible across multiple sites, the Asset Libraries is a new way to achieve that.
There is also new functionality around the publication. If you have used Liferay for any number of years, you would be familiar with the functionality of Staging. Content Publication is a new approach centered around content authors, marketers, and designers (rather than a centralized/IT function); giving them full control of the preview and publication of their content. Users create a Publication and while working in it, all changes are automatically added. Publications can be reviewed, published, and if needed, rolled back. If two users make changes to the same asset/content, Publications has conflict detection and provides a choice option to resolve those types of conflicts. Multiple users can work on the same Publication simultaneously. Publications work on the global level where Staging only works at a site level.