Magnolia Content Management

JSR-170 compatible content management system
Download

Magnolia Content Management Ranking & Summary

Advertisement

  • Rating:
  • License:
  • Freeware
  • Price:
  • FREE
  • Publisher Name:
  • Magnolia International Ltd
  • Publisher web site:
  • http://www.magnolia.info/
  • Operating Systems:
  • Mac OS X 10.2 or later
  • File Size:
  • 22 MB

Magnolia Content Management Tags


Magnolia Content Management Description

JSR-170 compatible content management system Magnolia is the first open-source content-management-system (CMS) which adheres to the upcoming standard of Java content repositories (JCR).Its main goal is ease of use for all parties involved in running a CMS. It features a very flexible structure, platform-independence through the use of Java and XML, a simple to use API, easy templating through the use of JSP, JSTL and a custom tag library, automatic administrative UI generation, transparent and uniform data access to multiple data repositories, easy configuration through XML, easy application integration and easy deployment with professional staging on any J2EE Server.Magnolia is available free of charge as an open source product. Magnolia is provided as a binary download based on tomcat for easy deployment on Mac OS X, Solaris, Linux and Windows.NOTE: Magnolia is licensed and distributed under the terms of the GNU Library or Lesser General Public License (LGPL). Here are some key features of "Magnolia Content Management": · Instant inline editing · Browser-based user interface · Human readable web addresses · Versioning · Integrated document management · Role-based user management · Full-text search · Multilingual user interface · Unlimited page and paragraph designs · Syndication and staging · Java Content Repository (JCR) · Workflow · Unlimited scalability, clustering and load-balancing Requirements: · Java What's New in This Release: · Improved templating: we improved Magnolia's templating by providing template definition and model objects; other useful objects are also now available in the templates, reducing the need for scriplets. This gives the developer more power and flexibility, while the template code becomes more readable. See What's new in templating with Magnolia 4.0 for more details. · FreeMarker support: we added full support for FreeMarker templates for both page and paragraph templates. Both FreeMarker and JSP templates can be used in combination. But in addition to the JSP templates the FreeMarker templates can be loaded from the classpath, repository or file system. See our Magnolia FreeMarker integration page for more details. · Standard Templating Kit (STK): Magnolia now provides a full set of useful templates and paragraphs; use-case-driven templates, flexibility and extensibility are key points of the STK. Standards compliance and accessibility, too! The STK will be part of the Magnolia Enterprise Edition, but also available as a separate Badgeware download. See the Standard Templating Kit documentation for more details. Note that this first release of the STK lacks translations. Feel free to jump in and contribute! · Extended Templating Kit (ETK): while the STK is freely available, the ETK is only available with the Enterprise Edition. It adds advanced features like multiple site configurations. · New developer samples: we replaced the previous Samples module with new developer-oriented examples featuring the latest developments within Magnolia. The new developer samples show a range of functionality from basic things like templating to more advanced topics like adding custom filters or using module configuration beans. This is done with minimal code to keep the examples as simple as possible. The examples contain both FreeMarker and JSP templates. · In-place templating: the FreeMarker templates can be stored in the repository (which allows, amongst others, activation and quick prototyping). We plan to add WebDAV support in 4.1, so that a template workspace can be mapped to a network drive. This would allow developers to edit templates directly in their favored editor as a quick way to learn more about Magnolia or do smaller projects that do not demand the rigourous release-cycle of enterprise deployments. · Resource module: similar to the templates, it is useful to have the CSS files stored in the repository (and thus, under access and version control). Similar to the In-place Templating Module we will add support for WebDAV in 4.1. · Link API: the link API as been moved from info.magnolia.cms.link have moved to info.magnolia.link. LinkResolverImpl, LinkHelper and LinkUtil have been replaced by the single LinkUtil class. (MAGNOLIA-2542) · API cleanup: we cleaned up the Magnolia API by finally removing of a lot of deprecated code. Check the complete list of removed methods and classes, along with explanations of what happened to them. · Breaking API changes: a couple of API changes were introduced, and you might want to read about them. · Modules: (!) modules that were written for Magnolia 3.0 are not supported anymore, and will have to be updated. · Jackrabbit 1.5: Magnolia now ships with Jackrabbit 1.5, which provides performance and reliability improvement over the previous version. · Dependencies and 3rd party libraries: we've updated a lot of the 3rd party library we use. See MAGNOLIA-2532, MAGNOLIA-2536, MAGNOLIA-2537. · Multi-value support: we've introduced multi-value support in dialogs with the DialogMultiSelect / MultiValueSaveHandler combination. (MAGNOLIA-2363) · Logging configuration: the default logging configuration has been revised and now provides a clearer layout. · Java 5: Magnolia 4.0 still works with Java 1.4. However, we're moving forward, and the next releases will require Java 5.


Magnolia Content Management Related Software