Wrappers

Wrappers provide the overall structure or frame of a web page. They generally contain static information that is common across all web pages, such as header branding, section navigation, and company logo.

A web site can have more than one wrapper. For instance, a home page, with its unique design, often requires a separate wrapper. You can also create a printer-friendly wrapper or one that optimizes your site for mobile devices.

Only a Website Administrator can create and edit wrappers. A folder-level administrator can assign a wrapper to a folder, an individual content item, or both, depending on whether he or she is an Author or a Manager.

A Luminate CMS wrapper:

  • Is edited in HTML source mode. Wrappers can't be edited with the WYSIWYG content editor. During editing, page content is represented by HTML tags which are replaced with text when the page renders. The most basic wrapper looks like this:

    <html>
    <head>
    <title> %page_title%</title>
    </head>
    <body>
    %page_content%
    <P>
    %page_powered_by%
    </body>
    </html>

  • Can be assigned as the site-wide, default wrapper.

  • Can be assigned as the default wrapper for a folder (including the root folder), overriding the site-wide default.

  • Can be assigned to any web page on a page-by-page basis in the Authoring Wizard Properties step, overriding the parent folder's default wrapper or the site-wide default. (A Website Administrator must configure the Properties step manually to include a wrapper-selection menu).

  • Can include all the functionality of a display template (including component instances, personalization and conditionals).

  • Has highly flexible preview options, including preview of draft or live wrappers and use of multiple preview users (from a pool of preview users set by a Website Administrator in Reports and Tools).

Best Practice: Avoid using a <base href> tag in a wrapper. This changes the browser’s frame of reference for all relative links in the page (links to the same host name, beginning with / rather than http://). An error or mismatch in the <base href> can cause broken links to images, style sheets, javascript libraries and other assets. It can also cause form submissions to fail.