Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.
Creating App Templates
A template must have the isTemplate system attribute in the <aura:component> tag set to true. This informs the framework to allow restricted items, such as <script> tags, which aren't allowed in regular components.
A component with the isTemplate system attribute set to true can’t be used on a site page. To use a component on a site page, the isTemplate system attribute can’t be set to true.
For example, a sample app has a np:template template that extends aura:template. np:template looks like:
Note how the component extends aura:template and sets the title attribute using aura:set.
The app points at the custom template by setting the template system attribute in <aura:application>.
A template can only extend a component or another template. A component or an application can't extend a template.