When a template is created within Confluence, variables are created by getting nested inside the @ symbols. It then spots the variables and replaces them as appropriate. However, it runs into several serious problems when you attempt to make a template that's anything more than cut-and-dried.

The following commands (and more) run into trouble when used with a variable

Inline Pictures
-The picture will be displayed, but only if the variable is set in another location. There's no way to display a specific picture without a dummy spot to load the variable, which clutters the page space
Ex:
Unable to render embedded object: File (@MyPict@) not found.
won't work until you also have
@MyPict@ somewhere else on the page

Mailto:
Ex:
@CustEmail@ Displays a nasty line of confusing entry boxes which cannot be filled by a user. This confuses users who are filling in the template.
Once again, the use of a dummy location to fill in the data solves the problem, but creates clutter on the page.

Links
Ex:
Associated with Project: [@ProductName@|@ProductPage@|The @ProductName@ Page]
Confluence is smart enough to catch the @ProductName@ variable, but misses the other two entirely, creating an error. Once again, a series of dummy locations to fill in the data would work, but would add to page clutter and be extremely undesirable.

A system needs to be in place whereby a user only has to fill in the appropriate variables and upload the needed files for a page to be properly created. When Confluence reads through a template and fails to catch variables within the markup, it creates headaches for web developers and end users.