Quote from: smashingred at Feb 22, 2008, 03:52 PMDavid, great insight and thoughtfulness. What great company. Gentle, self deprecating and all with the simplest points.
Thanks
Quote from: BobRay at Feb 22, 2008, 10:32 PMJason’s probably not going to like this, but I think that from a marketing standpoint, it’s too late to call MODx anything other than a CMS. (...) I believe that what won the Packt award was MODx the CMS. A whole lot of what’s currently in the Wiki and docs is read by outsiders as referring to MODx the CMS. And, let’s face it, we’re having this discussion on modxcms.com.
Great feeback Bob, I think challenging our own assumptions is good, as you point out it’s easy to get lost in our own perspective. Actually, what you’re saying is the very point I was trying to make to begin with : we’re emphasizing more and more (but we always have been, by the way -> check the current modxcms.com homepage, it reads CMF from day one) the framework aspect of MODx.
It’s feedback from clients on modxcms.fr which had me think we had to avoid confusion by naming the framework.
Quote from: BobRayIf we want to make a public distinction between the application and the framework (and I’m not convinced that it’s a good idea), I really think that they need two different names and that it’s too late to use MODx as the name of the framework. If we try to say that MODx is two (or more) different things, we’ll just confuse people (and ourselves).
My point exactly !
Quote from: BobRaySo, in summary (thanks for reading this much of my rant), I think we need to emphasize that MODx is a single tool (possibly built on the amazingly powerful and robust --your name here -- Framework) that will take you to CMS heaven, the Swiss Army knife of CMSs, the preferred brand -- not of techies -- but of people who want a solid CMS that will make web-site creation and maintenance a dream instead of a nightmare, in other words, the ultimate CMS.
Certainly not a rant, more of a passionate advocacy of your point of view on the matter and as I said challenging what we take to be granted is very productive ! I am sure this will push us into being better at marketing MODx and also allow us to align with each other’s perspective
Saying MODx is built upon a framework doesn’t mean it’s not a single tool. You can certainly use MODx as a CMS, I should now since that’s what I do : I can’t use the framework to extend MODx capabilities since I am no coder. But let’s look at the "developper" target : I assume the content management framework aspect would definitely speak to them (but I am not the one to say, really).
Remember xPDO is already distributed as a standalone product (
http://xpdo.org). Saying MODx 0.9.7 is built on xPDO would definitely make sense IMHO, and I don’t see how it could confuse people. Let’s say a developper wants to build an app upon xPDO, that would probably mean (correct me if I am wrong) that MODx and said app would be way easier to integrate. That would also mean big addons such as Ditto or MaxiGallery could become standalone app built upon it (maybe I am raving here...).