Including pages

Including is how you reuse content: you drop one page inside another by writing its name in double curly braces — {{Page name}} — and its content appears right there. Because an included page can take parameters, the same one can render differently everywhere it appears.

{{Solar System Navbox}}

This pulls in the Solar System Navbox page and renders it in place. Most reusable content — navigation boxes, infoboxes, banners — is just an ordinary page you include this way. There's no separate concept to learn.

How {{Name}} resolves

{{Name}} is looked up in two steps:

1. the reserved helper space (/template/Name) — a small, fixed set of building blocks, then
2. the general pages (/wiki/Name) — an ordinary article.

So it finds a reserved helper if one exists by that name, and otherwise includes the general page. There's no prefix to type in wikitext — the {{ }} implies the lookup.

You type	What happens
{{Infobox game}}	Includes the Infobox game page
{{Solar System/Planets}}	Subpages work too
{{Nope}} (no such page)	Renders a red create link

Forcing the general page

If a reserved helper shadows a name you want as a plain page, add templatebypass as the first argument to skip the reserved space and go straight to the general page:

{{Name|templatebypass}}

Passing values

Add pipe-separated arguments to feed an included page's parameters:

{{Infobox game|title=Black Desert Online|year=2015}}

See Parameters for how a page receives and uses these, and Include control for showing content only when a page is included (or only on its own page).

Where included pages live

Almost everything you include is a normal page in the general space (/wiki/Name). A page that shares its subject's title takes a Navbox suffix so the two can coexist:

{{Star Wars Navbox}}   ← the navigation box (a general page)
[[Star Wars]]          ← the article

Only a small reserved set of syntax helpers lives in the helper space (/template/Name) and is edited by admins: Collapse, Endcollapse, EmbedYoutube, googlemap, Ruby, Colorlink, Note, Ref.

Safety limits

Including is protected against runaway expansion — you'll get an inline error message if:

• a page ends up including itself (template loop detected),
• nesting goes too deep (recursion depth limit exceeded),
• the expanded output grows too large (include size limit exceeded).