Sitecore
As your code base grows, you might observe certain patterns to emerge and you start repeating very similar pieces of code over and over. This is usually a good indicator that a refactoring might be a good idea.
Sitecore
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,
Sitecore
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:
Sitecore
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