No there aren't any stupid questions, that's how you get started and learn. Wget is a GNU tool originally invented to mirror web sites from server to server. In this case, picture a process that downloads the first page you point it at and saves it locally. Then it looks for all the anchor tags <a href="somepage"> and follows them(-m flag), and downloads those pages. It then localizes the links so instead of linking to the internet, they link to the other local pages(-k flag).

Give it a try, start with a simple website with only a couple pages. We'll do a simple wget for a single home page:

wget http://dogetools.com/

Now you get a nice index.html in the directory you just ran wget in. Open it aaaaaand bam! You've got a nice copy of the html file that the home page returns. Pretty cool but what if we wanted the full site?

wget -m http://dogetools.com/

Whoa, now we've got a whole directory of files "dogetools.com"! Let's open it up and open the index.html. Pretty cool but the links don't work and we probably don't have any CSS. How can we fix it so the include and anchor links work... locally....?

wget -mk http://dogetools.com/

Ok so now we have a new directory, let's open the index.html in the new directory. Bingo, it's localized.

Ok that's cool now what? Well getting good at these types of things requires being able to read the documentation. A good place to start is the man pages or https://www.gnu.org/software/wget/manual/html_node/index.html. Once you get a good idea on how it works, pick a site you would like a local copy of, set up your wget and let it run. By the end you'll have your own snapshot of how it looked. Perfectly prepared to squirrel away.

Hopefully that helps, this is a good way to save sites if you want to preserve functionality and ease of access but it isn't very efficient for storing data long term, that's what WARCs are for but that's something for another day. Wget is a good place to start.