Merge pull request #156 from wasmerio/ai/docs-context-update

feat: AI consistency update

Author: syrusakbary

pages/edge/_meta.json

@@ -3,7 +3,6 @@
   "guides": "Guides",
   "cli": "CLI",
   "learn": "Learn",
-  "integrations": "Integrations",
   "configuration": "App Configuration",
   "observability": "Observability",
   "architecture": "Architecture",

pages/edge/architecture.mdx

@@ -107,19 +107,20 @@ and long term low cost operations:
 
 ## Wasmer Edge Regions
 
-The closed beta will launch in a set of limited production regions for invited
-participants only, these locations are:
+Wasmer Edge is generally available in the following regions:
 
-- US West Coast
-- US East Coast
-- Europe Central
-- Asia
-- Australia
-- South America
+- `us-hillsboro` – US, Oregon
+- `us-ashburn` – US, Virginia
+- `us-losa1` – US, California
+- `de-falkenstein` – Europe, Germany
+- `be-mons1` – Europe, Belgium
+- `gb-lond1` – Europe, United Kingdom
+- `fr-pari1` – Europe, France
+- `sg-sing1` – Asia, Singapore
 
-Once the product transitions out of this beta phase then other hosting locations
-will be unlocked and made available to customers. Ultimately though users of Wasmer
-Edge that deploy stateless packages are abstracted from this and do not see it.
+As we monitor traffic patterns and demand, we may add or adjust regions over time.
+Ultimately, Wasmer Edge abstracts regions away for most stateless applications;
+the platform will route requests to the closest healthy region automatically.
 
 import CoreRegions from "@assets/deploy/architecture/core-regions.png";
 
@@ -189,9 +190,13 @@ Watch this space for further announcements on WASIX and other supporting ABI's a
 
 ## Wasmer Storage
 
-Persistent Storage will be released after the **Beta**, this will allow for databases,
-file systems and object storage to be compiled against WASM and run natively inside the
-Wasmer Edge platform. More details on this will be released later.
+Wasmer Edge provides persistent storage through **volumes**. Volumes are currently
+regional, meaning data is stored and accessed within a single Edge region. They are
+exposed as mounted directories inside your apps and can also be accessed remotely
+via an S3-compatible API and a built-in web UI.
+
+For details on capabilities, limitations, and usage (including backup and
+restoration policies), see the dedicated [Volumes documentation](/edge/learn/volumes).
 
 ## Wasmer Distributed Networking (DNET)
 
@@ -200,9 +205,9 @@ Every Edge Computing platform requires a network backbone as the foundation of
 the workloads it hosts, without one the use cases it can host are quite limited.
 Wasmer Edge uses a virtual networking overlay exposed directly to the WASIX sandbox.
 
-In the first beta release of Wasmer Edge you will see aspects of this distributed
-mesh network that allow for sockets and networking from workloads however its full
-potential will only become visible later as we unlock more core networking functionality.
+In early versions of Wasmer Edge you already see aspects of this distributed
+mesh network that allow for sockets and networking from workloads. Over time,
+we will continue to unlock more core networking functionality.
 
 Traffic is sent from browsers over websockets to enter the Wasmer Distributed
 Network while UDP encapsulated (and encrypted) packets are used to ship enternet

pages/edge/cli.mdx

@@ -208,7 +208,7 @@ wasmer app create
 ❯ Choose an existing package
 ```
 
-{/* [TODO]: Add link to templates list */}
+
 
 Templates allow users to kickstart their custom application from one of the
 available boilerplates like a static website, a PHP application, a JavaScript

pages/edge/guides/laravel.mdx

@@ -9,7 +9,7 @@ Getting an application running on Wasmer Edge is essentially working out how to
 Once packaged, it can be deployed to the [Wasmer Edge](https://wasmer.io/products/edge) platform.
 
 In this guide we'll learn how to deploy a Laravel application on Wasmer Edge.
-You can also set up a new app easily with the [Laravel template for Wasmer Edge](https://staging.wasmer.io/templates/laravel-starter).
+You can also set up a new app easily with one of the [Laravel templates on Wasmer](https://wasmer.io/templates).
 
 ### Prerequisites
 

pages/edge/guides/laravel/with-mysql.mdx

@@ -1,28 +1,8 @@
 For data store, why not start with a relational database classic: MySQL.
 
 You can set up a MySQL-compatible serverless database:
-* PlanetScale (Vitess)
 * TiDB Cloud - https://tidbcloud.com/
 
-
-## Laravel with MySQL-compatible PlanetScale
-
-For a basic PlanetScale and Wasmer Edge connection, follow [our guide here](/edge/integrations/planetscale).
-
-Once you're setup with PlanetScale, connect your Laravel application in Wasmer Edge through the following steps below:
-
-1. Get Laravel connection information from PlanetScale instance
-2. Connect from Laravel application in Wasmer Edge.
-
-Once initialized, your database dashboard should have metrics and options like so:
-
-1. Click on the Connect button at the top right, this should provide a box of information for connecting with your PlanetScale database.
-2. First though, make sure to add a password, by clicking on the “New Password” button at the upper right corner. This should show you a new password afterwards.
-3. Next, select “Laravel” in the list labeled “Connect with”
-
-Take note of the connection string provided and let’s move on!
-
-
 ## Laravel with MySQL-compatible TiDB
 
 You can also use TiDB in Wasmer Edge. TiDB is mostly MySQL-compatible (although it has some minor incompatiblities).

pages/edge/support.mdx

@@ -1,5 +1,11 @@
 # Wasmer Edge support channels
 
+If you need help with Wasmer Edge, you can reach us in the following ways:
+
+## Email support
+
+For direct support, including account, billing, or technical issues that aren't suitable for public discussion, contact us at **[email protected]**.
+
 ## Issues
 
 If you have concrete, actionable issues, please create a new issue in the [wasmer-edge-support repository](https://github.com/wasmerio/wasmer-edge-support).