Recent Blog Entries

The Complete Archive

Trends by Vendor

Web Content Management Trends

Enterprise Portals Trends

ECM Trends

Web Analytics Trends

Enterprise Search Trends

SharePoint Trends

Digital & Media Asset Management Trends

XML & Component Content Management Trends

E-mail Archiving & Management Trends

The Web CMS Report 2009 looks at... Magnolia

"However, one important point to note here is that unlike other systems, the content is created from the perspective of the published web pages. So you first have to define pages and then add paragraphs using submitted content. In other words, Magnolia is, comparatively, a very page-oriented system. As elsewhere, we'll argue this is not a bad thing, because most web editors think that way and most websites (especially simpler sites) work that way. However, if you plan more intensive content component reuse, this system may not be ideal. "

More about The Web CMS Report 2009

NEW at CMS Watch

	The Web CMS Report 2009: In its 15th edition, this report evaluates 42 web content management systems and vendors... Read more
	The ECM Suites Report 2009: This report evaluates 30 ECM offerings... Read more
	Join us in Rome: On November 6-7 in Rome, CMS Watch's Theresa Regli will teach a tutorial on "Enterprise Search Technology and How to Optimize It"... Read more

 

Magnolia's new enterprise edition is more of a departmental tool

14-Jul-2007

We've now started coverage of Magnolia as a part of the Web CMS Report. Like many open source Web content management tools, Magnolia has seen growing exposure in recent years. In recent news, the product now also supports IBM WebSphere Application Server, building on its J2EE technology base. With this move and a new enterprise licensing model, Magnolia is clearly trying to position itself with larger enterprises, much like open source competitors Alfresco and eZ Publish.

Magnolia has some modest strengths in this vein (e.g. usability, localization, well-regarded support and community), but for implementation at an enterprise level, the platform's weaknesses (e.g. limited staging and deployment, small community, spotty documentation) still stand out. As we conclude in our review: for a departmental setup, with a handful of super-users as the only contributors, Magnolia might offer a good fit.

- Submitted by: Janus Boye, Contributing Analyst

All CMS Channel Trends

Join the conversation

Wondering about CMS Watch research? Sign up to receive free samples of any of our products.