Including pages

Writing a page’s name in double braces includes that page — its content is inserted, fully rendered, at that spot:

{{Welcome box}}

Includes keep repeated content in one place. Edit the included page once and every page that includes it updates. Infoboxes, navigation footers, and notice banners are all built this way. Includes can also take parameters, and an included page can control which parts of it are included.

Where the content comes from

{{Name}} looks the name up in two places, in order:

1. The Template namespace — pages under /template/…, written specifically for inclusion. Lookup is case-insensitive: {{collapse}} finds Template:Collapse.
2. Regular wiki pages — if no template matches, the article with that title is included instead. This is how shared page fragments (for example navbox pages) work without living in the Template namespace.

To skip templates and force the regular wiki page, pass templatebypass as the first parameter:

{{Rome|templatebypass}}

The flag itself is consumed — the included page never sees it.

If the name matches nothing, the include renders as a link to the missing page — blue like every other link (this wiki has no red links).

Writing the name

• Names are written exactly like page titles: {{Star Wars}} with spaces.
• Underscores are not spaces. {{Star_Wars}} names a different page than {{Star Wars}}.
• Never write a Template: prefix. {{Template:Collapse}} looks up a page literally titled “Template:Collapse” — which doesn’t exist. Write {{Collapse}}.
• Subpages work: {{Star Wars/Nav}} includes the Nav subpage. For a title that contains a literal slash, escape it: {{TCP\/IP}}.

Showing a literal {{…}}

You can’t — almost. Template expansion runs before everything else, including <nowiki>, so <nowiki>{{Hello}}</nowiki> still includes the template. The working route is HTML entities for the braces:

{{Hello}}   →   {{Hello}}

A lone unmatched {{ (or an empty {{}}) renders literally with no escaping needed.

Built-in names

Three names are implemented by the engine itself and don’t correspond to template pages:

Stock templates

Every wiki ships a small set of maintained templates. On Wikiglide:

Limits and safety rails

The engine guards against runaway includes; each failure renders an inline error message instead of content:

• Depth — includes may nest 40 levels deep.
• Loops — a page including itself (directly or through a chain) stops at the loop.
• Total size — one page may pull in at most 2 MB of included source.

Editing template pages

Template pages are maintained by sysops — editing one silently changes every page that includes it, so the Template namespace is locked. Regular pages included via the fallback are ordinary pages anyone can edit.