Template:LoadBox/doc

This template creates a box able to load content from another page.

Usage

 * page
 * Specifies the wiki link text of the content to be loaded (e.g., ).


 * title
 * Specifies the identifying text to be displayed in the box, and its link target string (e.g., ). Leaving title unspecified will generate an error message and should be corrected.


 * float
 * Optional. Specifies how the box should be positioned. The only two valid values are, which creates a left-floated box, and  , which creates an un-floated box spanning the available width. If float is not specified, or an invalid value provided, LoadBox creates a right-floated box. Can also be overridden with the style parameter (below).


 * class
 * Optional. Specifies one or more css classes to add to the outer box.


 * style
 * Optional. Specifies additional styling code for the entire box. Its value should be a css declaration or declaration group with no surrounding braces or quotes (e.g., ).


 * titlestyle
 * Optional. Specifies additional styling code for the title. Its value should be a css declaration or declaration group with no surrounding braces or quotes (e.g., ).


 * contentstyle
 * Optional. Specifies additional styling code for the loaded content. Its value should be a css declaration or declaration group with no surrounding braces or quotes (e.g., ).

Considerations
The generated box will change its size when its content is loaded by the reader. Consider using - to ensure that the box doesn't overlap or push aside other content on the page inappropriately (for example, the Usage heading above has a - before it so that the example won't overlap it when its content is loaded). Don't necessarily put - directly after LoadBox -- it may be better to put it below the content the LoadBox accompanies.

Alternatives
The preferred method for initially hiding content that won't significantly impact server load times is a table with, because it keeps all of an article's content in one place.

LoadBox is intended for small article fragments which could impact server load times if placed in the article directly. For large article fragments, which could actually constitute article sections, consider LoadPage.