This blog is running on Orchard. Though, truth be told, I went ahead and put this blog on the server without having any freaking idea how Orchard worked. I figure that I would be able to figure it out without issue. I mean, hell, all I have to do is choose this blog recipe thing and budda-bing-budda-boom I would have a blog; and, to be truthful, that is exactly how it worked out. The issue though lies in anythind additional that you want to do.

     I thought I would just make a new blog theme, easy stuff. However, the convention involved around the core of Orchard is beastly. Honestly, I had read that there are unexplained intricacies added into the core setup of Orchard and I didn't understand it until now. The content parts can be tacked onto content types which can be turned into content items, and they can be displayed by widgets that have shapes, and soon enough you get to a point where you read a sentence in the documentation and realize there were 5 things in that sentence that you have never heard of before.

     In reading reviews about orchard I usually heard that the extra plumbing needed to make a module is daunting. After doing it, let me tell you, it is, in fact, daunting. You need a content record which has a content part that derives from that record, then a handler to wire up the repository, then a driver to display it, and then a migration file to setup the DB for that new part. That is about five separate things to wire up. Now, you just read me type that all out in one sentence and you might say to yourself, "well, that wasn't all that bad," but believe me, that was knowledge gained after HOURS of being generally confused.

     Because I can't be bested, I am going to learn the shit out of this technology. I am going to own it. However, it will take some time and I it hope doesn't take my soul with it.