Make your websites instantly mobile by using Magnolia's unique Standard Templating Kit 2.0 (STK). Your mobile site's look & feel is completely customizable, as is the case with all sites developed with STK.
Keep track of all your output channels with Magnolia's new multichannel support. Publish to the web, smartphone, tablet, ebook, newsletter or any other output channel from a single source. Easily assign whole pages, page areas or page components to each channel and ensure pixel perfect outcome no matter where.
Preview what your content will look like on the web, mobile, tablet or any of your custom output channels. Ships with preview for the iPhone, iPad and web right from the page editing interface, so you know exactly which content will be rendered on which device, and how it looks.
Magnolia now supports CMIS (Content Management Interoperability Services), a standard that Magnolia co-sponsored. Easily access and edit Magnolia documents with e.g. Sharepoint, Alfresco or Photoshop as if they were local documents.
We have made page editing nicer on the eye and more intuitive. Edit page content by clicking on what you wish to edit, and create new content by clicking on the placeholders for new components. Also, when you want to move content, it is clearly indicated where you can move a component to.
Magnolia's Standard Templating Kit 2.0 has been updated to HTML5, including support for HTML5 video. STK 2.0 also provides mobile website templates and follows the newest best practice in Javascript, CSS and semantic HTML. Some new page components have been added as well.
Blossom is simply the world's best framework to combine business logic developed in Spring with content management and multi-channel publishing. Magnolia 4.5 ships with Blossom 2.0 to provide access to Magnolia's new templating API. It's never been easier for Spring developers to create a virtual presence for their enterprise.
With our move to JCR 2.0 we now support secure access of content, right through the standard API, no matter if you want to access content from within Magnolia or externally. Use any tools adhering to JSR-283 (or JSR-170) to manipulate content in an access-secured way. The old content API is being phased out.
Many lessons learned from Magnolia's Standard Templating Kit have been incorporated right into the core templating mechanisms, including area management. The new API is much easier to learn, use and maintain and will reduce the time it needs to create new projects. It is now also easier to add custom tempting languages.
Demo Project
Yes, we're open.
