Web development jargon: static files vs static content vs static websites vs react production build

What is the difference between static files and a static website? Are static files anything that is not an executable or are statics files files what make a static website? in other words can a website been made of static files be a dynamic website?

How can React be used to make dynamic websites if the production build is entirely made of statics files?

If I understand correctly a React app consist of static files including javascript files and also a React website can be dynamic, so it follows that a dynamic website can be made with static files? A website to be dynamic it should retrieve data from the server, if a react dynamic website is made of static files that retrieve data from a database in the server then BOTH static and dynamic websites are made of statics files.

The node.js files that interact with the database for example, this are the back end part of the website and they are also static files? So why is the notion of "static files" being used so broadly in web development when is redundant and not that useful.

Or could be that react is used only to make static websites and then you have to add the back end logic that is the "dynamic" part of the website, but the documentation clearly states that React can be used to create "any type of website".

There is not book or documentation that precisely define what static files are or what the difference between "static files" and "static files" is, what the two meanings of static files are. However it is a term used broadly.If you search for "static files definition" what you get is that "static content" (are this two the same?) is anything that is used to make static websites, but again how can react be used to make dynamic websites if is entirely made of static files?

Either "statics files" is a term being used to refer to two different things or the react documentation is incorrect.

What this "static" jargon really means?

Thanks for your help.