Competitive Intelligence for MODx and beyond

Jason, thanks for taking the time to enlighten me here, it will help me have a better outlook on positionning MODx. I also have a better understanding of the road ahead, which is sure important

Also, it will help answering developpers talking ORM, CRUD and all these things I don’t know about... Anyway, lots of content in your post, and a lot of added value for Marketing

So sound like Tattoo is going to require PHP5 and will be integrate with Propel. Is that right?

Keep in mind that most hosting company are still not offering PHP5 at the moment and it might take some time to be widely available to the mass.

You’re exactly right Chanh, which is why we don’t expect it to be widely deployable (for a year or so) and more targetted at the ECM market where custom configurations are a non-issue. It’s the same with RoR.

Quote from: chanh at Feb 14, 2006, 12:40 PM

So sound like Tattoo is going to require PHP5 and will be integrate with Propel. Is that right?

Keep in mind that most hosting company are still not offering PHP5 at the moment and it might take some time to be widely available to the mass.

That is correct, Tattoo is built using Propel and will require PHP 5. However, the concepts being built into Tattoo, could be refactored to work in PHP 4 (and possibly using the older Propel PHP4 run-time framework), should that action be warranted and if MODx does not follow the same conceptual path moving forward. However, I believe at this point that most of the content/script resources developed in MODx will always be easily portable to the Tattoo model, since Tattoo will be more like a Content Management Framework, which will allow users to basically generate a Content Management System tailored to their needs (including the need for MODx compatability) and provide an easy way to manage (featuring completely customizable manager interfaces, built in the same manner as traditional front-end Tattoo Resources--aka MODx documents/pages), replicate (reproduce a vertical-oriented CMS aimed at a specific industry or niche market like blogging, CRM, ERP, BI), and integrate that system (with existing or future web resources, whatever they may be).

I believe the idea would be to market Tattoo at medium to enterprise-level markets (though without excluding smaller markets that might have access to PHP 5 facilities) and keep MODx aimed at small to medium markets and focused on the more common PHP4/MySQL environments.