I read a great white paper on open-source content management last night called “Content Management Problems and Open Source Solutions.” In it, the author examines several different scenarios and profiles over a dozen different open-source content management systems, explaining the key features of each and why it’s right for the scenario he’s recommending.
If you’re a content management geek, and love trying new systems, this is a good paper to read. It’s extraordiinarily well-written, up-to-date, and it gives you a solid taste of a bunch of different platforms. (In that respect, it’s like a buffet — and who doesn’t like a buffet?)
What I liked is how the author divided things up into four scenarios, understanding that no CMS is good for everything. He covers:
While I applaud his deliniation of different use cases, I do think he put some things in the wrong spots.
He has high marks for eZ publish and Typo3, which is nice. I didn’t have much luck with Typo3, but it’s got good buzz and there’s the church project built on it that we discussed last week. A commentor to that post has much to say about Typo3 as well.
For breadth and eye opening ability, It reminds me of The Mother of All Content Management Discussions from last month. This is a great read. If you like content management, give it a look.
The Web Empowered Church: This is a system to power your church Web site that's built on Typo3 -- the founder of which proclaims his faith directly in the license agreement. The WEC is a ministry of The Foundation for Evangelism designed to help churches around the world apply…
Making A Better Open Source CMS, by Jeffrey Veen: This is a great article -- a rant, really -- about how much the author thinks the open-source CMS offerings just plain suck. He laments about a lot of things I agree with. The real goldmine, however, are the comments. …
http://www.geocities.com/eddyczachorwak/beach.html >g string beach girls http://stewartgroscost.rapidboards.com >sex on the beach http://kalatheresaman.beep.com >nude beach pics