Quote from: beryl at Mar 11, 2008, 09:53 AM
I find it odd that a CMS that "created" the slogan "AJax CMS" has decided to go for "php framework cms"
Anyhow, thank you the the detailed answeres, now i know what direction to go.
There is the catch in marketing a tool that people are passionate about. A successful project becomes what the users experience no matter what marketing is used to promote, present or lure. Ultimately the marketing needs to correctly present the brand that most effectively represents the meaning of MODx and that has to be inline with user perception or it will confuse or frustrate. Personally I would like to see the whole focus on AJAX and gadgetry disappear and shift focus back onto flexibility, ease of use and extensibility with freedom for developers instead.
I don’t think you will see MODx abandon a packaged release but I think better than that you will start seeing builds and addons for one flavour or another of AJAX or JSON or the as I call the library of the month.
I don’t foresee MODx sidestepping into the realm of PHP Rapid Application Framework although I plan on using it somewhat as such on a personal project.
I am speaking personally and not for the MODx team when I say that I have grown to appreciate Jason’s POV on shipping MODx as a clean/prepped canvas, while at the same time I know that solution packages are essential to the migration of new users to MODx--I was one. I barely understood how to read an API until recently and that is all thanks to the snippets and plugins that come with MODx. I have taken my PHP "skills" to new levels and do so on every project.
The point is that MODx is whatever you make it into. I can’t wait until I can devises custom builds for client deployments and I don’t need to weed out the junk at every install.