<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Blog posts by Dylan McCurry</title><link href="https://world.optimizely.com/blogs/dylan-mccurry/" /><updated>2020-12-18T14:31:10.0000000Z</updated><id>https://world.optimizely.com/blogs/dylan-mccurry/</id><generator uri="https://world.optimizely.com/blogs/dylan-mccurry/" version="2.0">Optimizely World</generator><entry><title>Restricting available types based on site context in Episerver</title><link href="https://blogs.perficient.com/?p=285276" /><id>https://blogs.perficient.com/?p=285276</id><published>2020-12-18T14:10:22.0000000Z</published><updated>2020-12-18T14:31:10.0000000Z</updated><author><name>dylan.mccurry@perficient.com</name></author><category term="Blog post" /><summary type="html">Valdis Iljuconoks previously helped me understand how to effectively implement AllowedTypes restrictions with interfaces, something like  [AllowedTypes(typeof(INestedContent))]&amp;#8211; 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, [&amp;#8230;]</summary></entry><entry><title>Tune Your Episerver Find Indexes by Only Indexing Necessary IContent</title><link href="https://blogs.perficient.com/?p=284277" /><id>https://blogs.perficient.com/?p=284277</id><published>2020-12-04T14:00:30.0000000Z</published><updated>2020-12-04T14:01:29.0000000Z</updated><author><name>dylan.mccurry@perficient.com</name></author><category term="Blog post" /><summary type="html">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&amp;#8217;s Pages, Blocks, Media, or Folders- Find doesn&amp;#8217;t care and will index all of it.  [&amp;#8230;]</summary></entry><entry><title>Caching Service Layers in Episerver</title><link href="https://blogs.perficient.com/?p=284213" /><id>https://blogs.perficient.com/?p=284213</id><published>2020-11-30T02:00:58.0000000Z</published><updated>2020-11-30T02:01:27.0000000Z</updated><author><name>dylan.mccurry@perficient.com</name></author><category term="Blog post" /><summary type="html">When building highly performant web applications, it&amp;#8217;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&amp;#8217;s Object Caching can help [&amp;#8230;]</summary></entry><entry><title>Restoring production DXP content for local Episerver development</title><link href="https://blogs.perficient.com/?p=283795" /><id>https://blogs.perficient.com/?p=283795</id><published>2020-11-20T00:00:41.0000000Z</published><updated>2020-11-20T00:04:12.0000000Z</updated><author><name>dylan.mccurry@perficient.com</name></author><category term="Blog post" /><summary type="html">While developing new features in Episerver CMS, it can be incredibly useful to have a local copy of the production content.  Here are the steps required for extracting content from Episerver&amp;#8217;s DXP platform and restoring it into your local environment for development. Step 1: Request a database backup from the PaaS portal The first step [&amp;#8230;]</summary></entry><entry><title>The importance of “Branch Templates” within Episerver</title><link href="https://blogs.perficient.com/?p=283667" /><id>https://blogs.perficient.com/?p=283667</id><published>2020-11-13T17:36:56.0000000Z</published><updated>2020-11-13T18:01:16.0000000Z</updated><author><name>dylan.mccurry@perficient.com</name></author><category term="Blog post" /><summary type="html">In modern day CMS systems we rarely create pages that have fixed layouts with zero flexibility.  Often times we give the marketing team the power to define experiences by placing a number of configurable components on the page in the layout that they see fit.  This is empowering, but can also be intimidating if you&amp;#8217;re [&amp;#8230;]</summary></entry><entry><title>Implementing field level editing restrictions in Episerver</title><link href="https://blogs.perficient.com/?p=282947" /><id>https://blogs.perficient.com/?p=282947</id><published>2020-10-30T19:32:17.0000000Z</published><updated>2020-10-30T20:01:13.0000000Z</updated><author><name>dylan.mccurry@perficient.com</name></author><category term="Blog post" /><summary type="html">Often times when building content models inside of a CMS, it&amp;#8217;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 [&amp;#8230;]</summary></entry><entry><title>Keep your environments in sync with Episerver DXP!</title><link href="https://blogs.perficient.com/?p=282591" /><id>https://blogs.perficient.com/?p=282591</id><published>2020-10-24T00:17:58.0000000Z</published><updated>2020-10-24T00:28:00.0000000Z</updated><author><name>dylan.mccurry@perficient.com</name></author><category term="Blog post" /><summary type="html">While iterating on projects it&amp;#8217;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 [&amp;#8230;]</summary></entry><entry><title>Defer offscreen images in Episerver</title><link href="https://blogs.perficient.com/?p=282237" /><id>https://blogs.perficient.com/?p=282237</id><published>2020-10-14T20:01:57.0000000Z</published><updated>2020-10-14T20:30:59.0000000Z</updated><author><name>dylan.mccurry@perficient.com</name></author><category term="Blog post" /><summary type="html">Lazy loading images is a technique for modern web developers where you instruct the client&amp;#8217;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&amp;#8217;ll use some client side mechanisms from css-tricks.com [&amp;#8230;]</summary></entry><entry><title>Episerver and Alternate Text for Images in the TinyMCE Rich Text Editor</title><link href="https://blogs.perficient.com/?p=282158" /><id>https://blogs.perficient.com/?p=282158</id><published>2020-10-12T19:13:55.0000000Z</published><updated>2020-10-14T03:29:16.0000000Z</updated><author><name>dylan.mccurry@perficient.com</name></author><category term="Blog post" /><summary type="html">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 [&amp;#8230;]</summary></entry><entry><title>Responsive Image Cropping for Episerver is Here!</title><link href="https://epijocks.com/?p=203" /><id>https://epijocks.com/?p=203</id><published>2020-03-05T23:02:00.0000000Z</published><updated>2020-10-14T03:29:18.0000000Z</updated><author><name>dylan.mccurry@perficient.com</name></author><category term="Blog post" /><summary type="html">SCORE for Episerver &amp;#8211; New Image Crop Tool Responsive Web Design (RWD) offers a cost-effective, high quality and easily managed delivery of content to a variety of devices. Many teams build sites in RWD by using custom or popular responsive frameworks like Twitter Bootstrap or Foundation Zurb. But how can we combine the responsive design [&amp;#8230;]</summary></entry></feed>