<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><language>en</language><title>Blog posts by Dylan McCurry</title> <link>https://world.optimizely.com/blogs/dylan-mccurry/</link><description></description><ttl>60</ttl><generator>Optimizely World</generator><item> <title>Restricting available types based on site context in Episerver</title>            <link>https://blogs.perficient.com/?p=285276</link>            <description>Valdis Iljuconoks previously helped me understand how to effectively implement AllowedTypes restrictions with interfaces, something like&#160; [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;]</description>            <guid>https://blogs.perficient.com/?p=285276</guid>            <pubDate>Fri, 18 Dec 2020 14:10:22 GMT</pubDate>           <category>Blog post</category></item><item> <title>Tune Your Episerver Find Indexes by Only Indexing Necessary IContent</title>            <link>https://blogs.perficient.com/?p=284277</link>            <description>Episerver Find is a great and easy way to integrate search into your Episerver powered website.&#160; One often overlooked aspect, however, is keeping your search indexes lean.&#160; 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.&#160; [&amp;#8230;]</description>            <guid>https://blogs.perficient.com/?p=284277</guid>            <pubDate>Fri, 04 Dec 2020 14:00:30 GMT</pubDate>           <category>Blog post</category></item><item> <title>Caching Service Layers in Episerver</title>            <link>https://blogs.perficient.com/?p=284213</link>            <description>When building highly performant web applications, it&amp;#8217;s always important to consider your caching strategy.&#160; 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.&#160; Luckily, Episerver&amp;#8217;s Object Caching can help [&amp;#8230;]</description>            <guid>https://blogs.perficient.com/?p=284213</guid>            <pubDate>Mon, 30 Nov 2020 02:00:58 GMT</pubDate>           <category>Blog post</category></item><item> <title>Restoring production DXP content for local Episerver development</title>            <link>https://blogs.perficient.com/?p=283795</link>            <description>While developing new features in Episerver CMS, it can be incredibly useful to have a local copy of the production content.&#160; 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;]</description>            <guid>https://blogs.perficient.com/?p=283795</guid>            <pubDate>Fri, 20 Nov 2020 00:00:41 GMT</pubDate>           <category>Blog post</category></item><item> <title>The importance of “Branch Templates” within Episerver</title>            <link>https://blogs.perficient.com/?p=283667</link>            <description>In modern day CMS systems we rarely create pages that have fixed layouts with zero flexibility.&#160; 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.&#160; This is empowering, but can also be intimidating if you&amp;#8217;re [&amp;#8230;]</description>            <guid>https://blogs.perficient.com/?p=283667</guid>            <pubDate>Fri, 13 Nov 2020 17:36:56 GMT</pubDate>           <category>Blog post</category></item><item> <title>Implementing field level editing restrictions in Episerver</title>            <link>https://blogs.perficient.com/?p=282947</link>            <description>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.&#160; One technique that I find highly effective is to limit the amount of fields a user may see based on their CMS role.&#160; Removing non-essential fields from [&amp;#8230;]</description>            <guid>https://blogs.perficient.com/?p=282947</guid>            <pubDate>Fri, 30 Oct 2020 19:32:17 GMT</pubDate>           <category>Blog post</category></item><item> <title>Keep your environments in sync with Episerver DXP!</title>            <link>https://blogs.perficient.com/?p=282591</link>            <description>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.&#160; 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;]</description>            <guid>https://blogs.perficient.com/?p=282591</guid>            <pubDate>Sat, 24 Oct 2020 00:17:58 GMT</pubDate>           <category>Blog post</category></item><item> <title>Defer offscreen images in Episerver</title>            <link>https://blogs.perficient.com/?p=282237</link>            <description>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.&#160; This leads to tremendous performance improvements, as client devices do not waste bandwidth downloading assets which are not being rendered.&#160; To achieve this, we&amp;#8217;ll use some client side mechanisms from css-tricks.com [&amp;#8230;]</description>            <guid>https://blogs.perficient.com/?p=282237</guid>            <pubDate>Wed, 14 Oct 2020 20:01:57 GMT</pubDate>           <category>Blog post</category></item><item> <title>Episerver and Alternate Text for Images in the TinyMCE Rich Text Editor</title>            <link>https://blogs.perficient.com/?p=282158</link>            <description>Last week I received a nasty bug report regarding Accessibility and Episerver.&#160; Within Rich Text areas in Episerver, the file name is injected by default for alternate text.&#160; This hurts your accessibility score and is a detrimental impact to visually impaired users.&#160; Coincidentally, others in the community have written about and questioned how to solve [&amp;#8230;]</description>            <guid>https://blogs.perficient.com/?p=282158</guid>            <pubDate>Mon, 12 Oct 2020 19:13:55 GMT</pubDate>           <category>Blog post</category></item><item> <title>Responsive Image Cropping for Episerver is Here!</title>            <link>https://epijocks.com/?p=203</link>            <description>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;]</description>            <guid>https://epijocks.com/?p=203</guid>            <pubDate>Thu, 05 Mar 2020 23:02:00 GMT</pubDate>           <category>Blog post</category></item></channel>
</rss>