MojoMotor turned 1 year old this past Memorial Day Weekend! Although it wasn't available to purchase until July 29th of last summer, it was announced at the 2010 EECI conference in San Francisco. I was fortunate enough to be in attendance when Derek Allard proudly demoed Mojo. Now, Mojo isn't for everyone, but I found myself very excited as I knew this product would fit many of the needs of the clients and sites I build.
Over this past year Ellislab has gone through a number of changes such as the release of EE2 as well as the now-infamous post on the Nerdary by Kenny Meyers. That soon was followed with some hoopla that rippled through the CodeIgniter community regarding community participation and development releases.
Later in the fall of 2010, Derek Allard, the primary developer of MojoMotor announced that he would be leaving EllisLab to pursue other interests. Having met Derek at EECI, and having seen his passion for the success of Mojo, I knew immediately that this would affect the progress of MojoMotor, at least for the immediate future.
However, I’ve also been around the EllisLab community for a number of years and I knew that they have a solid commitment to their products, but more so, to their community. On numerous times I’ve seen transparency, genuineness, and commitment for the success of the community at large.
So, take that commitment to excellence in product as well as the commitment to the community, I have high hopes for the future of MojoMotor.
MojoMotor’s undeniable strength is the simplicity that it offers to clients who don’t need a full blown EE installation. I love showing a client how to update some content on their site using Mojo. They are frequently amazed and respond with comments like this:
That’s it? That’s all it takes? Man, that’s easy!
That being said, any seasoned ExpressionEngine developer that has used MojoMotor has undoubtedly run in to some issues. For example, have you every tried creating an image gallery? I still haven’t found a good solution!
Somehow EllisLab needs to harness some of the power that we all take for granted with ExpressionEngine and marry it to the simplicity in MojoMotor.
Where does MojoMotor need to go from here? What would you suggest needs to happen with MojoMotor to make it more useful to you? I have some ideas myself, but I want to hear from you first!
photo credit: lucias_clay
A good article and I am interested to see where they take MM in terms of development next and what, if any, new features they add.
I’m suggesting to a friend that she uses MM for a quick re-design of her site to enable her to manage the content and images far more easily by herself going forward.
Date: 06/05/11
Author: Jesse Schutt
I'm particularly interested in how the body class is added when the mojobar is opened! That was one that was hard to get around in the past.
Feb 09, 2012 3:20am
Donna M.
06/09/11
I’ve just launched my first MojoMotor project., and found it generally an easy job. Had a few blips here and there, but not bad. My biggest issue was not being able to use php code in templates. Finally got around this by using a javascript alternative, but I don’t find that, or the alternative of building an add-on to be able to use php a good long term solution.
I’d like to see a way to support php within MojoMotor. Other than that, from the client’s perspective, this is a great product.