Slice has been available for a long time and it has proven successful in dozens of applications implemented by Cognifide for our clients. The library is publicly available as an open source project and has been adopted, to a good effect, by other companies. The experience gained and the feedback received allows us to continuously improve its expressive power and functionality and massively accelerate development of AEM-based applications.
However, my engagements with current and potential clients, as well as fellow AEM developers, have shown that there is a deal of confusion about what Slice can do and how it fits into the bigger picture of the AEM ecosystem. With the recent emergence of many new technologies, I can see where the uneasiness comes from.
One question that is raised especially often is that of Slice’s compatibility with Sightly. The new templating language for AEM has been around for over a year and it’s rapidly gaining traction. During my talk at this year’s AEM Hub conference, I’ll show you how Slice and Sightly can be used together to improve code quality and boost the productivity of AEM teams, effectively reducing time to market. I will also tackle a number of common misconceptions about both technologies and address some of the most common concerns.
While snippets of concise code are always a treat for front-line developers, they rarely show the things really important to those of us who don’t write the code themselves. Instead of opening the honey pot of short and sweet snippets of Java and Sightly, I will concentrate on the philosophy behind the Slice & Sightly stack, the impact it makes in terms of code structure and dependency injection, and the ways organizations can benefit from adopting it.
- Is this combination safe to bet on?
- Does it fit into your stack?
- What does it have to offer that other frameworks do not provide?
- How different is it from Sling Models?
- What else does it depend on?
Don’t miss my talk if some of these questions have crossed your mind.