Using MODx
December 30th, 2006Choosing the name was hard, choosing a software package to use was nearly impossible. I decided that I wanted to run a full fledge CMS/Portal. I didn’t know what I wanted to put on the page, but I wanted to be able to expand it easily. Perhaps that is why I like open source software, I know there are no artificial limitation in what I can do. I searched and installed random packages on my poor little Linux box in my house. Finally I found OpenCMS.org. They have tons of open sources packages running on their server. You can log in and play with all the different software packages they have, as well as read reviews by other users. It is one of the best resources for deciding what to use.
I spent a long time setting up different packages and playing with them, but couldn’t find anything I liked. Everything was cluttered and too ‘user friendly.’ I didn’t want to click and point to make things happen, I wanted to get my hands dirty in code. Everything claimed to be so customizable and that may be true for someone who just wants to point and click, but I found most interfaces restricting.
Then I found MODx. I installed it and all it had was a welcome page, clean and simple. Anything I wanted to do I would have to add and integrate myself, exactly what I wanted.
There was one problem…I couldn’t log in. I could tell it was set up properly, but there was some error with my password. I had a suspicion of what the problem was - my password had the php variable symbol ($) in it. I almost uninstalled it right there because I didn’t want to use a product which such a clumsy bug in it, but up until this point I hadn’t found anything half as promising. It also gave me an excuse to go through the source code. I took 2 minutes looking through the code, found the problem and fixed it. At this point I was in love. There ended up being something about going into the code and fixing a bug myself that gave me much more satisfaction than using a bug free program.
MODx’s logo is ‘take control’ and it seems completely true. They built a nice interface that allows you to edit the code and write pages and basically do whatever you want in their framework. Its beautiful, except it doesn’t work well in Opera, my browser of choice. Not a huge deal. A lot of things don’t work in Opera, so its rare that I browse the web without opening both Opera and Firefox. I would be logged into my MODx site editing items with Firefox and viewing the changes with Opera.
I started going through the source code and reading everything I could. I thought I was done with my software search, so I took a break to learn CSS and plan a design. When I got back to using MODx I was ready with a design and began implementing it, but I couldn’t make it ‘perfect.’
Barry Schwartz author of “The Paradox of Choice,” talks about this problem. When we have so many choices we aren’t satisfied with anything but perfection. I suppose it is even harder as a programmer working with open source software, because I know if I work hard enough at it I can get it ‘perfect.’ There aren’t any limitation except my own time and skill. It became clear that using Modx to get my site perfect would take more time than I was willing to use.
The main problem came down to documentation and examples. They have documentation, tutorials, forums, a wiki, and walkthrough sites setup by users. Its just all over the place and the best documentation is in the forums, the worse possible place for it. Learning how to use it is easy, setting up a standard blog is simple, doing anything complex and finding out how others have used MODx is near impossible. Ajaxian wrote a short review of it and John Vilsack made the comment that, “MODx is the Othello of CMSes: It can take a minute to learn, but a lifetime to master!” I didn’t want to spend my lifetime mastering it. I had spent months looking for a content management system, looking for a web host, learning CSS, and now I was spending forever trying to make my site exactly how I wanted it.
The final straw was that I had a hard time finding sites that used MODx the way I wanted to use it. After searching through the forums and other documentation I could usually find things that I thought would work, but to test them I had to code them up and implement them myself only to find out it didn’t do what I wanted it to do. This just got too time consuming.
Finally, I decided to stop and took a break from working on the site all together. After a break I decided to go with Wordpress and got this blog up and running so I could began writing.
I still hope to use MODx, but I’ll wait until they get a 1.0 release out and have a more central place for their documentation. I’ll probably also wait until I have something I want to do with the site that requires more than a simple blog framework.
As a side note Albuqueque, NM has just been dumped with snow. Nothing like Dever, but more than I have ever seen in the 15 years I have lived here. I setup a page with pictures if anyone is interested.