Changes in version 1.1
See all changes made in SDL Digital Experience Accelerator 1.4.
- Context Engine support
The previous version of SDL DXA already supported Context Engine, class ContextEngine, ContextClaims, and subclasses, however it was implemented in the Sdl.Web.Tridion assembly. - Support for multiple sites in one Web application
Starting from version 1.1, in SDL Digital Experience Accelerator 1.1 if you host many low-traffic Web sites that use the same application code (and views), but have their own HTML design and content, you can make your Web and application server use less resources by hosting all such sites in a single Web application. - Improved handling of Media Items
DXA 1.1 introduces improvements in handling Media Items. - Model Page Includes as Page Regions (.NET)
To simplify the page model structure and improve the clarity of the View code, starting from version 1.1, SDL Digital Experience Accelerator will treat Page Includes as Page Regions. - Model Page Includes as Regions (Java)
To simplify the page model structure and improve the clarity of the View code, starting from version 1.2, SDL Digital Experience Accelerator 1.2 treats Page Includes as Page Regions. - New Razor view syntax (.NET)
To improve the View code usability, SDL Digital Experience Accelerator introduced the user-friendly HtmlHelper extension method. - View syntax for Java
To improve the View code usability, SDL Digital Experience Accelerator introduced the user-friendly HtmlHelper extension method. - More refined styling options for views
By modifying your Page Template metadata or Component Template metadata, you can now configure one or more CSS classes to apply to the root HTML element of a Page view or Entity view. - Removed Node.js dependency
The Content Manager server (or specifically, the server that contains the Publisher) no longer requires Node.js. (It is now embedded as a part of the HTML Design configuration through its build files.) - Experience Manager is automatically enabled based on Publication Target settings
DXA Publish Settings Page automatically enables Experience Manager on the published site if the Publication Target being published to has Session Preview configured. - Faster application startup (.NET)
Several improvements improve the speed at which the application starts, but this does result in some API changes. - Faster application startup (Java)
Several improvements improve the speed at which the application starts, but this does result in some API changes. - Ability to load Dynamic Component Presentations separately as Entity Models
To load Dynamic Component Presentations as Entity Models, use theIContentProvider.GetEntityModelmethod. - Ability to create Region metadata
By specifying the regions field in DXA Page Template metadata, you can specify Region metadata. - Custom Region Models, Page Models and Entity Models
You can now create custom Models that are a subclass of the generic Models. You can also give those custom Models different Experience Manager markup than the generic ones. - New location of Core Controllers
All Core Controllers, except AdminController, are now located in the Sdl.Web.Mvc assembly.