Posts Tagged ‘episerver’

This is the second in a series of posts that look at some potential ways that the Optimizely and Episerver products can be integrated.  In this post we will be updating the code that was created in the first article to include a Full Stack A/B test to determine if an increase in price would affect […]

Rarely does a company get the chance to do a lot of things well. Specialization is often the path to excellence. But at Perficient, we have a different story to tell – and we’ve been recognized by one of our most important partners for it. A New Episerver Emerges Just this week, Episerver announced a […]

I recently came across a project where there was a slightly different twist for the site’s authentication needs.  For this project the company had three different authentication scenarios that needed to be covered. Log in via a primary Azure AD tenant. This Azure AD instance was set up with application roles and the users were […]

Valdis Iljuconoks previously helped me understand how to effectively implement AllowedTypes restrictions with interfaces, something like  [AllowedTypes(typeof(INestedContent))]– which is a beautiful solution for building a block library. This makes our blocks and their Content Areas only concern themselves with specific interfaces. In our case, we usually have layers such as IPageContent (for stripes, grid structures, […]

Episerver Find is a great and easy way to integrate search into your Episerver powered website.  One often overlooked aspect, however, is keeping your search indexes lean.  By default, Episerver will index all instances of content across your website, whether it’s Pages, Blocks, Media, or Folders- Find doesn’t care and will index all of it.  […]

If you’re building modern web applications, you need to carefully consider the front-end technology stack you use. Webpack, a static module bundler, combined with NPM for package management, is a great starting point. Here’s how you can incorporate these technologies into your Asp.net MVC application built upon Episerver. Alongside Node.js, we need to have node-sass […]

When building highly performant web applications, it’s always important to consider your caching strategy.  There are some generic things you can do to make your overall website faster (such as setting efficient client-side cache policies), but often times a much overlooked performance pitfall involves making too many API calls.  Luckily, Episerver’s Object Caching can help […]

Managing your AllowedTypes (insert options) in Episerver can become overwhelming, depending on the strategy you take. You can read about different options here: https://world.episerver.com/blogs/Henrik-Fransas/Dates/2015/10/the-known-and-unknown-of-include-includeon-exclude-and-excludeon/ https://world.episerver.com/documentation/Items/Developers-Guide/Episerver-CMS/75/Content/Attributes/ but there is a strategy you can take for a very developer-friendly approach. As highlighted on Epi World forum thread (Dylan McCurry and I worked together on the project where […]

Often times when building content models inside of a CMS, it’s important to consider the various types of editors and the permissions they may have within the eco-system.  One technique that I find highly effective is to limit the amount of fields a user may see based on their CMS role.  Removing non-essential fields from […]

While iterating on projects it’s always a good idea to keep your lower environments in sync with the latest content and imagery from your production environment.  In some platforms this is a significant effort, but with Episerver DXP it can be easily automated! Eric Markson from Perficient recently blogged about how to automate the orchestration […]

Lazy loading images is a technique for modern web developers where you instruct the client’s browser to only download images as they are needed.  This leads to tremendous performance improvements, as client devices do not waste bandwidth downloading assets which are not being rendered.  To achieve this, we’ll use some client side mechanisms from css-tricks.com […]

Last week I received a nasty bug report regarding Accessibility and Episerver.  Within Rich Text areas in Episerver, the file name is injected by default for alternate text.  This hurts your accessibility score and is a detrimental impact to visually impaired users.  Coincidentally, others in the community have written about and questioned how to solve […]