2 ms·
If you are modifying HTML directly, no cache is involved. But if you are modifying something that is used to generate the HTML, what you deploy is a complete c
by chrismorgan 7y ago
If you are modifying HTML directly, no cache is involved.
But if you are modifying something that is used to generate the HTML, what you deploy is a complete cache of the operation of building the site. The fact that you could throw it away and build a new version is what makes it match the definition—just because no piece is colloquially known as a cache doesn’t stop it from being just that. Build artefacts are a cache of the operation of compiling the source.
To demonstrate this, putting the “requests” part into it: imagine hooking the static site generator up to the server directly, so that a request to /widgets.html turned into “run the static site generator, but only ask it for what it would output for /widgets.html, then respond with that”.
The terminology I used is quite correct and widespread in the industry at large—it’s just that it’s not at all in vogue in the JAMstack world.