You can learn all about my story and the challenges I face during my professional life as an Episerver Architect and Tech-lead. Feel like home and Welcome
Episerver continuously improves all aspects of our platform. One area that definitely – and unfortunately – lacks attention, for native support, is the authentication part, which out of the box relies on the old ASP.NET Membership framework. Let me be honest, I don’t like ASP.NET Membership. ASP.NET Identity and the OWIN specification, via Katana, is, in my humble opinion, the
Episerver provides editors and administrators with great digital asset management capabilities. It definitely serves the purpose.. especially if they are in possession of all the required assets at the time content and platform is built. Exactly that issue – a typical chicken egg situation – often proves to be problematic during development of CMS experiences. The issue is a twofold one: My
Episerver’s multi-site feature is a really powerful feature when dealing with enterprise solutions. It supports the need to create more than one site running on a single instance (code base). I have, quite recently, used this feature to create dedicated brand experiences and a loyalty program site for a unified Commerce experience. We are often facing the same issue when
Translations.com has provided a Translation Connector to the Episerver community that ties Episerver Commmerce and Episerver CMS – being Pages, Blocks and Catalog items – with their existing GlobalLink Translation suite. Large Episerver solutions tend to require custom Content Types, which also requires translation during the authoring flows, via customized ContentProviders. My experience tells me that business users expects that
Episerver’s new User Notification System is a powerful tool in the search of bridging the gap between a client’s CMS and Commerce platform – facilitating authoring and administering – and their existing collaboration and communication platforms. It is, by default, possible to extend the Episerver platform with customized notification managers for e.g. Slack and Yammer. It’s all really cool.. but it kind off assumes that
Episerver Find is considered a near-realtime search engine. It’s achieved via a event-driven strategy that automatically propagates content-changes to the Search Index whenever Content changes in either Episerver CMS or Episerver Commerce. We’ve experienced that Episerver Find can have a hard time managing large – as in thousands – sets of bulk changes. What we meet is an exception indicating
Intercepting the download process of MediaData in Episerver can be helpful when e.g. tracking of downloads or lead generation features are requested by clients. Previously our Episerver teams has numerous times been requested to implement scenarios that ensures valuable visitor information are collected before a file-download is processed. I won’t cover the actual generation or download tracking, but I will
Our solutions are expected to work in a stateless environment where session affinity (sticky sessions) is disabled. ASP.NET MVC, which is the .NET web foundation of most Episerver projects, are considered stateless with a few exceptions. One of them is their persistence of temporary data across requests. Getting management of temporary data in a distributed setup is fairly simple. There are
There is no doubt in the fact that Episerver is well suited for managing localization of content. Localization of the site copy – being e.g. global elements and labels – and site content – being block/page content – is, natively supported via a combination of language branches and xml-resource files. Many Episerver developers agrees that relying on static XML Resource
Catalog authoring were with Episerver Commerce 7.5 aligned with the authoring experience known from Episerver CMS. It made the life of development and authoring easier and gave our clients a long list of benefits. There are still features that are not supported due to the underlying Commerce engine and the usage of Meta Data Plus. One of them is the