Development for Ignition 3 has started!
We are working on the next iteration of Ignition, now to be called Ignition.Framework. There are going to be a number of fundamental changes to the core architecture, including even more in the way of abstractions and dependency management, more flexibility than was already there, and a reduction in the required dependencies to the toolset.
Some changes to note:
- Instead of using the concept of Foundation.Business Feature>Presentation Feature>Project, we are moving things that are part of the framework to an even lower core Framework layer. Then, supporting class libraries can exist at Foundation, and the clear line of Stable Dependencies is maintained. It will also be marked by more strict dependency management between these layers and clear abstractions between platforms. This will drive the ability for Ignition to be able to be used for both Sitecore, Episerver, Sitefinity, SharePoint, or any other dev platform while maintaining consistent patterns and libraries.
- We are stepping away from native support for Glass Mapper, thus removing a dependency on Glass and Castle. Instead, we are going to be providing a simple wrapper ORM out of the box and allowing for providers to be installed/used to wire op models. This means that any of the available ORMs could potentially be used including Glass, Fortis, Synthesis, etc.
- Ignition will include default support for things like Sxa, Logging, Caching, Search, App Insights, etc. out of the box. We also plan to have a general set of components that can be used to drive content components for clients.
- We are also looking at expanding our clientside support, integrating common UI toolsets like Typescript, Knockout, Angular, React, Webkit, and many more.
If you are interested in contributing or have questions, you can reach the ignition team at: 596a5747.Perficient.email@example.com. Additionally, the new repository is located here: https://github.com/sitecoreignition/Ignition.Framework.