Sitecore Pipeline ValueProvider for Mvc
Lumi.Foundation.PipelineValueProvider is a module that helps you speed up Sitecore development for Controller Renderings and allow you to supply Sitecore context type objects to your Controller Actions.
Lumi.Foundation.PipelineValueProvider is a module that helps you speed up Sitecore development for Controller Renderings and allow you to supply Sitecore context type objects to your Controller Actions.
A quick blog on something I discovered recently. If you have a page with a lot of renderings and many placeholders, then the xEditor’s performance can drastically get affected. In my efforts to fix this behavior for one of our clients I found a solution I’d like to share.
I’m blogging about this just in case someone else runs into this problem and for future reference in case I run into it again. If you have more than 2 versions of a page in a language other than the default ‘en’ and you select the ‘Approve with Test’ option, then the wrong version to compare to is selected.
This will hopefully be the first part of many blog posts about the Sitecore Experience Accelerator. Starting with what I think is one of the fundamentals: The Partial and Page Designs concept.
A really small feature, yet very handy, of which I found myself adding over and over again. Time to put it into a nuget package so we can just install and use.
I’ve been thinking this library is deserving a blog post on its own for a while now. I’m talking about the BoC.Persistence.SitecoreGlass library made by my colleague Chris van de Steeg. There is a lot more to talk about than what I will cover, especially since this library is part of a larger BoC collection, but I can assure you it’s worth getting to know.
With atomic design being a popular thing with Sitecore solutions, bringing great flexibility, it also brings some challenges like making simple -add content component- task quite cumbersome. Let Partial Layout Presets help you!
Lately I found myself adding the same templates and renderings over and over again because I wanted to add Bootstrap to my Sitecore solution. But not anymore, now there’s a Nuget package for that!
This issue has been on the outskirts of my radar for a while, Sitecore’s placeholder settings strategy is pretty straight forward and not optimal for multisite environments. While working on a generic presentation framework I felt it was time to address this issue.
Getting every view PageEditor compliant can be a tricky thing. Getting stuck with this bloated view containing if statements, checking the PageMode.IsPageEditor state a lot. In this situation I think it would be better to have a completely different view to render. This solution helps you with just that!
Ever needed to wrap al your components with a container div or something else if a certain condition is met? I know I have and I have made several solutions with different approaches, but this time I think I got it right: RenderingWrappers!
There have been a number of times where setting an expiration date on a renderings html cache would have been the right thing for me to do. I wasn’t able then but I have found a way now.
And I say ultimate because others have fixed this before me, but I think this solution is the most complete.
In case you did not know: DisplayModes are awesome and I think we should consider to use them more. This example will show you how you can create your own displaymode and understand the potential of this feature.
A bit bold title but it seems this "issue" has not been solved properly. Like: I haven't been able to google a solution that feels right. So I figured it was time to take the dive myself and fix this once and for all.
Sitecore 7 and later releases was shipped with the new Insert (internal) link modal window setup with the SPEAK interface. However, editing an existing link did not automatically select the existing link for you, forcing you to reopen the entire tree. Time to fix this annoying little bug.
In my last post I referred to Route Hijacking. This is a term used by Umbraco and enables you to let Umbraco find your custom controllers based on the RenderMvcController rather than returning the regular RenderMvcController. But I don’t need and don’t want the RenderMvcController so this post explains how you can create your own ControllerFactory which Umbraco will use.
One of the really cool features that is introduced with MVC is modelbinding. The DefaultModelBinder already gives you a great start for binding request data to models but wouldn’t it be really cool if we could have an UmbracoModelBinder?
So 2 things that clients ask at least once are:
I will answer both questions and will show the way for one...
The Glass.Mapper framework for Umbraco is premature compared to Sitecore and since this awesome project is opensource I can contribute wherever is needed. First thing I really want: InferType.
So get ready for some stonecoal english at a periodic rate! Starting with a brand spankin new Umbraco 7 installation and already keeping track off the usefull stuff to share.