Short answer: I think it's a great fit since, this is basically what I have done before.
The useful answer: Let's see. You have a site that uses a lot of different apps? If they are iframed, then sure, no problem, if not, then some more integration-work is done today right? To begin with Magnolia has excellent Spring support in the form of the module called Blossom. It gives you the ability to integrate seamlessly with Spring, and by doing so I think you won't really have any problem integrating any apps or services that exist today. Integration is the high-point of Spring after all(in my eyes). But if you also feel that you want to convert your dozens of apps then I can at least vouch for a grails plugin that me and a college have made, called Maglev. It's designed to be used just like any other grails plugin by a developer who is at home with the grails idioms and conventions. It's fairly quick to start up a magnolia-grails-app this way, and I'm sure it's not really a big hassle to convert an existing app to magnolia. But let me just say that from experience that there are few if any CMS out there with the adaptability and usability of Magnolia, so if it can be done, Magnolia is a great bet. I have never felt hampered by using Community Edition, and all this can be done to a degree in CE. EE is for the bigger enterprise features. Things like clustering with a few extra public instances is also an EE feature. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=1c91a7e4-0116-4529-9c79-fa065c3224b7 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
