docs: restructure documentation with proven hierarchy

- Rewrite landing page (remove "edge" claims, add value props)
- Add quickstart guide for onboarding
- Reorganize nav: Getting Started, Workers, Bindings, Examples, Reference, Deployment, Architecture
- Create examples index with 3 new examples (hello-world, form-handling, authentication)
- Merge environment-variables into bindings overview
- Expand custom-domains with SSL, apex domains, troubleshooting
- Add table of contents to runtime APIs
- Remove obsolete online-editor section

Author: max-lt

src/lib/docs-nav.ts

@@ -6,46 +6,61 @@ export interface NavItem {
 
 export const docsNav: NavItem[] = [
   {
-    name: 'Introduction',
+    name: 'Getting Started',
     path: '/docs',
     children: [
       { name: 'Overview', path: '/docs' },
-      { name: 'Runtime', path: '/docs/runtime' },
-      { name: 'Custom domains', path: '/docs/custom-domains' },
-      { name: 'Online editor', path: '/docs/online-editor' },
-      { name: 'Environment variables', path: '/docs/environment-variables' },
-      { name: 'Limits & Quotas', path: '/docs/limits' },
-      { name: 'Self-Hosting', path: '/docs/self-hosting' }
+      { name: 'Quick Start', path: '/docs/quickstart' }
+    ]
+  },
+  {
+    name: 'Workers',
+    path: '/docs/workers',
+    children: [
+      { name: 'HTTP Handlers', path: '/docs/workers/event-fetch' },
+      { name: 'Scheduled Tasks', path: '/docs/workers/scheduled-tasks' }
     ]
   },
   {
     name: 'Bindings',
     path: '/docs/bindings',
     children: [
       { name: 'Overview', path: '/docs/bindings' },
-      { name: 'Storage', path: '/docs/bindings/storage' },
       { name: 'KV', path: '/docs/bindings/kv' },
+      { name: 'Storage', path: '/docs/bindings/storage' },
       { name: 'Database', path: '/docs/bindings/database' }
     ]
   },
-  {
-    name: 'Workers',
-    path: '/docs/workers',
-    children: [
-      { name: 'Handle HTTP requests', path: '/docs/workers/event-fetch' },
-      { name: 'Scheduled tasks', path: '/docs/workers/scheduled-tasks' }
-    ]
-  },
   {
     name: 'Examples',
     path: '/docs/examples',
     children: [
+      { name: 'Overview', path: '/docs/examples' },
+      { name: 'Hello World', path: '/docs/examples/hello-world' },
       { name: 'JSON API', path: '/docs/examples/json-api' },
-      { name: 'Redirect Service', path: '/docs/examples/redirect' },
+      { name: 'Form Handling', path: '/docs/examples/form-handling' },
+      { name: 'Authentication', path: '/docs/examples/authentication' },
       { name: 'CORS Proxy', path: '/docs/examples/cors-proxy' },
+      { name: 'Redirect Service', path: '/docs/examples/redirect' },
       { name: 'Telegram Bot', path: '/docs/examples/telegram' },
       { name: 'S3 Proxy', path: '/docs/examples/s3-proxy' },
-      { name: 'S3 Proxy (AWS v4)', path: '/docs/examples/s3-proxy-aws-v4' }
+      { name: 'S3 Proxy (v4)', path: '/docs/examples/s3-proxy-aws-v4' }
+    ]
+  },
+  {
+    name: 'Reference',
+    path: '/docs/runtime',
+    children: [
+      { name: 'Runtime APIs', path: '/docs/runtime' },
+      { name: 'Limits', path: '/docs/limits' },
+      { name: 'Custom Domains', path: '/docs/custom-domains' }
+    ]
+  },
+  {
+    name: 'Deployment',
+    path: '/docs/self-hosting',
+    children: [
+      { name: 'Self-Hosting', path: '/docs/self-hosting' }
     ]
   },
   {

src/routes/docs/+page.md

@@ -1,63 +1,31 @@
-# About OpenWorkers
+# OpenWorkers
 
-OpenWorkers is a serverless runtime environment that allows you to run your code without having to worry about the underlying infrastructure.
+Serverless JavaScript runtime. Self-hosted, open source, Cloudflare Workers compatible.
 
-## Features
-
-- **Fast** - OpenWorkers is built on top of the javascript V8 engine.
-- **Secure** - Each worker runs in its own V8 isolate, which means that your code is isolated from other workers.
-- **Easy to use** - OpenWorkers is designed to be easy to use, so you can focus on writing your code while we take care of the rest.
-
-## Getting started
-
-To get started, you need to create an account. You can do this by clicking the "Sign in" button in the top right corner of the page.
-
-You will then be redirected to the sign in page. Sign in with your GitHub account.
-
-After logging in, you will be redirected to the dashboard. Here you can see all your workers and create new ones.
-
-### Creating a worker
-
-To create a worker, click the "Create a worker" button in the top right corner of the page.
-
-Here you can enter the name of the worker and select a language template.
-
-The name of the worker must be unique and can only contain letters, numbers and dashes, it will be deployed to `https://<worker-name>.workers.rocks`.
-
-### Editing a worker
-
-To edit a worker, click the "Edit" button in worker overview page.
-
-Here you can edit the code of the worker.
-
-The default returns a "Hello World" html page.
+## Quick Example
 
 ```typescript
-addEventListener('fetch', (event: FetchEvent) => {
-  event.respondWith(handleRequest(event.request).catch((err: Error) => new Response(err.stack, { status: 500 })));
-});
-
-// More examples available at: https://openworkers.com/docs
-async function handleRequest(request: Request): Promise<Response> {
-  const { pathname } = new URL(request.url);
-
-  // Return a 404 response for requests to /favicon.ico.
-  if (pathname.startsWith('/favicon.ico')) {
-    return new Response('Not found', { status: 404 });
+export default {
+  async fetch(request: Request, env: Env): Promise<Response> {
+    const data = await env.KV.get('config');
+    return Response.json({ data });
   }
+};
+```
 
-  // Return a JSON response for requests to /api containing the requested pathname.
-  if (pathname.startsWith('/api')) {
-    return new Response(JSON.stringify({ pathname }), {
-      headers: { 'Content-Type': 'application/json' }
-    });
-  }
+## What You Get
 
-  // Return a HTML response for all other requests.
-  return new Response('<h3>Hello world!</h3>', {
-    headers: { 'Content-Type': 'text/html' }
-  });
-}
-```
+- **V8 Isolates** — Millisecond cold starts, memory-safe sandboxing
+- **Standard APIs** — Fetch, Streams, Crypto, Web APIs you already know
+- **Bindings** — Connect to databases, storage, KV without exposing credentials
+- **TypeScript** — First-class support, no build step required
+
+## Next Steps
 
-From now on, you can edit the code of the worker and it will be automatically deployed.
+| | |
+|---|---|
+| [Quick Start](/docs/quickstart) | Deploy your first worker in 5 minutes |
+| [Workers](/docs/workers/event-fetch) | HTTP handlers and scheduled tasks |
+| [Bindings](/docs/bindings) | Storage, KV, Database connections |
+| [Runtime APIs](/docs/runtime) | Full API reference |
+| [Self-Hosting](/docs/self-hosting) | Run on your own infrastructure |

src/routes/docs/bindings/+page.md

@@ -4,16 +4,14 @@ Bindings connect your worker to external resources. They're injected via the `en
 
 ## Variables & Secrets
 
-Environment variables for configuration.
+Environment variables for configuration. Set them in the **Environments** tab of the dashboard.
 
 ```javascript
-const apiUrl = env.API_URL; // Variable (visible)
+const apiUrl = env.API_URL; // Variable (visible in logs)
 const apiKey = env.API_KEY; // Secret (hidden in logs)
 ```
 
-Configure in **Environments** in the dashboard.
-
-See [Environment Variables](/docs/environment-variables) for setup.
+**Variables** are visible in logs. **Secrets** are masked.
 
 ---
 

src/routes/docs/custom-domains/+page.md

@@ -1,9 +1,49 @@
-# Custom domains
+# Custom Domains
 
-You can add a custom domain to your worker in the "Domains" section of the worker overview page.
+Route your own domain to a worker.
 
-For example, for `example.com` to points to your worker, add `example.com` to the "Domains" section.
+## Setup
 
-Then, add a CNAME record to your DNS provider pointing to `workers.rocks`.
+1. Go to your worker's **Domains** tab
+2. Add your domain (e.g., `api.example.com`)
+3. Add a CNAME record at your DNS provider:
 
-Requests to `example.com` will now be routed to your worker.
+```
+api.example.com  CNAME  workers.rocks
+```
+
+4. Wait for DNS propagation (up to 24h, usually minutes)
+
+## SSL/TLS
+
+SSL certificates are provisioned automatically. Your domain will be accessible via HTTPS.
+
+## Apex Domains
+
+For apex domains (`example.com` without subdomain), use one of:
+
+- **ALIAS record** (if your DNS supports it)
+- **A record** pointing to our IP (contact support)
+- **Subdomain redirect** from `example.com` → `www.example.com`
+
+## Multiple Domains
+
+A worker can have multiple domains. All domains route to the same worker code.
+
+## Wildcard Domains
+
+Not currently supported. Create separate workers for each subdomain.
+
+## Troubleshooting
+
+**Domain not resolving:**
+- Verify CNAME is set correctly: `dig api.example.com CNAME`
+- DNS propagation can take time
+
+**SSL certificate error:**
+- New domains may take a few minutes for certificate provisioning
+- Ensure the domain resolves correctly first
+
+**404 on custom domain:**
+- Check the domain is added in the worker's Domains tab
+- Verify the worker is deployed and working on the default URL

src/routes/docs/environment-variables/+page.md

@@ -0,0 +1,27 @@
+# Examples
+
+Copy-paste examples to get started quickly. Each example is self-contained and ready to deploy.
+
+## Beginner
+
+| Example | Description |
+|---------|-------------|
+| [Hello World](/docs/examples/hello-world) | Minimal worker, routing basics |
+| [JSON API](/docs/examples/json-api) | REST endpoints, request/response handling |
+| [Form Handling](/docs/examples/form-handling) | Parse form data, file uploads |
+
+## Intermediate
+
+| Example | Description |
+|---------|-------------|
+| [Authentication](/docs/examples/authentication) | JWT validation, protected routes |
+| [CORS Proxy](/docs/examples/cors-proxy) | Proxy requests with CORS headers |
+| [Redirect Service](/docs/examples/redirect) | URL shortener with KV storage |
+
+## Advanced
+
+| Example | Description |
+|---------|-------------|
+| [Telegram Bot](/docs/examples/telegram) | Webhook handler for Telegram |
+| [S3 Proxy](/docs/examples/s3-proxy) | Stream files from S3 (v2 signing) |
+| [S3 Proxy (AWS v4)](/docs/examples/s3-proxy-aws-v4) | Stream files from S3 (v4 signing) |