Dette er CodeArts blog. Vi deler thought-leadership og tekniske tips og tricks - men som regel på engelsk.
Ever needed a way to inherit property values down through the page hierarchy in Optimizely CMS 12? Now there is an easy way to enable that.
WebLoadBreaker is a new, open source, browser based tool to help you do quick and easy load tests.
Generic property lists is a cool editorial feature that has gained a lot of popularity - in spite of still being unsupported (officially). But if you dig a bit deeper you can actually customize the editor experience even more...
Videos and well executed webinars are key tools in achieving a higher engagement and conversion rate from your visitors and customers. TwentyThree is a powerful video hub and webinar service. I was lucky enough to get an account and access to their API and that escalated quickly into a prototype integration into Episerver.
In the EU the past year has added even more rules and regulations to which cookies can be set, which data can be collected and which consents are needed for it. While it may not be tricky to add a basic consent box, adding one that adhere to all the proper legislation and then follow the consents given can be a bit more challenging. In this post I take a deep dive into how Cookie Information's solution together with their Connector for Episerver can make it easier - and faster to accomplish.
Over the years I have been involved in quite a lot(!) of Episerver addons and integration projects. A key to a successful add-on is to get the entire project and environment correctly setup and working from the start. This is my recipe.
When one of the market leaders in digital experience / content management / e-commerce acquires the market leader in Optimization and Experimentation - great things can be expected. But how will it differ from the optimization techniques used by Episerver customers today? Here are my thoughts.
In 3 previous blog posts I compared various azure storage technologies with regards to performance and scalability in typical web usage scenarios. I was actually done with the series, but with all that interesting data, I decided to throw my current favorite search/storage/no-sql technology into the mix to get an idea about how it all compares. So - ElasticSearch enters the competition!
This is the 3rd post in my Azure Storage Performance comparison. So far we've examined the typical scenario of storing/retrieving data that most dynamic websites of today deal with. In this post, we'll take a closer look at Update and Delete - and finally review the financial aspects.
In this second post of my performance series looking at Azure storage we're going to take a good look at Read speeds for the various storage types.
Almost every project has some data you want to persist, then read, search through, update and eventually delete. With Azure there are loads of great possibilities - for example Blob Storage, Table Storage, CosmosDb, SQL Azure. I've decided to do some simple and fairly naive tests to compare these for some typical usage scenarios and see how they perform.
Azure Storage has a new cool feature in preview - Static Website. But what exactly does it do - and how can I connect my Episerver installation to it? I decided to find out.
