\n\ntl;dr - A hash of the contents of a file is included in the filename. A change in the content changes the filename. These files can be cached forever. This is awesome.
\n
There's a lot of great content on this topic already. Google has some great answers to this question.
\nJust for you. A very short summary. Hashing is a mathematical function. The hash function output is always the same size. A very small change in the input creates a large change in the output.
\nHere's a few md5 examples:
\nInput hello
5d41402abc4b2a76b9719d911017c592Input hello.
d94c10e437d18531e122ed0b45badd2aGatsby generates lots of static files. Those files have names. One part of the name is a hash. The hash is built from the contents of the file. A small change in the content of the file changes the hash.
\nNow every change creates a new filename. No matter how small the change. Each time the content changes, the file name changes. Every version of a file has its own unique name.
\nGreat. So what?
\nSo now your static files can be cached forever.
\nGatsby is all about speed. Insanely fast static sites. One part of insanely fast is caching. Cache as much as possible.
\nThe content hashing technique helps with caching. The contents of a file will never change. If the content changes, the name changes, so it's a new file. Now the static files can be cached indefinitely.
\nThat's really helpful. Why? Updating a cache is hard. It's much easier to push stuff into a cache and forget about it. It never changes. Every change creates a new file. Add files. Never delete. Easy.
\nAll of Gatsby's static files apply this technique. The .html pages do not. You need to be able to change the content of your site. So the .html pages must change over time. But otherwise, all other files can be cached forever.