tag:blogger.com,1999:blog-3198935374994345981.post3270498689726360771..comments2010-06-03T08:50:23.542+02:00Torkel Ödegaardnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3198935374994345981.post-79323388322941308062008-08-08T20:10:00.000+02:002008-08-08T20:10:00.000+02:00I agree. CMS are a typical case of providing "everything for no one". <BR/><BR/>Customers <B>always</B> want you to add extra functionality that is not provided by the CMS and often not even intended to do so.<BR/><BR/>And then you'll either get frustrated by poorly designed and insufficient CMS APIs or end up bypassing the CMS API completely.<BR/><BR/>Since the web demands more and more complex features, I don't see a valid future for CMS which focus on providing simple web content that is not very customizable.Alexnoreply@blogger.comtag:blogger.com,1999:blog-3198935374994345981.post-37414028450850902532008-08-08T09:49:00.000+02:002008-08-08T09:49:00.000+02:00Good post, I have done some work using a CMS product and I have certainly felt the pain. Especially when the feature requests just keep on coming and you have to use the CMS product in ways it wasn't designed for.Jacknoreply@blogger.com