Repository: sling-site Updated Branches: refs/heads/master 5abce2030 -> 4109671d3
Document the page variables Project: http://git-wip-us.apache.org/repos/asf/sling-site/repo Commit: http://git-wip-us.apache.org/repos/asf/sling-site/commit/4109671d Tree: http://git-wip-us.apache.org/repos/asf/sling-site/tree/4109671d Diff: http://git-wip-us.apache.org/repos/asf/sling-site/diff/4109671d Branch: refs/heads/master Commit: 4109671d3ba72c431f6494ec016699de179c4918 Parents: 5abce20 Author: Bertrand Delacretaz <bdelacre...@apache.org> Authored: Tue Oct 3 13:22:33 2017 +0200 Committer: Bertrand Delacretaz <bdelacre...@apache.org> Committed: Tue Oct 3 13:22:33 2017 +0200 ---------------------------------------------------------------------- README.md | 7 +++++++ 1 file changed, 7 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/sling-site/blob/4109671d/README.md ---------------------------------------------------------------------- diff --git a/README.md b/README.md index b55057a..00fbf76 100644 --- a/README.md +++ b/README.md @@ -35,6 +35,13 @@ The ASF's gitpubsub mechanism then synchronizes that content to http://sling.apa It would be nice to automate this in a Jenkins build...patches welcome! +## Variables in page content +Adding `expandVariables=true` to a page's front matter enables simple variables replacement, see the `pageVariables` map in +templates code for which variables are supported or to add more variables. A pattern like `${sling_tagline}` in page content +is replaced by the `sling_tagline` variable if it exists, otherwise a MISSING_PAGE_VARIABLE marker is output. + +Please use a `sling.` prefix for new site-related variables in `jbake.properties`, to differentiate from JBake built-in variables. + ## TODO Here's a rough list of things that need to be done after the 2017 migration to gitpubsub.
