Rendering order and how to use the scratchpad

I have a question, regards to how to use the scratchpad.
If things are rendered in order, is it possible to fill up a Scratch variable from within a renderhook, and get the result in <head> ? I’ve not been able to pull it off yet, removing 99% of the usefulness of the scratchpad as far as I’m concerned.
This below fills up the variable

{{with .Attributes.loading}}
{{ Scracth.Add “eager_images_list” (slice `<link rel=“preload” as=“image” href=“{{$medium.RelPermalink}}” imagesrcset=“{{ $smallest.RelPermalink }} {{$smallest.Width}}w{{ range uniq (slice $very_small $small $smallmedium $medium $mediumlarge $large $img) }}, {{ .RelPermalink }} {{.Width}}w{{end}}” imagesizes=“(max-width: 400px) 100vw, {{if in .Attributes.class “center”}}(max-width: 604px)100vw, 70vw{{else}}50vw, 35vw{{end}}” crossorigin=anonymous>`)}}

But then the questions are: in the following template, is .Content evaluated before <head> ?

<!DOCTYPE html>
<html lang="{{ default site.Language.Lang site.LanguageCode  }}"><head>
{{ partial "docs/html-head-specific" . }} > **<------ here**
{{ partialCached "docs/html-head" . }}

I want to add to preload pictures that are not lazy-loaded (nearly all are). I know someone did it already but I understand nothing at all to his code so I must do it myself.

1 Like

I’ll try to find time to write a more complete response later, but:

  1. I use both .Store and .Scratch because neither alone achieves the desired result.
  2. You may have missed the ‘setup’ in baseof.html in

You might also want to look at @vassap 's research in

the LQIPs .Store is filled in the image partial and output in the ‘head’ partial:

which calls


And yeah the code needs to be refactored, badly, but as I keep saying: time…

So I was dead on the money on this, not a bad guess for an amateur :rofl:
But isn’t that weird to have to “assume” anything at all ? I know it’s not a characteristic of the hugo project, but it still boggles me. Why don’t developpers just document what they write when they write, when it should be the easiest ?

That is up to you.

What you need/want to do is something ala:

{{/* The partials below depends on scratch state set during content rendering, so make sure to trigger that first: *}}
{{ $tmp := .WordCount }}
{{ partial "docs/html-head-specific" . }}
{{ partialCached "docs/html-head" . }}
1 Like

Ah so the order can change !! Ok.
If only we state those choices clearly in a configuration file.
So calling upon .WordCount or anything using .Content is gonna make available, let’s say the product of render-hooks available before <body> ?

  1. I trigger rendering like this
  2. two: render-link.html fills up a Scratch variable
  3. I use .Scratch.Get in <head> ?

And it would produce a predictable result ?

  1. I may be misunderstanding, but I don’t see any ordering issue in the above example; the order top down within a given template is deterministic (top down).
  2. The ordering of of different pages is performed in parallel, so the order is random.
  3. We do, however, render the languages and output formats serialised, so one trick is, if you need to collect some stuff from the rendering step, to create a output format and set a weight to make sure it gets rendered last and then pick up your scratch state there.

And it is me who doesn’t understand you…
I only ever needed information from .Content within the same page, nothing fancy.
Up to now I could not do something as basic as those three steps I mentioned. In a live-reload environment, the content produced would depend on which page is reloaded last, making the feature unusable. Do you want a sample ?

Please refrain from these constant jibes; it is more than a little wearing.


  • For the same reasons plumbers don’t write what they work on then they work on it.
  • For open-source projects, documentation isn’t usually the enjoyable part
  • It’s a lot harder to document as you code than you think.
    • One does not typically code everything perfectly the first time, there is often experimentation and changes. Documenting that process would be like asking a novel writer to document how they were writing their novel.
    • At the very least it interrupts the creative process.
  • Often the first time one deals with documenting code is one is in school, and one loses marks for not having perfect documentation. It is off-putting rather than helpful.
  • Documentation quickly becomes stale and out of date, and it is a never-ending chore.
  • How well do you document your templates / code?
  • For non-open-source projects (where most developers spend most of their time) the emphasis from managers is not on documentation but on getting stuff ‘out-the-door’. In the corporate world there tends to be a lack of appreciation of the value of documentation, and that affects developer habits and what developers become used to having expected of them.
  • I could go on, but I think you get the point; there are in fact many reasons, and sniping about how things aren’t the way you think they should be, is at best irritating and shows your lack of awareness (of both the realities of developing, and social).
1 Like

You have to keep in mind, in a live reload environment, .Scratch is cleared as soon as a rebuild occurs. It only gets refilled if the pages are reprocessed, which only occurs for the changed pages. You will also need to use .Store (as I have) to keep track of what you need from pages that have no changes, and therefore for which no .Scratch information is generated on a particular live rebuild.

start/end of baseof, though I haven’t seen any difference with or without this initializing:

{{ .Page.Store.Set "all_sources" (slice (slice)) }}

in single.csv:
{{ with (.Page.Store.Get “all_sources”) }}{{ . }}{{end}}

inside render-link.html, if the link is remote:

{{ .Page.Store.Add "all_sources" (slice .Destination .Text)}}

It’s supposed to list all the page’s external link. It works with .Store, but rarely does it with .Scratch in livereload environments, and never in a production environment. In that last case, the csv file is always empty with .Scratch.

An exemple of current output:

[ egyptian scriptures the key role in the ageing process Then we develop a heightened healing factor As Hypocrate did not say (but thought nonetheless): Research shows primates to be very active during the night Burnt bones become fluorescent, and are very effective as a light in cellars. terribly addictive effect This article may point to an early, if short-lived, establishment of cooking and cereals]

ps: one long giant string, sigh… how can I set that up to get an object like this [[“url” “text”] [“url” “text”]] ? Ultimately I want something like:

{{ with (.Page.Store.Get "all_sources") }}{{ range .}}
Titre: {{ index . 0}}
URL: {{ index . 1}}
1 Like

Sorry, I have lost the plot on this part of it. Could you refresh me/us on what you mean by this (that is, what are you doing, what do you expect to happen, and what actually happens)? If possible, error messages, or the actual templates, and inputs, and resulting outputs (as much as you can reasonably capture and show us).

Also DM’d you, hope you don’t mind. Didn’t want to get even more off-topic.

post edited and clarified.