The comments on this Talk page may provide some additional useful insight into the high-level concepts that users find confusing or missing in our current documentation: https://wikitech.wikimedia.org/wiki/Help_talk:Toolforge/Quickstart#Critics_to_this_Quickstart_guide:

I navigated and read a lot of wiki pages and subpages about Toolforge, Kubernets, Toolforge/Web, Python (because I want to create Python-based tool), Version control, Gerrit, etc. And, as a result, all those peaces of information I read are now messed up in my head and I still don't know what to do to launch my first service, and what does that "webservice start" command do, and how is this Kubernets and Bastion are related to my new webservice, and what is a place that I get into, when I do SSH at "tools-login.toolforge.org" or "tools-dev.toolforge.org". And what is a difference between "tools-dev" and "tools-login" (this Q arises when you're reading Help:Access to Toolforge instances with PuTTY and WinSCP). And why " manage files in Toolforge" link tells how to "take ownership"? In my new service there's no files at all. And why have to do "become <tool>"? This "Quickstart" guide is fine, I passed all 6 steps, but what is next?

This user's comment indicates both: a need for improved tutorials / how-to guides (which is covered by other phabricator tasks), and a need to understand the general concepts of how Toolforge works, to clear up confusion about how Kubernetes and Bastion relate to their webservice, how file management works, what ownership means in the context of tool accounts, etc. etc. That is the focus of this task.

Note to self: after this is published, replace link here with one to the section about bastion hosts:

Log in to Toolforge

1. Use your SSH client to connect to Toolforge through a [[Help:Terminology#Bastion host|bastion host]]. <-- replace this link

Nice work! I made a few small edits. I also noticed a few places with "Note: ..." where it might be nice to use a callout template.