Since Optimizely (Episerver) published the Deployment API [https://world.optimizely.com/documentation/developer-guides/digital-experience-platform/deploying/episerver-digital-experience-cloud-deployment-api/] . for you DXP deployments, it enabled some new deployment strategies regarding how you could setup your environments. For example, you don’t need any more a internal testing environment, since you can deploy separately
There aren’t many real world websites that doesn’t have any integration requirements to display content from external sources. For example, you probably need to show job openings from a third party system, or fetch news items from multiple different sources, or import media content from external mediabank APIs.
Finally, Optimizely (Episerver) published a preview version of their .NET 5 renewal [https://world.episerver.com/blogs/martin-ottosen/dates/2021/6/-net-5-public-preview/] . This gives us developers wide variaty of new options to deside what kind of our future development environment is going to be. Since there isn’t any dependency
Interfaces are more or less basic stuff in programming and in Episerver development. You probably have seen these guys (IThisAndThat, IEtc..) all over the reference solutions (AlloyDemoKit, Quicksilver, …). In this blogpost, I’ll be taking a concrete approach how to make one of the AlloyDemoKit’s content blocks more compatible