In version 2 of SDL’s Digital Experience Accelerator (mostly referred to as DXA), SDL introduced the DXA resolver. Customizing the resolving process can be used to manipulate the list of items to publish that results from a publish action.
“EditFrames in the Experience Editor is a feature that you can use to give users front-end access to fields that are not directly accessible, either because they are not visible or they are of a type that are not directly front-end editable.”
When editing a component using EditFrames or the Editor Button, the component datasource does not refresh. To do this, you have to save the page first, followed by reloading the page with the latest changes, which is cumbersome for content editors.
As a recommended practice, we should not allow duplicate names, in order to achieve this, we have to create a new event in Sitecore. Events in Sitecore are similar to the events in other systems: something triggers an event and there are handlers that are configured to handle the event.
Hotfix rollup 1 (HR1) for Tridion 2013 SP1 was released by SDL in December 2014. The hotfix rollup includes hotfixes for Content Manager, Content Manager Explorer, Experience Manager, Content Delivery, Translation Manager, and Audience Manager and Outbound E-mail.
On February 12th, SDL released DXA 2.0, the shiny new version of the Digital Experience Accelerator. Part of this new version is a new REST service called the model service, which is able to return content quicker, and in a leaner format. Not only that, the model service is also able to resolve links in the content on the fly. This is an important improvement, because link resolving is one of the most expensive operations in DXA as well as DD4T.
A full migration of your application from DD4T to DXA is far from trivial, at least not with the DXA 2.0 release that is currently out. But there is good news: it is very easy to start using the DXA model service in your DD4T .NET application (it is also possible with a Java DD4T application, but we’ll discuss that some other time). Your application is likely to become faster because of it.
There is one important condition: you have to use SDL Web 8.1 or higher, and DD4T 2.0 or higher, in order to upgrade to the model service.