Hi All,
I am working on a client project where they specified Midgard/Aegir as a requirement. It was for a friend in desperation, so I dusted off my PHP brain and got stuck into it.
While there are some things that frustrate me after the clear environment of ACS, I am learning a lot about what functionality in the API and structure is usefull for a content dominated site. Midgard has an amazingly flexible base, as can be seen by what get's bolted on top liek MidCOM.
Something very cool coming out of OSCOM is a mozilla-embedded hierarchical user interface to the content editing (I believe based on some stuff from a Zope project) - check out this url: http://www.oscom.org/Projects/Twingle
especially view the pdf presentation:
http://www.oscom.org/attachment/72c7a5e5939d06b8545b6a41cc703144/e0b427078c9a68d4c03c8a8aab698429/Twingle_for_Developers.pdf
To get a feel for a cms structure, people with spare time on their hands will find reading the midgard manual valuable, it has a lot of schema diagrams etc. as well as function listings etc:
http://midgard-project.org/manual/en/
Midgard is object-ish, although it separates things like topics and articles, and there is a tacked-on unique ID concept that is a bit kludgy.
When I am done with this project, I am going to try to get a similar project with a slacker timeframe that will allow me to build midgard-like functionality into an OACS package. No promises, but if I can swing such a project... happy days.
