hugo/docs/content/templates/template-debugging.md

title	description	godocref	date	publishdate	lastmod	categories	menu	weight	sections_weight	draft	aliases	toc
Template Debugging	You can use Go templates' `printf` function to debug your Hugo templates. These snippets provide a quick and easy visualization of the variables available to you in different contexts.	http://golang.org/pkg/fmt/	2017-02-01	2017-02-01	2017-02-01	templates	docs parent weight templates 180	180	180	false		false

Here are some snippets you can add to your template to answer some common questions.

These snippets use the printf function available in all Go templates. This function is an alias to the Go function, fmt.Printf.

What Variables are Available in this Context?

You can use the template syntax, $., to get the top-level template context from anywhere in your template. This will print out all the values under, .Site.

{{ printf "%#v" $.Site }}

This will print out the value of .Permalink:

{{ printf "%#v" .Permalink }}

This will print out a list of all the variables scoped to the current context (., aka "the dot").

{{ printf "%#v" . }}

When developing a homepage, what does one of the pages you're looping through look like?

{{ range .Data.Pages }}
    {{/* The context, ".", is now each one of the pages as it goes through the loop */}}
    {{ printf "%#v" . }}
{{ end }}

{{% note ".Data.Pages on the Homepage" %}} .Data.Pages on the homepage is equivalent to .Site.Pages. {{% /note %}}

Why Am I Showing No Defined Variables?

Check that you are passing variables in the partial function:

{{ partial "header" }}

This example will render the header partial, but the header partial will not have access to any contextual variables. You need to pass variables explicitly. For example, note the addition of "the dot".

{{ partial "header" . }}

The dot (.) is considered fundamental to understanding Hugo templating. For more information, see Introduction to Hugo Templating.