Magnolia 3.0 Enterprise released, with Sitedesigner online editor

Discussions

News: Magnolia 3.0 Enterprise released, with Sitedesigner online editor

  1. Magnolia International celebrates Magnolia's third anniversary with the release of Magnolia Enterprise Edition, a major upgrade to the JSR-170-based Enterprise Content Management system. Magnolia Enterprise Edition introduces significant new features and is backed with unlimited support from Magnolia International. Magnolia Enterprise Edition allows you to:
    • create custom layout directly in the browser
    • display Magnolia content in JSR-168 portals
    • authenticate and authorize using directory servers (LDAP, ADS)
    • package content and resources into single entities to facilitate multi-stage deployments
    SITEDESIGNER In addition to Magnolia's powerful custom template abilities Magnolia Enterprise Edition introduces Sitedesigner to create complete web site layouts directly in the browser. Unlike standard template-based approaches that simply let a user pick between a couple of predefined layouts, Sitedesigner completely replaces traditional client-based web design tools. This has significant benefits:
    • fully working prototypes can be build within hours
    • new ideas can immediately be realized online
    • layout (as well as content) is versioned and changes can easily be undone
    • updates are painless, since no custom templates are involved
    Sitedesigner produces valid XHTML, generates and consumes RSS, provides functionality for news items, glossaries, FAQ's, podcasting, multimedia, mp3's, navigation, sitemaps, imagemaps, custom CSS, analytics and statistics integration, content inheritance and seamlessly integrates into the Magnolia document management system. In addition it can easily be extended with custom functionality without breaking the upgrade path. JSR-168 PORTAL SUPPORT Magnolia EE is delivered with Portal integration that allows you to publish content to any JSR-168 Portal with Magnolia's traditional ease-of-use. Magnolia's distributed architecture provides unique benefits for large-scale portal deployments. Each portal can contain its own copy of Magnolia as a subscriber to the Magnolia author environment. This eliminates the traditional communication bottleneck between a portal and its content delivery system and allows for unlimited scalability and speed. LDAP/ADS DIRECTORY SUPPORT Magnolia Enterprise Edition uses JAAS, a standard for authentication and authorization. This standard allows to use JAAS modules to implement single-sign-on requirements or connect to existing directory servers. Magnolia contains functionality to connect to ADS and LDAP servers for user authentication. This makes it easy to deploy Magnolia in large scale intranet settings where user management infrastructure already exists. PACKAGE MANAGER The Package Manager allows anybody to bundle arbitrary content, including templates, files and static resources, into a single entity. This makes the Package Manager an ideal tool for custom backups, delivery of updates and multi-staging scenarios.

    Threaded Messages (4)

  2. JBoss, meet Magnolia. Liferay, meet Magnolia. Portal, meet Content.
    Very nice, and congrats on this release! ;-) Q: Are there any plans to integrate the authoring environment as a portlet? STAY METAL! Roy Russo
  3. authoring in portlet[ Go to top ]

    Thanks Roy!
    Q: Are there any plans to integrate the authoring environment as a portlet?
    No we do not plan to do this. We see Magnolia as serving content to many portals simultaneously, and in that scenario it would make little sense. However if all you want to do is edit single pages of a single Magnolia installation from within a portlet, that should be straightforward to realize. Do you see specific use cases / customer requests for that? Boris Kraft
  4. Re: authoring in portlet[ Go to top ]

    However if all you want to do is edit single pages of a single Magnolia installation from within a portlet, that should be straightforward to realize. Do you see specific use cases / customer requests for that?
    Perhaps, but the problem with this scenario is that once you release something basic like this, users are going to want more, ie. versioning control, move/copy/upload content, etc... So even a small feature like this can suffer from scope creep. ;-) You can chalk my suggestion down as the rantings of a lunatic for now, and we should see what the community/customers suggest, as they begin to absorb this new CMS choice for JBoss Portal. Again, great work! STAY METAL! Roy Russo
  5. Re: authoring in portlet[ Go to top ]

    You are right, thats exactly what we wait for - feedback from the users. Right now we are finalizing Sitedesigner to be usable directly with portals, i.e. with a couple of changes you can design the look and feel of the portlets. Lots of good stuff to come, now that we have the basics defined. Cheers Boris