Sulu is een contentmanagementsysteem dat is gebouwd op Symfony, een php-webapplicatieframework. Volgens de eigen omschrijving richt men zich voornamelijk op digitale bureaus om een stabiel en makkelijk aanpasbaar platform te bieden. Zo is het gestoeld op een headless en api-first werkwijze. Voor meer informatie over het hoe en wat verwijzen we naar deze pagina waar de mogelijkheden verder worden uitgediept voor developers, content teams en digital marketers. Het ontwikkelteam van Sulu heeft versie 2.3.0 uitgebracht. De bijbehorende aankondiging ziet er als volgt uit: Sulu Release 2.3.0 After about 6 months of development since the last minor version, we are thrilled to announce that we released Sulu 2.3.0 today! The release introduces a brand new activity log feature that allows users to see what is happening in the application and provides a way for developers to listen for changes and other events that happen in the system. Along with many other improvements, this release also adds new features to the page functionality, enhances the built-in form functionality, and improves consistency throughout the application. Central activity log and event hub Allowing users to see the activities happening inside of a Sulu application is a frequently requested feature in our community. We are happy that Sulu 2.3.0 finally introduces an application-wide activity log to do exactly that. The new version includes a fresh “Activities” view in the “Settings” section of the navigation, that lists all changes that were made to all built-in entities such as pages, snippets and categories. The list includes a timestamp and the associated user for each activity. In addition to the application-wide log, the new minor version also adds an entity-specific activity log for pages and media. This view allows the user to see what happened to a specific entity at what time. We have added this tab to page and media entities for now, but we are open to adding a similar view to other entities in the future. Feel free to reach out to us via GitHub, Slack or our contact form to add your thoughts on this. Behind the scenes, the new activity log feature also brings great possibilities to developers. Each activity that is displayed to the user is created based on an event that was dispatched in the application. These events are dispatched using the Symfony event dispatcher and developers can easily listen and react to specific events using Symfony best practices in a project. Similar functionality can easily be implemented for all activities that are displayed to the user in the activity log. This is especially useful for synchronizing data to other systems and makes the Sulu content management system even more flexible and extensible. New features for pages The block feature of Sulu increases flexibility for the content manager while keeping content structured and consistent. Sulu 2.2.0 introduced a block display settings functionality that allows you to display a block for a specific segment or for specific target groups only. With 2.3.0, we improved this feature and now allow the content manager to configure blocks to be displayed based on the current time or date. To make this feature easy to use, we even added a date selection to our preview that allows the content manager to see the rendered website for the specified date. In addition to the improvements of the block display settings functionality, Sulu 2.3.0 also improves the handling of localized pages. Sulu was built with support for multilingual content from the start and allows users to change and publish content of different localizations independently. Starting with version 2.3.0, it is now possible to remove a specific locale from a page completely. Enhance validation and conditions in forms The form functionality of Sulu is one of the most central and most frequently used features of the content management system. It is not only used for managing pages and snippets, but it is also used for integrating custom entities and external systems into the Sulu administration interface. Sulu 2.3.0 refines this form functionality by solving a common pain point of using conditions inside of blocks, and significantly improves the validation functionality inside of forms. Sulu allows the use of “disabledCondition” and “visibleCondition” attributes to disable or hide properties based on the values of other properties inside of page templates and form configurations. Until now, these conditions could only access data of root properties of a template and could not reference the data of properties of the same block instance. Accessing properties relative to the current block was a frequently requested feature by our community and we are happy that this is finally possible in Sulu 2.3.0 by using the “__parent” variable. Furthermore, the new minor release significantly improves the validation functionality inside of forms. In addition to correctly validating the “mandatory” attribute for all property types, the form view also allows specifying additional validation rules. All selection property types now support parameters for specifying a minimum and maximum number of selected items. Text properties allow to specify a minimum and maximum number of characters and also support validating the given value against a specified pattern. To explain validation rules and display additional information to the content manager, all form properties support the “info_text” element. Other miscellaneous improvements In addition to the new functionality and major improvements described above, Sulu 2.3.0 comes with many small improvements and tweaks in various areas. Here are some noteworthy changes: