I'm at my local public library which has wifi. It's also how I download new NPM modules, email my client, deliver my work to him, etc. But I do 90% of my work offline at home.
Are you a dev? If yes, how do you refer to documentation without internet??!!
I too am curious about the workflow.
Also, kind of off topic, but I found it fitting that your (original poster) website is hosted on AWS.
Aside from my other answer, the local library has internet access, so I'm able to use AWS as needed.
You'd be surprised how much documentation you can download. And the ones that are hosted on sites, those sites are often just git repos that you can clone. A few of them (like webpack.org) are trickier because you have to build the static site while online, but then you can run it offline (via python -m SimpleHTTPServer). There's tons of little tricks like this you can use to get documentation for pretty much anything you need. Not to mention Zeal (open source Dash clone) for tons of other things, Win32 API has a CHM file, and actual books at the library work great like for Python or C++, which often have the whole standard library in them, or at least most of it. And it's always a pleasant surprise when an NPM module bundled its thorough README.md file right into the package file (and often even more docs than that), and sometimes even the original source code, so that all I have to do is run `code node_modules/webpack-dev-server` and press Cmd-Shift-V (to preview .md file as Markdown in VS Code) and then it's as if I'm right there on their GitHub page. Also Safari has an amazingly useful feature of saving a page exactly as-is into a single file that can be opened in Safari, instead of saving all the external files into a sibling folder like Chrome does.