You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Hugo contains an internal template for Google Analytics (added in October, 2015), the existence (in the Hugo docs) of a special partial file for Google Analytics (added in May, 2014) seems redundant—or, basically so. It almost exactly duplicates Hugo's internal template, with two differences:
The Google Analytics tracking code is hard-coded; and
The third argument (to script ga in the template) is spf13.com.
The tracking code could be moved to the Hugo docs' config file by adding to it the usual googleAnalytics variable.
The third argument has remained unchanged from its original value of spf13.com set in November, 2013, despite the fact that in September, 2014 the Hugo docs moved (from http://hugo.spf13.com to http://gohugo.io). BTW, a search confirmed that Google Analytics generally works on Github Pages.
If the third argument is best kept as it is (or changed to auto), then its configurability (in a new variable in config.toml if different from baseurl), since useful to the Hugo docs, presumably also would be useful to some of Hugo's users on their own sites.
If the third argument is best changed to gohugo.io then, for the Hugo docs, the present default value as calculated in Hugo's internal Google analytics partial (i.e., the value of baseurl) would work.
Since Hugo contains an internal template for Google Analytics (added in October, 2015), the existence (in the Hugo docs) of a special partial file for Google Analytics (added in May, 2014) seems redundant—or, basically so. It almost exactly duplicates Hugo's internal template, with two differences:
ga
in the template) isspf13.com
.The tracking code could be moved to the Hugo docs' config file by adding to it the usual
googleAnalytics
variable.The third argument has remained unchanged from its original value of
spf13.com
set in November, 2013, despite the fact that in September, 2014 the Hugo docs moved (fromhttp://hugo.spf13.com
tohttp://gohugo.io
). BTW, a search confirmed that Google Analytics generally works on Github Pages.If the third argument is best kept as it is (or changed to
auto
), then its configurability (in a new variable inconfig.toml
if different frombaseurl
), since useful to the Hugo docs, presumably also would be useful to some of Hugo's users on their own sites.If the third argument is best changed to
gohugo.io
then, for the Hugo docs, the present default value as calculated in Hugo's internal Google analytics partial (i.e., the value ofbaseurl
) would work.Then, seemingly, either way would enable Hugo to:
layouts/partials/analytics.html
; andJust to confirm, should the third argument indeed be
spf13.com
? or should it change togohugo.io
?If a new, "
ga
third argument" configuration variable is desirable, what should its name be?The text was updated successfully, but these errors were encountered: