What did you use before MODx?

Our firm has setup sites in Joomla, WordPress, CushyCMS, Intellogy, and Light CMS, as well as dabbling in Drupal. While we plan to keep using some of these for specific areas, e.g., WordPress for a pure blogging site, ModX is now our choice for most development projects. It’s great to have a robust development platform that is aimed at allowing us to craft the varying CMS functionality our clients need. Best of all, our designers love how easily and accurately we can import their work into live sites, no matter how ’creative’ they’ve gotten.

Thanks for everyone on the ModX team for building and supporting a great product!

I’ve been using CMS Made Simple for a long time before finally deciding to cross over to MODx. I’ve never looked back since. CMS Made Simple is quite a nice little system, but there were way too many bugs present and CMSMS turned out to be a bit limited for what I wanted to accomplish.

I don’t have these problems with MODx. I can easily use my own HTML, which is a big plus. Great system, I’ll certainly stick to this one for quite some time.

hi,

i’ve been building home-made cms for nearly 10 years now... and i must say, clients love them because they have the "i’m in my website feeling" and everything is very simple for them to do but... not simple at all for me to develop

in the meantime, i’ve always been playing with some existing cms just in case... and i msut say that, in the end, there are only two i always end in thinking, i’ll use them sooner or later, Automne cms (fabulous editing for the clients build on Zend framework) and MODx.

now it’s time to use one for production and it will be MODx for it’s API (hope i’ll understand it as my main goal is developping custom apps within the classical not really dynamic pages cms seem to be made for, well, that’s my feeling for the moment and for it’s templating which i feel really great.

we’ll see...

have swing

Thanks everyone for your stories.

virtualgadjo, hopefully you will be able to do what you hope.

Martijn van Turnhout, great to hear MODx has made your life easier.

edomingo1, we love to hear that MODx gets adopted as a firm’s CMS of choice. Thanks for sharing.

PurpleEdge2010, MODx is should be able to fill most of your needs. Learning evolution for the basics will not be wasted as the general paradigm is the same but Revolution takes it to another level with a more robust API (and fully documented) as well as many enhancements to the way you can work with it and extend it. We’d love to hear the progress of your evaluation. Thanks for taking the time to discuss it.

Where is the "All of the above" and "Many of the above" options?

I would have selected All of the above and would have to admit I spent too many years reinventing the wheel jumping from application to application, as they were proving to limited.

MODX Rocks.

Prior to MODx, I was using Classic ASP and some MS Access and MS SQL databases.

Now I use PHP, MySQL for MODx still on IIS though.

I use Salesforce.com to handle my Login System.

Then I use PHP, MySQL custom database to handle my .PDF, DOCX, XLSX and other physical documents.

It would be great if you guys could build a physical asset management system and tie it to your security model for CMS pages. Weblinks work great for this of course unless you want to put an Document Abstracts and information about the file to display to the user prior to them downloading the document. e.g. http://www.tsia.com/professional_services/ps_research_reports.html

BUT!!!!!

I really want to thank you guys for building the most flexible CMS system I have ever come across.

MODx blows Joomla and Wordpress out of the water.

Keep up the good work.

Jason Buck
TSIA

It would be great if you guys could build a physical asset management system and tie it to your security model for CMS pages.

I did this some years ago; it’s kind of old and dated now, but it does still work. Metadata, checkin/checkout, download, etc all controlled by the MODx user system.

This thread begins with a poll as to site creation methods prior to trying MODx. Well, I had to pick the "Home-grown (dynamic) site" option because that is correct, strictly speaking. However, my PHP use was really not very dynamic at all, just a few "include()" statements to insert HTML corresponding to MODx Chunks and to help me manage those painfully hand-rolled navigation menus that MODx Evo’s Wayfinder Snippet now computes for every page.

I know that the MODx Development Team are excited about Revolution’s design and versatility. Me too. Makes me glad to have dodged the obvious Joomla! / Wordpress / Drupal CMS rabbit hole in favor of following the CMF route exemplified by MODx.

That is a subtle distinction, CMS versus CMF. Important too, I believe.

But lemme tell ya, folks, the simple stuff is what hooks newbies like me. The nav menu problem was enough all by itself to drive me to the CMS / CMF solution. I can no longer imagine hand-rolling anything beyond a single-page placeholder site. And why would I even do that, when I can benefit from the MODx Manager with zero additional work?

I didn’t experience the infamous MODx "steep learning curve" either. Following the nice Evo tutorials available on the Web, I found that MODx and its Extras worked pretty much the way I would have expected and wanted them to work. This leaves me scratching my head over what it would be like to use a more popular CMS.

I decided on MODx after a rain-soaked, long-weekend Google-fest. I read reviews, press announcements and forum posts. Then I looked at the CMS and Blog systems featured on respectable, well supported hosting services. MODx kept popping up, and in frequency well out of proportion to its minuscule installed base. Not only did it seem safe enough for my modest needs, but MODx also approached the Web publishing problem from the direction of flexible development rather than applying canned design elements to narrow problem domains. The MODx Core and Extras developers seemed quite pleasant and helpful as well.

So I bit. It has worked for me.

Just the good-old php/css/sql, usually with a code management assist from Dreamweaver.

That’s why I like modx... It is the best CMS for coders who don’t like using a CMS. I need the fun that first hooked me on programming. I don’t get any programmer fun with a CMS and I hate templates. I hate even modding them, nevermind creating them. Yet for mysterious reasons, with modx I don’t mind templating at all. Maybe it’s the per-page nature of it. And I don’t feel like the site I’m putting together is a soapbox derby car.

Having said that, I just finished a Joomla site for a client. p

I’ve used joomla (and even mambo in the older days). I’ve scripted my own CMS (Vit.iX) and
after that i scripted my own framework (DreamFrame) in a period of over one and a half
years (for the company i was working for at the time).

DreamFrame was a LOT more powerfull then joomla (since that is just a CMS) but i prefer
MODx over it now since it just has the edge over DreamFrame.

We didn’t knew of xPDO back then which is a darn shame!