Hi all, Magnolia provides a feature rich interface for managing JCR 170 based content. Based on a review of RC3 it uses a handful of custom content types currently including: * mgnl:content * mgnl:contentNode * mgnl:metaData We have an established more strongly-typed content model we'd like to manage, potentially using Magnolia. Has anyone used Magnolia with other custom content types created to model a particular problem domain e.g.? * acme:fooBarPage content type If not, is it feasible to use Magnolia for custom content types or is the CMS fundamentally based on the mgnl:* types? All comments appreciated. Regards, Shaun. PS> Well done to the team for getting RC3 released.
Send instant messages to your online friends http://uk.messenger.yahoo.com ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
