docs(whp): add welcome + containerized hosting explainer

src/content/docs/whp/getting-started/welcome.mdx

@@ -0,0 +1,28 @@
+---
+title: Welcome to WHP
+description: Quick orientation for new customers — what WHP is and where to start.
+sidebar:
+  order: 1
+---
+
+Welcome aboard. WHP is the control panel you'll use to run your hosting with us — adding domains, creating sites, managing email, checking backups, and turning on optional add-ons. Every WHP account is its own isolated container, so what you do here only affects your stuff.
+
+## What to do first
+
+A typical first hour looks like this:
+
+- **[Add your domain](/whp/how-to/add-a-domain/)** — point a domain at your hosting, whether you registered it with us or somewhere else.
+- **[Create your first site](/whp/how-to/create-a-site/)** — PHP, Node, or static HTML; we provision the container in under a minute.
+- **[Set up email](/whp/how-to/create-an-email-account/)** — add a mailbox on your domain and wire up your email client.
+
+## Where to learn more
+
+- **[What is containerized hosting?](/whp/getting-started/what-is-containerized-hosting/)** — plain-language explainer of what makes this different from shared hosting or a VPS.
+- **[Service hostnames](/whp/reference/service-hostnames/)** — how to connect to MySQL, PostgreSQL, Redis, Memcached, and SMTP from inside your site.
+- **[Add-ons](/whp/add-ons/overview/)** — monitoring, archival email, resource upgrades, and more.
+
+## Getting help
+
+import Support from '~/content/partials/support-link.mdx';
+
+<Support />

src/content/docs/whp/getting-started/what-is-containerized-hosting.mdx

@@ -0,0 +1,40 @@
+---
+title: What is containerized hosting?
+description: Plain-language explainer of containerized hosting and how it compares to shared hosting and a VPS.
+sidebar:
+  order: 2
+---
+
+Containerized hosting means your site lives in its own lightweight, isolated environment — a "container" — on one of our servers. Your container is yours alone. Its CPU, memory, disk, and software versions don't depend on what other customers on the same machine are doing.
+
+## An analogy
+
+Think of a shared house with one kitchen versus an apartment building. **Shared hosting** is the house: lots of people share the same kitchen, and when one person leaves dishes in the sink, everyone notices. **Containerized hosting** gives you your own apartment, with your own kitchen, in the same building — you still benefit from the shared infrastructure (heat, security, plumbing), but day-to-day you're not stepping on anyone else's mess.
+
+## How it compares to shared hosting
+
+- **Predictable performance.** Another customer can't slow your site down by running a big import or sending a traffic spike. Your CPU and memory are yours.
+- **Pick your software versions.** PHP 8.3 or 8.4? Node 20 or 22? You choose at the site level. Different sites on the same account can use different versions.
+- **Isolation = security.** A vulnerability in another customer's site can't reach yours. There's a hard boundary between containers.
+- **Add resources without moving.** Need more RAM next month? Upgrade in place — no migration, no downtime.
+
+## How it compares to a VPS
+
+- **No server admin required.** We patch the underlying OS, monitor the host, and back up the underlying disk. You focus on your site, not on `apt update`.
+- **Right-sized resources.** A VPS gives you a whole virtual machine whether you need it or not. A container gives your site exactly the CPU, RAM, and disk you actually use — and you can resize whenever.
+- **Cheaper to run small.** Containers share the host efficiently, so you don't pay for an idle VM sitting at 5% CPU all day.
+
+## What it doesn't change
+
+- **SFTP still works** within the limits of your plan, so your usual file-upload workflow is unaffected.
+- **Your databases still live next to your site**, on the same host, with low-latency connections.
+- **Your domain works the same way** — DNS, SSL, redirects all behave like any other web host.
+
+## When you might want a VPS instead
+
+We'll be honest with you: if you need kernel-level tweaks, custom networking, non-standard runtimes we don't support, or root over SSH, a VPS may suit you better. Most sites don't need any of that — and the trade-off is that you're then responsible for your own OS upkeep.
+
+## Related
+
+- [Add-ons overview](/whp/add-ons/overview/)
+- [Service hostnames](/whp/reference/service-hostnames/)