Loading...
Loading...
Access Project Properties
Various properties from the current environment can be used within templates but access must be granted through the setProps
command in the hooks.js file first.
With this in place, we gain access to the following within template files.
{{project.siteURL}}
String
{{project.mode}}
String
{{project.title}}
String
{{project.slogan}}
String
{{project.copyright}}
String
{{project.email}}
String
{{project.contactText}}
String
{{project.enableSocialTags}}
Boolean
{{project.language}}
String
{{project.logo.url}}
String
{{project.logo.alt}}
String
{{page.title}}
String
{{page.description}}
String
{{page.id}}
String
{{page.language}}
String
{{page.filename}}
String
{{page.ext}}
String
{{page.absolutePath}}
String
{{page.docRootPath}}
String
{{page.resourcesPath}}
String
{{node.id}}
String
{{node.parent.id}}
String
{{node.parent.container}}
String
{{node.title}}
String
{{element.group}}
String
{{element.title}}
String
{{element.version}}
String
{{element.assetPath}}
String
{{element.siteAssetPath}}
String
The following template example will output the page (and folder) details for all the pages in a project.
Before you can access the page properties you'll need to include the following code in the Hooks.js