The AMP templating system allows AMP elements to render dynamic content using templates defined within the AMP document. The data for templates is received from a CORS JSON endpoint.
The templates are defined using a templating language exported by an AMP templating extension. For example, "amp-mustache" templates are defined using Mustache.js syntax. However, any templating language has its syntax restricted and verified by the AMP validator to ensure that XSS and other issues cannot be dynamically injected into the AMP document.
Before AMP templates can be used, the templating system has to be declared in the document's head
:
<script async custom-template="amp-mustache" src="https://cdn.ampproject.org/v0/amp-mustache-0.1.js"></script>
The script
tag must be declared as async
and with the custom-template
attribute.
See the AMP Spec for more detail.
All AMP template implementations must go through the AMP security review before they can be submitted to the AMP repository.
Templates can be defined anywhere in the AMP document's body
, like this:
<template type="amp-mustache">
Hello {{world}}!
</template>
The type
attribute must reference the template's type as defined in the custom-template
attribute when the templating system was imported in the document's head
.
The use of the template is up to a specific AMP element that wants to use it. An AMP element would typically
look for a template within its children or using a template's ID. For instance, an amp-carousel
element
may (in the future) use a CORS endpoint and an AMP template to load and render a dynamic set of slides.
AMP elements can use templates.renderTemplate
methods to render a template. It is up to
a specific AMP element how templateElement
and data
are provided.
Here's a list of available extended templates:
Template | Description |
---|---|
amp-mustache |
Allows rendering of Mustache.js templates. |