Why do you want a CMS where content types can be created via the admin panel? This is not a role I see the average end user of a CMS using (it's a design/architectural feature of the data structures used) and by having it in code it's left to the developers who understand this kind of thing.

Do you have a use-case where this approach would be useful?

For example wanting to create a simple data entry form. Wanting to create a poll.

I do not recommend you any CMS because I do not use any, but I can tell you that in the next months I will be developing one from scratch to address needs of some new sites that I intend to launch next year.

I will not use any third party code, because as usual I do not want to rely on the limitations of other people approaches.

What I can advance to you is that I will be using the UCM - Use Case Mapping methodology, not only to separate the presentation, controller and model, but also to provide a service layer that will make it easy to distribute application layer components to backend implemented most likely by Gearman worker processes.

There is a bit outdated article on UCM here, that does not cover the finalization step and the service layer that I use in today's projects. But it should give you an idea.

http://www.meta-language.net/metastorage-example.html

Of course I will use Metastorage ORM generator tool as usual. It generates Metabase XML schema definitions that allow me to version schema changes and provide a smooth upgrade path that will not get in the way when I think of adding new features.

As for content storage and presentation layout, I have not it all figured out, but I will probably use XML definitions that are mapped to database records cached as PHP serialized structures, as I have been doing for many in other projects that I need to configure modules of content, like e-commerce stores or job candidates skills.

That is the way I assure that content identifiers on production get the same names or values on development and production environments.

Anyway, although I cannot promise that will be an Open Source project, just let me know if you want to be kept up to date of the progress of the project.

First, your blog's comment system is terrible. I shouldn't have to move to the bottom of your comments (on another page) to post a comment. It's meant to be easy to use so that people are encouraged to interact.

That being said, I don't use CMS packages in my work, but I've found Drupal and ModX to be the most agreeable out of the evaluations of software that I have performed. ModX certainly seems to have the least learning curve of any I've seen.

Hey,
do you know about papaya CMS? It's opensource and imho not as like as all other CMS. I consider it more like a content management framework, since you have all freedom to tailor it to your needs.
It's really responsive, implements a lot of cache levels and it uses standards like XML and XSLT.
If you are looking for a cms enabling your to handle things your way your definitly have to have a look at http://papaya-cms.com.

Been a while since I have checked out papaya. Most of my coworkers love XSLT. However papaya has one serious flaw that makes it not useable for me: Its GPL'ed. Means that the risk of running into licensing issues is too big to make it my goto CMS.

use Drupal. Best PHP CMS outthere

Carlos

@Carlos @ 23/11/2009 04:11 CEST

Drupal is functional mess. It's a clear showcase what you can achieve with the bad habits that reigned in the old php days.
It is so frustrating that all cool php apps are such a mess. One day I thought it was nice to look at the source of phpmyadmin. Man, this is programming gone wrong.

Even my beloved Doctrine has serious flaws. Look at the god-class Doctrine, it tries to be everything, including your grandmother. But ok, Doctrine 2 will be a lot better I think.

I have to agree, typo3 is a monster. If you just install it and use never touching the code i think its fine, i mean is more or less like others. But if you plan on changing anything or writing extensions just forget about typo3. Its really bad in sense of documentation, structure and 'magic'.

I liked Drupal, very good doc, good community etc. But i assume you are not happy with it. i agree that navigation in admin menus and getting to know how to click-out what is confusing at the start as there is a lot of it.

Joomla and mambo are just bad in every way i can imagine.

ps. i would not choose cms because it uses XLST ;-) i think i would rather stay away :- ) just because some people like to make simple things in very complicated way but i dont know papaja so its just my gut feeling.

I have a few more observations on my site http://artur.ejsmont.org/blog/category/free-tags/cms

I just found a new content management system (actually they call it cm "framework"): http://diem-project.org/

Didn't test it but sounds good.