Page History

This page provides a high-level overview of Magnolia apps.

...

All apps are implemented using the app framework, whether they are apps provided by Magnolia or your own custom-built apps. Because content is at the heart of Magnolia, there is a specific framework subset dedicated to creating apps that manage content; apps created using this framework subset are referred to as content apps. Some examples of content apps are the Pages and Assets apps, some non-content app examples are the Log Tools and About Magnolia apps.

...

• An editor may need to access product data in a remote ERP system in order to create content to sell the products. Such remote data can reside in a relational database, on the filesystem, in a Web service, or some other data delivery service. For convenience, you make the remote data available inside the familiar Magnolia environment so editors don't need to jump from one system to another. For example, Magnolia's IBM WebSphere Commerce Integration module connects a WebSphere Commerce store to Magnolia. 
• Your authors need to choose image assets from Flickr but they do not have to leave Magnolia just because the content resides somewhere else. With a content connector you can decouple content management from content storage. 
• Your clients need to contact you via forms on your website: the External Forms module provides functionality to render external forms configured in marketing automation software such as Oracle Eloqua on Magnolia pages. 

• Your company uses Amazon S3 to store large assets: the Amazon S3 Connector module provides an app that allows users to manage assets in Amazon S3 while using them in Magnolia.  

...