OSCOM is an international, not-for-profit organization dedicated to Open Source Content Management.
The goal is to bring together as many great brains as possible to build a network and grow the community of open source content management.
We want to show the world that there are already great and easy-to-use open source content management solutions out there.
Sounds good to me [Joe]
OSCOM – Open Source Content Management
A nice intro to In-Flow and email based Social Network Analysis. scratches the history and potential usage of this emerging discipline.
My God. A place with tons of OpenSource CMS’ installed ready for you to check-out. Dandy if you are trying to compare OpenSource solutions for your Content Management needs.
Pretty nifty, in that htey rebuild the various (41 at todays count) packages efery hour on the hour, so you always see a fresh-ish build.
Content management software hasn’t worked because it was badly designed and massively over-hyped. Software companies lied about their products, charging criminal prices for crap software. It hasn’t worked because organizations didn’t understand content. They wanted a quick fix. They issued specifications that bore little relation to what they actually needed.
SIGIA-L Mail Archives – February 2003
Worthwhile thread named:
“Study: Content Management Tools Fail”
with varrying viewpoints on how CMS has evolved, failed to deliver on it’s promise and why.
A Blog network analysis attempt
Unfortunately, they’re using Standard Meta Tags and Dublin Core association instead of RDF semantics, but maybe thet will change. A noble effort none the less!
Blizg – The Blog Resource
Here we combine a module holding the banner with another which hold our global navigation. This gives us a couple things: 1) the ability to use them together so your templates look clean and neat, and 2) by keeping the components separated, the ability to use them separately, say if you just want the banner with no navigation in a transactional area.
It starts with the “header” area. On my site that area’s the same throughout, so there’s no reason to not have it in one generalized place. We’ll then include that in all of our templates which need it, and then when we edit it in one place the whole site will reflect the change.
MovableType ships whith a series of tempaltes which do it’s bidding. What’s kind of silly about them, is that they are templates in that they are the basis for rendering your site, but they are not very abstract… that is, there is a lot of repitition.