Sometimes I see code examples and themes that use site.Params.heading instead of .Site.Params.Heading when accessing Site parameters. “site” seems benign, and will build locally when running hugo. But when I deploy to Netlify “site” always breaks. What is the purpose of site vs .Site - it seems to…

site is a global function. It allows to access the site variables without a page context. Pretty handy when needing site methods from within a partial to which no page context is available. I think site was introduced in Hugo 52 or 53 so better make sure the version your Netlify instance is using …

.Site vs site and failed Netlify builds

jmooring Split this topic April 9, 2024, 11:58pm 4

A post was split to a new topic: Site vs .Site vs $.Site

Topic		Replies	Views
Is it better to always write site.Params over .Site.Params or $.Site.Params? support	8	781	February 13, 2021
site.Params vs .Site.Params support	3	531	January 18, 2019
.Site vs $.Site vs site support	10	453	April 14, 2024
.Site vs site - any performance advantages of either? support	7	1071	April 10, 2024
.Site.Params not working at all, any suggestions? support	4	860	November 26, 2023

.Site vs site and failed Netlify builds

Related topics