The Plugin Layout is a container type that will redirect page rendering out of FirstMagic and into the FirstMagicPlugin. This is handy if you have custom forms or workflows produced for a different template set [like regular FirstClass, for example], that you want to be accessible from the FirstMagic website. Just fill the FirstMagicPlugin with the templates - or the template set - you want your objects to be rendered with, and publish the content in a Plugin Layout in FirstMagic: FirstMagic will open all page views in your custom templates. How it works: If you create a document or message inside a Plugin Layout, it will not be interpreted by FirstMagic. Instead, it will send the browser to the FirstMagicPlugin [Note that you cannot merely drop existing FirstClass objects into the Plugin Layout for this to work: they must be created or saved inside]. If anybody clicks on such an object, they will be sent to the FirstMagicPlugin. If anybody clicks on the container itself, they will be sent to the FirstMagicPlugin. The Plugin Layout do not have the usual FirstMagic object buttons in the toolbar, because it is not meant to render FirstMagic objects. Instead, it has the normal FirstClass pickers. You can add your own custom stationaries to the Toolbar, and they will work on the web as long as you have a corresponding template in the FirstMagicPlugin. The Custom Webpage Stationary does the same - any page published on it will be opened on a 96 template in the FirstMagicPlugin folder [meaning, you would need to write a 96 template there for it to be interpreted].