This document discusses embedding Magnolia content management into internet banking applications. It summarizes how the company customizes Magnolia for financial clients, using Freemarker templates and the Apache Wicket framework to render content. The content provider API allows applications to access Magnolia repositories or other external repositories. Benefits include faster development and customizable skins without changing backend code.

1. Embedded Content Management with Magnolia Making Content Management a key feature of an Internet Banking Application Suite

3. We specialize in customizing Magnolia for the financial industry worldwide. --Banking, Insurance, Brokerage etc.

4. Current clients using Magnolia for internet banking through our Fidelity Information Systems Partner platform include:

5. Ally Bank US (Formerly GMAC Bank)

6. Ally Bank Canada

8. Internet Portal - Service Framework + Magnolia API + UI Framework + FreeMarker

10. Content Managed Web Application Architecture Overview

11. Overall CMS Deployment Overview

13. Concept of a Content Provider API to make the web application able to access our core Magnolia repository or any external repository if necessary.-- The Content Provider API utilizes the MgnlContext Class to access the embedded content repository.

15. Does not need to be compiled

16. Can be hidden from other processing engines

18. Sophisticated design markup can be added after the application has been developed

19. Easily customizable markup

20. Skinnable per Bank and even per Bank Customer based on login information

22. Combined Wicket XHTML and FreeMarker The <wicket:remove> tag ensures all Freemarker tags will be removed from the final markup in the wicket application. The Wicket XHTML tags will be hidden by the browser when editing the page in Magnolia Author.

23. Content Provider API Example Repository: -- Index - Header - Label - Footer - Label Example Call to our Content Provider API -- ContentProvider.getLabel(“index.header”) -- ContentProvider.getLabel(“index.footer”) Properties File if no Content Repository index.header.label = Mylabel1 index.footer.label = Mylabel2

26. Content Management as part of the Business Application LifeCycle

27. Questions? Thank You!