In this blog you’ll find various posts about architecture, software development and tools. I use this mainly to document my learning journey to new topics and share them with my insights. Focus is on Microsoft Azure, .NET development and related products for example Optimizely (formerly Episerver).
Since Optimizely (Episerver) published the Deployment API. for you DXP deployments, it enabled some new deployment strategies regarding how you could setup your environments.
Wouldn’t it be nice to have the ability to check your features on your mobile phone or any external device, while you are developing an application.
There aren’t many real world websites that doesn’t have any integration requirements to display content from external sources.
Finally, Optimizely (Episerver) published a preview version of their .NET 5 renewal.
We had a nasty little bug in one of our development stage Episerver projects.
Interfaces are more or less basic stuff in programming and in Episerver development.
I have had the privilege to participate in couple of Episerver’s trainings. Both for the CMS and for the Commerce.
In the previous post, I wrote about profiling your Episerver site and how important it is to spot bugs and performance issues early on.
We all know that bug happens. They are inevitable during development, and basically in every step-in software lifecycle.
Ever had a problem where you would like to open or get the full public address of a page from the editor view in Episerver? Or is it a problem at all?