<Placeholders>

Placeholders allow you to define reusable content that can be used in other placeholders, page templates and in page content. There are two types of placeholders: those that replace previously defined ones, and those that append data to previously defined ones. The second type are used mainly by plugins to assemble your header and footer. BlüeBox will alert you during the build process whenever a placeholder is overwritten or appended.

Example:
<Placeholders>
  <Placeholder>       <Name> c:\folder\pics\        </Name> <Content> file://c:/folder/pics/         </Content> </Placeholder>
  <Placeholder>       <Name> file://c:\folder\imgs\ </Name> <Content> http://domain.com/imgs/        </Content> </Placeholder>
  <Placeholder>       <Name> %Menu%                 </Name> <Content> [HTML menu goes here]          </Content> </Placeholder>
  <PlaceholderAppend> <Name> %Menu%                 </Name> <Content> [HTML menu extensions go here] </Content> </PlaceholderAppend>
</Placeholders>
Properties:
<Placeholder>
This tag indicates the start of placeholder.
<Name>
 
This is the name of the placeholder.
<Content>
 
This is the content to substitute for the placeholder.
<PlaceholderAppend>
This tag indicates the start of a placeholder.
<Name>
 
This is the name of the placeholder. If the placeholder does not already exist, a new one will be created.
<Content>
 
This is the content to append to a placeholder.
Technical Details

BlüeBox defines internal placeholders that can be used to access site and page properties.

Internal Site Placeholders

Site-wide placeholders are commonly used in the header and footer to access setup data. Most of them are associated with <Setup> properties. Placeholders will be cleared if the data is undefined or does not exist. The following is a complete list of internal site-wide placeholders.

%AppName%
The application name (BlüeBox).
%AppVersion%
The BlüeBox version number.
%BuildVersion%
The BlüeBox build number. Build numbers are used during product development to track minor changes and can generally be ignored by users.
%WebsiteURL%
The website URL.
%OutputPath%
The output path.
%FeedLink%
When an RSS feed is enabled, BlüeBox will use a page template ( rssFeedLinkT ) to return a link to your RSS feed.
%HomePage%
The home page.
%LangCode%
The language code.
%Favicon%
The favicon URL.
%PluginsURL%
The plugins URL.
%SiteTitle%
The website title.
%SiteDescription%
The website description.
%SiteLogo%
The website logo URL.
%SiteBanner%
The website banner image URL.
%SiteAvatar%
The website avatar image URL.
%SiteHeading%
This is equivalent to the site logo, or the site title if the site logo is not defined.
Internal Page Placeholders

Generally, you would use Data References to access properties of the current page. Data references, however, are resolved at build time, and BlüeBox, for resource purposes, does not store your website's headers and footers in the same area of the database as your pages. Therefore every page must store the metadata needed by the headers and footers so that they can be resolved at page access time. The following is a complete list of page placeholders that are are stored in the database for this purpose.

%PageAuthor%
The page's author.
%PageFilename%
The page's filename.
%PageKeywords%
A comma delimited list of page keywords and hashtags.
%PageOverrides%
The page's overrides property.
%PageImage%
The URL of the page's image in medium format or smaller if not defined (m->s->l->t).
%PageRedirect%
When a redirect URL is provided for the page, BlüeBox will use a page template ( pageRedirectT ) to return the redirect.
%PageTitle%
The page's title.
%PageURL%
The URL of the page.