One of the things that has always made us impressed -- and uneasy -- about PaperThin's CMS product "CommonSpot" is its ease of implementation and use. In industry parlance, the product is very "out of the box." But remember that whenever a software product offers quick solutions, the vendor necessarily makes assumptions about how you want certain features executed. One particular CommonSpot shortcoming is the substantial constraints it places on HTML markup within both the CMS interface and rendered pages. In a recent wide-ranging interview, designer Todd Dominey describes some of the challenges he encountered implementing a new layout for PGA.com on top of CommonSpot. (Thanks to Darrell Austin for the link.) The import is less about PaperThin itself and more about the types of trade-offs you'll inevitably face at the lower end of the marketplace...
Read the interview at the Web Standards Project