What started out as a small piece of code to extract some metadata fields from your website markup is slowly growing in complexity. Testing, maintaining and extending your document extractor code is getting tougher. There is a very handy tool to change your development experience and speed up your work.
So, we talked about Model Builders to clean up your Sitecore Controllers in the last blog post [https://www.studert.com/cleaning-up-sitecore-controllers/]. Now you might be wondering: "Well, this sounds nice. It looks like some sort of design pattern - I guess design patterns are a good thing. But really,
Ever since the day I read the blog post by Paul Stovell [https://twitter.com/paulstovell] about cleaning up ASP.NET MVC Controllers [http://paulstovell.com/blog/clean-aspnet-mvc-controllers] back in 2012, I knew the day would come where I wanted to clean-up my controllers. By introducing NitroNet for Sitecore [https:
I'm currently involved in a Sitecore project that fully embraces NitroNet for Sitecore [https://github.com/namics/NitroNetSitecore] to integrate its frontend. So let's start this off with a bold statement, because - why not ¯\(ツ) /¯ NitroNet for Sitecore [https://github.com/namics/NitroNetSitecore] is how frontends should be integrated