For this post, I’ve tried to specifically focus on development practices. My rankings are my opinion based on a combination of the item’s importance and how frequently it is (or isn’t) done. So without further ado:
Last week I blogged about the power of Sitecore’s HTML Cache. I have found it so powerful that I become frustrated when I come across a component that cannot be cached. In this post, I’d like to introduce a couple of minor enhancements to extend its functionality.
Sitecore utilizes a number of layers of caching to help improve website performance. For the most part, these cache layers have been abstracted away from the developer. However, the most powerful caching layer is almost certainly the most underused layer. And arguably one of the most underused features in the entire platform.
Coveo recently released it’s new Coveo for Sitecore connector and updated Search UI controls. I shared some of my initial impressions after working with the Beta here: http://blog.velir.com/index.php/2013/12/12/coveo-and-sitecore-7-whats-new-and-improved/. I’ve been really excited to dig deeper into this product and have just begun my first full implementation.
After working on a project that had a very large content migration that saw us publishing and republishing large numbers of items, I began to greatly desire some sort of indicator to see the progress of my publishes. So, I decided I wanted to add a progress bar to the standard Sitecore Publish dialog box.
On nearly every Sitecore site I’ve built, we’ve had a need to display 2 separate sections of the content tree in a single treelist field. The most common use-case being, having a folder to hold components local to the current item, and a shared folder for all items to use. Until now, I had never taken the time to take that code and make it generally applicable to any Sitecore site, opting to port the code from one site to another. So without further ado, the Multi-Root Treelist: