After kicking the can around with SilverStripe and MODx CMS, I’ve decided that for my needs WordPress will do just fine.
I’ve settled for having several unique sites instead of one “all inclusive” one. The bang I was after on my portfolio was not compatible with a full site, so I just turned it into essentially a web brochure.
Next up: The blog. Anything you want to know about what I’m thinking… so read up, Camacho. And lastly but not least-ly: Shockeye, my solo music project. I haven’t spent any time thinking about how I’ll set that up yet… scratch that, I guess it was “least-ly” after all.
As far as WordPress goes, I seem to be having a more pleasurable time with it this time around as I am only using it as a blog. Another thing that makes WP slightly more joyful this time is the fact that I didn’t previously think to turn off the WYSIWYG editor.
Oh, yeah… they boasted that the new WYSIWYG editor in 2.5 doesn’t bork code on your posts. I had that one proven wrong within 2 minutes of turning it back on.
I won’t write a full diagnosis on WordPress 2.5; honestly, I don’t really care. It works and it was easy to setup. What else do I really need?
In my never ending search for the best CMS for me and my clients, I’ve been recently raving about SilverStripe. It’s great, but it’s a little heavy-handed, and some features flat out don’t work.
Tonight I tried out MODx CMS. So far, so good. A very similar interface to SilverStripe, with a lot lighter CPU load and smarter caching… and the file manager actually works in MODx — a complaint I have with SilverStripe. Unfortunately I’m not seeing the same MVC style framework in MODx as I would’ve liked, but there is still an extensible framework present to extend functionality.
Some day when I find the time I’ll play with it a little more.
In the mass of trying out this and that CMS for blogging and content publishing, I settled on SilverStripe. Overall, I’m sorta pleased with it.
I’m very picky about permalinks, SilverStripe has a completely customizable permalink structure which I’m very happy about. The drag-and-drop menu reorganization was really friendly and made it easy to manage a large menu hierarchy. The CMS is also very manageable and infinitely extensible.
SilverStripe ships with it’s own MVC framework which runs the CMS called Sapphire. What this means for me is that when I feel like extending the base functionality, I can do so with concepts ingrained into me from Rails. Very cool! Then I can choose to release my code back to the community as a module.
Of course, there are some features that are, in my opinion, are totally broken and not value-add functions.
The file upload manager is completely unusable. Sometimes it will upload, other times it will stop uploading completely, or even fail to start entirely. The image cropping and resizing tool is a useless feature and it makes images look terrible with every recursive edit. To me, a simple file upload interface would suffice. Something Flickr-like would be nice, but I think what SilverStripe currently has implemented is overcomplicated and completely defeats the purpose of even being in the feature set.
Other than my gripe with file and image management, SilverStripe is quite a nice start. It was a pleasure to get it up and running on my server and it has the advanced features I require. Even with the borked file management, I give SilverStripe 3 out of 5 stars for trying a new approach.
BlogMarks
Furl
Newsvine
Rojo
Email This to a Friend
If you like this then please subscribe to the