I’ve decided…I’ll be wading into some PyroCMS development and other PyroCMS things. This is kind of a follow up on my previous post where I talked a little bit about PyroCMS, WordPress and ExpressionEngine. In the end, for me, it came down to Expression Engine and PyroCMS. After Phil kindly left his thoughts on PyroCMS I did some more thinking and research. I’m not sure if this is the direction that my place of employment might go, but I’ll be an advocate of going this direction.
So why the change? It really came down to this. I was once again reading a WordPress plugin tutorial and trying my hardest to write a plugin for an upcoming site we have at work. It was a better tutorial than what I found in the past and I had high hopes of knocking it out of the park. But it just wasn’t making any sense. I felt as if I needed to know everything about modules and widgets before I would have been able to get something up and running (never mind the parse order…maybe I didn’t need to know that!). I’m up for a challenge and all of that, but this made no sense to me. So I dropped that, picked up the PyroCMS manual and began my module development. In less than 2 hours I had more than what I had on WordPress. So that’s why I will be going in the direction of PyroCMS with my development.
It doesn’t mean this site/blog will be switching to Pyro anytime soon. Pyro is a web development platform and WordPress is a blog platform. Although WordPress tries to act like a web development platform, and there are many who make a great deal more money than I do, doing that, it’s a pain. Pyro isn’t a blog platform and from the little I’ve used it as a blog, it needs some help (this site was originally on Pyro). Maybe I’ll help with that.
I’ve got a lot of learning to do with PyroCMS, but in the end I think it will be for the better. Hopefully I’ll be able to contribute in some fashion. I doubt that it will be to the core product. I suspect my biggest impact would be elsewhere (documentation or tutorials perhaps).