Tag: cms

RNC RFP

The RFP lays out RNC HQ’s tech vision in a way that might make more sense were hallucinogenic substances involved: “If we haven’t thought of it — think about it. If it hasn’t been tried — why not. If it’s going to be ‘outside the box’ — then not only keep it outside the box, but take it to someplace the box hasn’t even reached yet.” Like, woah.

LOL. RFPs like these is why i no longer work in CMS.

content wire interview

i recently did a new interview with paolo di maio of content wire.

Gregor J Rothfuss has been observing and working with content management tools for many years. We catch up with him over the internet to talk about open source, a subject increasingly recurring

How do you see the business model for OS developing?
In services, more and more. there are some excellent open source venture blogs that track this question in great detail: Open Source Strategies and Asay

Os tools are not very usable. Why is that? Is it just still too early in their evolution?
This held true, traditionally, but has recently been true less and less. One reason is that software per se is no longer interesting, and increasingly, developers are aware of usability issues, and a nice UI can now be considered quite sexy. This is mostly due to some well-publicized web applications that utilize AJAX technologies. At first, OSS was often in catch-up mode and had to quickly fill in holes in functionality. now that functional parity to commercial products is being reached, the focus has often shifted to these more subtle qualities.

Plus, more and more hackers understand the value of design, as exemplified by Apple who are taking geek toys and slapping nice UI on top, or Firefox, which is essentially a slimmed down Mozilla.

Only in its Firefox incarnation has full success come.

cms lessons from the best of the intranet

This year’s winning intranet designs emphasized workflow support, self-service content management, and offloading tasks from email to collaboration tools. On average, companies spent 3 years between redesigns, and 1 year on the redesign itself.

conclusions:

  • move from top-down publishing to bottom-up: more weblog, aggregation technology, xml fragment support, xlink leverage
  • reduce email load, make it easy to use intranet as part of PIM
  • provide rss feeds for workflow to do lists
  • enable trackbacks on any content type