I'm not sure how you define a "solved problem." Do you have an example? When it comes to end-user software applications, I can't think of any problem that has b

I'm not sure how you define a "solved problem." Do you have an example? When it comes to end-user software applications, I can't think of any problem that has been solved categorically (contact management, calendaring, browsers, word processing, spreadhseets). That's why I would take the other comments in this thread with a grain of salt. True, nobody has solved content management -- BUT, the leading solutions have put in a ton of work to solve vast swaths of the problem space even if they haven't nailed the whole thing. Wordpress, for example, while not the most architecturally elegant piece of software in the world, is an incredibly rich, powerful, and useable content management system. The plugin system enables a developer to extend the application in any number of directions, while the administrative toolset is sleek and sophisticated yet easy enough for hundreds of thousands of bloggers to use. Okay, I didn't mean to turn this is into an ad for Wordpress (which I've used as a CMS on several projects, btw). My point is simply that your CMS would have to get very far advanced before it even reached the terrain where the problems that Wordpress has not solved lie. I don't mean to discourage you in your project, but simply to point out the road might be more difficult than others make it appear. As a consolation here are a few areas that I haven't (in my own limited experience anyway) seen many CMSs nail effectively: * Content versioning * User commenting features (threaded commenting, ratings, user management/ownership of comments -- basically disqus's whole business is built on this lacking) * Snippet management (tools to manage little copy snippets etc., not just pages/posts) I'd be curious if anyone else had any specific features they felt were part of the "unsolved" problem set.