Content-Management

One of the many tricky decisions to be made when building content management tools is how to allow users to control the basic formatting of their input without breaking your carefully crafted layouts or injecting nasty hacks into your pages. One approach has long been to provide your own markup language. Instead of allowing users to write HTML, let them use bbcode, or markdown, or textile, which have more controlled vocabularies and rules that mean it’s much less likely that problems will occur. ...

Yesterday we pushed the button and launched the new version of GOOD Magazine, a site I’ve been working on for the past couple of months along with the folks at Area17. It’s a relatively large Ruby on Rails system built on top of the ORGware system (refitted as an engine) and supported with a caching system built for Madame Figaro. Most of my work has been under the hood, but where I’ve touched the frontend I’ve tried to make use of microformats and other good practices. We’re providing a range of atom feeds (which will become easier to find over time as we make some refinements) but eventually I hope that we’ll have all listing pages using hAtom so that anything can be a feed. ...

A recent comment reminded me of an old entry proposing yet another project I never had time to follow through with: Using Trac and Subversion with Social Documents. The idea there was to make use of subversion’s utility for version control and trac’s existing frontend for browsing that to present versioned documents. In hindsight, I don’t think trac would actually be a good frontend for this unless the intended audience was entirely techies. Trac works for those of us who use it every day to follow a variety of projects, and its ability to combine a wiki with version control of the ‘official’ versions of documents provides some interesting ideas, but the interface just wouldn’t work. ...