More reasons I use modx

I really enjoy working with modx and here’s why

No Magic output
- My designers can do anything they want with the design. Go crazy or stay simple- they’re not constrained by the output at all
- Nothing is automatically inserted into your template/website/design
- All fields and variables are controlled by you the designer like sweet puzzle pieces

API
- If there is a CMS function you need like checking userRole, getLoginUserType, it’s there already in document.parser.class.inc.php
- If you need to query or work with the database, the function’s already there in dbapi.mysql.class.inc.php
- I dont have to reinvent the wheel. I can use the CMS api for CMS-type stuff and create my custom functions/snippets (using the easy API) for custom things.

Forms!!! eForm
- Seriously! Have you tried to make a custom email form or form to database with Joomla?
- eForm events make it oh so functional

TVs
- You no longer need to show clients how to edit html tables in their wysiwyg
- If you need a new field like Product Type, Blog Category, just add a TV
- Widgets: Your user doesn’t have to type their values. You can give them a list of options as a dropdown box, checkbox, radio button, and more
- Bindings- Woohoo! This ties into widgets. You can use php code to generate checkboxes of all documents with a certain parent. Or give them a checkbox for each user in a document group. These are powerful

PHx
- Total control of your ’puzzle pieces’ of data
- Sometimes you need to do an if, then on data. PHx makes this more simple than needing to create a snippet.
- You can use custom PHx extenders to manipulate and massage data like phpthumb for images, or adding commas to long numbers

ManagerManager
- Increase how easy the manager is to use (isnt it easy enough already you ask?)
- Remove document fields for certain user groups.
- Move the tabs of the document around
- Add great jquery-ness to the admin via MM widgets

There’s more reasons. I didnt even mention that Ditto can do almost anything (include fly rocketships I think). It’s easy for designers via placeholders. It’s easy for developers via API. And it’s dead-simple easy for your customer.

What’s not to like?

Trying to gather all of that info makes my brainzzzz hurt

Guess thats a good thing

Wow chuck...awesome summary of modx. Wish I could write as well as you. I was reading this blog post today where this guy was complaining about all the CMSes out there...the block structure of most of them and the hacking, hacking, hacking of the code. Long story short, I asked him if he’d heard of modx? Haven’t checked if he answered....

kongondo, please post a link to that blog back here. We’re working hard on new content for the new site and those types of articles make for great source material.

Quote from: rthrash at Sep 25, 2008, 06:01 PM

kongondo, please post a link to that blog back here. We’re working hard on new content for the new site and those types of articles make for great source material.

Sure Ryan, here you go: http://www.designicu.com/blog/cms-or-frameworks/

You know when a designer with some php knowledge says stuff like, he spends a lot of time tweaking CMS to make it display what he wants and that at the end of the day he’s never really happy with the results...my head screams...modx! man modx!!

/k

Quote from: kongondo at Sep 25, 2008, 06:54 PM

You know when a designer with some php knowledge says stuff like, he spends a lot of time tweaking CMS to make it display what he wants and that at the end of the day he’s never really happy with the results...my head screams...modx! man modx!!

I know what you mean. I actually do scream it on twitter about 10 times a day. People are frustrated with most OOTB CMS systems--a couple in particular.

Thanks Chuck for sharing this post. It may end up in a blog post soon.

Hey Jay,

That’s great. I’ve been using modx for a little while now and every day I just find something better about it. That’s the whole point of the post- help you guys with some marketing and just say thanks in a descriptive way.