I’m currently building my second site in MODx, migrating a magazine site from Joomla. It’s been an interesting exercise and has given me reason to look closely at MODx’s database structure, etc.
It’s also made me realise how much is likely to change. For example, I need to be able to tag articles, and so I’ve used a modified version of the tagLinks snippet (thank you, Dr Delicious). That works, but obviously I’d rather have native support for tags, which I understand is coming. For now, I’m just presuming that one day I’ll need to write some SQL scripts to move my existing tags into the new tagging system.
But in other ways, it would be nice to make some decisions knowing how MODx will evolve. For example, I’ll need an Ajax library, and I’d rather have just one. But MODx has been using script.aculo.us to provide QuickEdit, is now using Mootools, and the roadmap says that Ext will be used in the 0.9.7 manager. A snippet I looked at yesterday used JQuery. If I’m not careful I could have a bunch of libraries clogging up my pages (as already happens in Joomla!).
The road map refers to other changes coming, like a unified user database and a new MODx tag syntax (and that’s just in 0.9.7). I’m interested to know how people are creating MODx sites now while making sure they will be as compatible as possible with the great stuff that’s coming.
I know some of this stuff has been covered in various wiki and forums posts, but it’s difficult to gather together. Comments are appreciated!
Thanks
Matt
