As more of our campus uses Magnolia to manage their websites, we've heard a request come up with increasing frequency:
"We have an application that we'd like to use the template from Magnolia for. The app is written in PHP/Perl/ASP/whatever, so we can't move it into Magnolia, but we'd like to wrap our Magnolia site's look, feel and menus around the application." My first thought is to provide Javascript includes for a header and a footer that our customers could then put into their application template to get everything from Magnolia. Then we'd have to render a page, strip out the content, and convert it into a bunch of "document.write" statements, finally serving the result out as the javascript file that would be included. Has anyone been down this road before? Any hard-won experience, advice, or suggestions for how best to go about this would be welcome. Sean ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
