A special CMS hook called Tokenizing allows custom Global Modules to intercept tokens in markup and optionally replace them based on special logic before it is rendered to a web site visitor. Token strings take the format {% TOKENNAME } and by default can be placed inside:

Layout Masters and Templates
Content items
Custom Views
Snippet templates
User supplied values such as Values and Snippets

The CMS has built-in support for the following tokens:

Name	Format	Summary
GlobalValues	{% GlobalValues["GROUP"]["KEY"] }	Replaced with the Global Value value found at Site Settings > Global Values. GROUP - the Global Value group KEY - the value key under the Group
ItemField	{% ItemField["ITEMID"]["FIELD"] }	Replaced with the specified item's predefined field. If the item is not found, then an empty string is used as a replacement. ITEMID - the globally unique identifier for an item. FIELD - Either "Name" or "Url"
ItemSingleValue	{% ItemSingleValue["ITEMID"]["PATH"] }	Replaced with the value in a specified item found at a path. If the item or the value located at the path is not found, then an empty string is used as a replacement. ITEMID - the globally unique identifier for an item. PATH - the path of the value. Learn more about Values and Paths.
Item	{% Item["ITEMID"] }	Replaced with the specified item as rendered by its Module. The item's includes are registered. If the item is not found or inactive then an empty string is used as a replacement. ITEMID - the globally unique identifier for an item.
Module	{% Module["MODULEID"] }	Replaced with the specified module rendering. This only applies to Modules that are not item-based. MODULEID - the globally unique identifier for a module.

Custom Global Modules can be written to support additional tokens.

Support