zuplo 7.8.7 → 7.8.8

package/docs/getting-started/dev-portal/local.mdx

@@ -0,0 +1,213 @@
+---
+category: Developer Portal
+showLastModified: false
+suggestEdit: false
+sidebar_label: Editor
+title: Getting Started with Developer Portal - Editor
+description:
+  Build a developer portal locally with API documentation, an introduction,
+  sign-in, and API key management, then test a protected route.
+---
+
+<WizardSteps build="dev-portal" method="local" />
+
+<MethodTabs build="dev-portal" method="local" />
+
+Build a developer portal with API reference documentation, a custom
+introduction, and API key management. You'll run it locally, sign in as an API
+consumer, and make an authenticated request from the API playground.
+
+## Prerequisites
+
+- [Node.js](https://nodejs.org/en/download) 24 or later and Git.
+- A [Zuplo account](https://portal.zuplo.com).
+- An editor and an email address you can use to sign in to the developer portal.
+
+## Create and customize the portal
+
+<Stepper>
+
+1. **Create a project**
+
+   Run:
+
+   ```bash
+   npx create-zuplo-api@latest my-api-project
+   cd my-api-project
+   npm run dev
+   ```
+
+   When prompted, choose **Yes** to create a matching Portal project, complete
+   sign-in, and select your Zuplo account. The CLI creates a hosted project and
+   links your local copy to it. Keep `.env.zuplo` out of source control.
+
+   The default template includes a Todo API and a developer portal. Open the
+   **Docs Server** URL printed in the terminal, normally
+   [http://localhost:9200](http://localhost:9200). You should see the Todo API
+   reference. The gateway runs on port `9000` and the Route Designer on `9100`.
+
+   :::tip{title="Use an existing project"}
+
+   If your project already has a `docs` directory, clone its Git repository, run
+   `npm install` at the project root, then run `npx zuplo login` and
+   `npx zuplo link`, selecting the project's **working copy**. This walkthrough
+   uses the Todo template; for your own API, apply the policy and tests to an
+   equivalent read-only route. Start all three services with `npm run dev` from
+   the project root. For an older project without `docs`, first follow
+   [Enable the Developer Portal](../../dev-portal/migration.mdx).
+
+   :::
+
+2. **Set your portal's title and introduction**
+
+   Open `docs/zudoku.config.tsx`. Set `site.title` and `metadata.title` to
+   `Todo Developer Portal`, and set `metadata.description` to
+   `Explore the Todo API and manage your API keys.` Keep the other settings.
+
+   The `apis` entry already reads `../config/routes.oas.json` and publishes it
+   at `/api`. Your API documentation updates when the OpenAPI file changes.
+
+   Replace `docs/pages/introduction.mdx` with:
+
+   ```mdx title="docs/pages/introduction.mdx"
+   ---
+   title: Welcome to the Todo API
+   description: Sign in, find your API key, and make your first request.
+   ---
+
+   Use the Todo API to retrieve tasks for your application.
+
+   1. Sign in using the email address registered as a key manager.
+   2. Open **API Keys** from your profile menu to find your assigned key.
+   3. Open **API Reference** and try **Get all todos** with that key.
+   ```
+
+   The default navigation already includes `introduction`. Open
+   `http://localhost:9200/introduction` to see the page. Changes appear as you
+   save. See [Writing content](../../dev-portal/zudoku/writing.mdx) for more
+   page options.
+
+3. **Require an API key for the sample route**
+
+   Replace the empty policy list with:
+
+   ```json title="config/policies.json"
+   {
+     "policies": [
+       {
+         "name": "api-key-auth",
+         "policyType": "api-key-inbound",
+         "handler": {
+           "export": "ApiKeyInboundPolicy",
+           "module": "$import(@zuplo/runtime)",
+           "options": { "allowUnauthenticatedRequests": false }
+         }
+       }
+     ]
+   }
+   ```
+
+   In `config/routes.oas.json`, find `paths["/todos"].get`. Update its
+   `x-zuplo-route` to retain the forward handler and add the policy:
+
+   ```json
+   "x-zuplo-route": {
+     "corsPolicy": "anything-goes",
+     "handler": {
+       "export": "urlForwardHandler",
+       "module": "$import(@zuplo/runtime)",
+       "options": { "baseUrl": "https://todo.zuplo.io" }
+     },
+     "policies": { "inbound": ["api-key-auth"] }
+   }
+   ```
+
+   If you're using an existing project, add the policy to its existing list and
+   put it first in this route's inbound chain. Leave the other routes and their
+   handlers in place.
+
+   `anything-goes` enables browser requests from the developer portal. For a
+   production API, configure [CORS](../../articles/cors.mdx) for your portal's
+   origin. This step protects `GET /todos`; apply authentication to other routes
+   before exposing private data through them.
+
+   Update `info.description` to say that `GET /todos` requires a bearer API key,
+   replacing the sample's statement that no authentication is required.
+
+   In a second terminal, run `curl -i http://localhost:9000/todos`. Expect
+   `401 Unauthorized`.
+
+</Stepper>
+
+## Assign an API key and test it
+
+<Stepper>
+
+1. **Create a consumer in the Portal**
+
+   Open your project in the Zuplo Portal and go to
+   [**Services → API Keys → Consumers**](https://portal.zuplo.com/+/account/project/services).
+   Select **Dev**, then click **Create Consumer**.
+
+   Set **Subject** to `tutorial-consumer`, add your email address under **Key
+   managers**, and leave **Metadata** as `{}`. Click **Save consumer**.
+
+   <ModalScreenshot>
+
+   ![Create an API consumer with a subject and key manager email](/media/api-key-consumer-bucket-portal-ui/create-consumer-modal.png)
+
+   </ModalScreenshot>
+
+   Key managers can view and manage this consumer's keys after signing in to the
+   developer portal. Signing in alone doesn't create a consumer. See
+   [API key management](../../articles/api-key-management.mdx).
+
+2. **Sign in to the developer portal**
+
+   Open `http://localhost:9200` and sign in with the same email address you
+   entered as a key manager. The template includes a demo sign-in provider and
+   `apiKeys: { enabled: true }` for this test.
+
+   Open your profile menu and select **API Keys**. The assigned consumer and its
+   key should appear. If they don't, check the email address and that you
+   created the consumer in **Dev** for the linked project.
+
+3. **Call the API from the documentation**
+
+   Open **API Reference**, select **Get all todos**, and click **Test**. Expand
+   **Authentication**, select `tutorial-consumer`, and click **Send**. Expect
+   `200 OK` and a JSON response containing todos.
+
+   You can also copy the key and verify it from a second terminal:
+
+   ```bash
+   export TODO_API_KEY="YOUR_API_KEY"
+   curl -i http://localhost:9000/todos \
+     -H "Authorization: Bearer $TODO_API_KEY"
+   ```
+
+   This request should return `200`; the same request without the header should
+   still return `401`.
+
+</Stepper>
+
+## Publish the portal
+
+Follow [Deploy to the edge](../gateway/deploy-to-the-edge/local.mdx) to connect
+your repository and deploy. In the Zuplo Portal, open **Deployment URLs** and
+copy the **Dev Portal** URL. The portal deploys with the gateway.
+
+Create a consumer in the deployed environment's **Prod** API key bucket and
+repeat the sign-in and API request there. Development keys are separate from
+production keys.
+
+Before inviting users or configuring a custom domain, replace the template's
+demo sign-in configuration with your own
+[authentication provider](../../dev-portal/zudoku/configuration/authentication.md).
+
+## Next steps
+
+- [Customize the theme](../../dev-portal/zudoku/customization/colors-theme.mdx).
+- [Create consumers on login](../../dev-portal/dev-portal-create-consumer-on-auth.mdx)
+  if every user should receive a key automatically.
+- [Add more documentation](../../dev-portal/zudoku/writing.mdx).

package/docs/getting-started/dev-portal/portal.mdx

@@ -0,0 +1,146 @@
+---
+category: Developer Portal
+showLastModified: false
+suggestEdit: false
+sidebar_label: Portal
+title: Getting Started with Developer Portal - Portal
+description:
+  Publish a developer portal in the Zuplo Portal, customize API documentation,
+  assign a consumer key, and test an authenticated request.
+---
+
+<WizardSteps build="dev-portal" method="portal" />
+
+<MethodTabs build="dev-portal" method="portal" />
+
+Publish API documentation and let developers manage their assigned API keys.
+You'll create a Todo API, customize its developer portal, and make an
+authenticated request from the portal's playground.
+
+## Prerequisites
+
+- A [Zuplo account](https://portal.zuplo.com).
+- An email address you can use to sign in to the developer portal.
+
+## Build and test your developer portal
+
+<Stepper>
+
+1. **Create a project and sample API**
+
+   Open [**Projects**](https://portal.zuplo.com/+/account/projects), click **New
+   Project**, and select **API & MCP Gateway**. Name it `my-dev-portal` and
+   click **Create Project**.
+
+   In **Code → config/routes.oas.json**, select **Start with Example API**, then
+   **Complete Import**. The Route Designer now lists the Todo API routes. Your
+   project also includes a `docs` directory for the developer portal.
+
+2. **Customize the portal**
+
+   In the **Code** file tree, open `docs/zudoku.config.tsx`. Set `site.title`
+   and `metadata.title` to `Todo Developer Portal`, and set
+   `metadata.description` to `Explore the Todo API and manage your API keys.`
+   Keep the other settings, including `apis`, `authentication`, and `apiKeys`.
+
+   The `apis` configuration reads `../config/routes.oas.json` and displays it at
+   `/api`. Editing your routes updates the API reference.
+
+   Open `docs/pages/introduction.mdx` and replace its contents with:
+
+   ```mdx title="docs/pages/introduction.mdx"
+   ---
+   title: Welcome to the Todo API
+   description: Sign in, find your API key, and make your first request.
+   ---
+
+   Use the Todo API to retrieve tasks for your application.
+
+   1. Sign in using the email address registered as a key manager.
+   2. Open **API Keys** from your profile menu to find your assigned key.
+   3. Open **API Reference** and try **List todos** with that key.
+   ```
+
+   Save the changes. The introduction already has a navigation entry. See
+   [Writing content](../../dev-portal/zudoku/writing.mdx) for more options.
+
+3. **Protect the sample route**
+
+   Open `config/routes.oas.json` in the **Route Designer** and select **List
+   todos** (`GET /todos`). Open **Policies → Add Policy**, search for **API Key
+   Authentication**, and accept its default configuration.
+
+   <ModalScreenshot>
+
+   ![Choose the API Key Authentication policy](/media/step-3-add-api-key-auth/choose-policy.png)
+
+   </ModalScreenshot>
+
+   Keep this policy first in the inbound policy chain. On the same route, open
+   **Deny All Origins (CORS)** and select **Allow All Origins** so the developer
+   portal can call it from the browser. Save your changes.
+
+   In the code view, add `info.description` to the OpenAPI file and set it to
+   `GET /todos requires a bearer API key.` Save again.
+
+   Click **Test** next to the route's path and send a request without a key.
+   Expect `401 Unauthorized`. This step protects `GET /todos`; apply
+   authentication to other routes before using them for private data.
+
+4. **Assign a key to a developer**
+
+   Open
+   [**Services → API Keys → Consumers**](https://portal.zuplo.com/+/account/project/services).
+   Select **Dev** and click **Create Consumer**. Set **Subject** to
+   `tutorial-consumer`, enter your email under **Key managers**, and leave
+   **Metadata** as `{}`. Click **Save consumer**.
+
+   <ModalScreenshot>
+
+   ![Create an API consumer and assign its key manager](/media/api-key-consumer-bucket-portal-ui/create-consumer-modal.png)
+
+   </ModalScreenshot>
+
+   A key manager can manage the consumer's keys after signing in. Signing in
+   doesn't create a consumer automatically. See
+   [API key management](../../articles/api-key-management.mdx).
+
+5. **Open and test the developer portal**
+
+   Open **Deployment URLs** and copy the **Dev Portal** URL for your working
+   copy. Open it in a new tab. Visit `/introduction` to check your new page.
+
+   Sign in using the same email address you entered under **Key managers**. The
+   template includes a demo sign-in provider for this tutorial. Open **API
+   Keys** from your profile menu and confirm your consumer's key appears.
+
+   Open **API Reference → List todos → Test**. Expand **Authentication**, select
+   `tutorial-consumer`, and click **Send**. Expect `200 OK` and todos in the
+   response. Select **None** under Authentication and send again: expect
+   `401 Unauthorized`.
+
+   If the key isn't listed, check the key manager email and that the consumer is
+   in the **Dev** bucket. If the browser reports a CORS error, check that this
+   route allows requests from the portal.
+
+6. **Deploy for other developers**
+
+   Follow [Deploy to the edge](../gateway/deploy-to-the-edge/index.mdx) to
+   connect your Git repository and deploy. Open **Deployment URLs** for the
+   production deployment and copy its **Dev Portal** URL.
+
+   Create a consumer in the **Prod** API key bucket and repeat the signed-in
+   request there. Dev and Production keys are separate.
+
+   Before inviting users, replace the demo login with your own
+   [authentication provider](../../dev-portal/zudoku/configuration/authentication.md)
+   and configure [CORS](../../articles/cors.mdx) to allow your portal's origin.
+
+</Stepper>
+
+## Next steps
+
+- [Customize the theme](../../dev-portal/zudoku/customization/colors-theme.mdx).
+- [Create consumers on login](../../dev-portal/dev-portal-create-consumer-on-auth.mdx)
+  if every signed-in user should receive a key automatically.
+- [Develop locally](./local.mdx) with live updates in your editor.

package/docs/{articles/step-3-add-api-key-auth.mdx → getting-started/gateway/add-api-key-auth/index.mdx}

@@ -1,11 +1,20 @@
 ---
-title: Step 3 - API Key Authentication
-sidebar_label: "3 - API Key Auth"
+category: API Management
+showLastModified: false
+suggestEdit: false
+title: Add API key authentication - Portal
+description:
+  Put API key authentication in front of your routes, issue a key to a consumer,
+  and reject calls that arrive without one in the Zuplo Portal.
 ---
 
+<WizardSteps build="gateway" method="portal" step="add-api-key-auth" />
+
+<MethodTabs build="gateway" method="portal" step="add-api-key-auth" />
+
 In this guide we'll add API Key authentication to a route. You can do this for
 any Zuplo project but will need a route, consider completing
-[Step 1](./step-1-setup-basic-gateway.mdx) first.
+[Step 1](../setup-a-basic-gateway/index.mdx) first.
 
 API Key authentication is one of our most popular **policies** as implementing
 this authentication method is considered one of the easiest to use by developers
@@ -14,10 +23,10 @@ other authentication methods.
 
 :::info{title="What's a Policy?"}
 
-[Policies](./policies.mdx) are modules that can intercept and transform an
-incoming request or outgoing response. Zuplo offers a wide range of policies
-built-in (including API key authentication) to save you time. You can check out
-[the full list](./policies.mdx).
+[Policies](../../../articles/policies.mdx) are modules that can intercept and
+transform an incoming request or outgoing response. Zuplo offers a wide range of
+policies built-in (including API key authentication) to save you time. You can
+check out [the full list](../../../articles/policies.mdx).
 
 :::
 
@@ -31,26 +40,26 @@ Let's get started.
    `routes.oas.json`) and open the **Policies** section. Then click **Add
    Policy**.
 
-   ![Add Policy](../../public/media/step-3-add-api-key-auth/image.png)
+   ![Add Policy](../../../../public/media/step-3-add-api-key-auth/image.png)
 
    Search for the API key authentication policy, click on it, and then click OK
    to accept the default policy JSON.
 
    <ModalScreenshot>
 
-   ![Add API Key Authentication](../../public/media/step-3-add-api-key-auth/choose-policy.png)
+   ![Add API Key Authentication](../../../../public/media/step-3-add-api-key-auth/choose-policy.png)
 
    </ModalScreenshot>
 
    :::tip
 
    The API key authentication policy should usually be one of the first policies
-   executed. If you came here from [Step 2](./step-2-add-rate-limiting.mdx) then
+   executed. If you came here from [Step 2](../add-rate-limiting/index.mdx) then
    you will want to drag it above the rate limiting policy.
 
    :::
 
-   ![reorder policies](../../public/media/step-3-add-api-key-auth/image-1.gif)
+   ![reorder policies](../../../../public/media/step-3-add-api-key-auth/image-1.gif)
 
    If you test your route, you should get a 401 Unauthorized response
 
@@ -68,11 +77,11 @@ Let's get started.
    [**Services**](https://portal.zuplo.com/+/account/project/services) tab in
    your project, then select **API Keys → Consumers** in the sidebar.
 
-   ![The API Keys → Consumers page in the Services section](../../public/media/step-3-add-api-key-auth/image-2.png)
+   ![The API Keys → Consumers page in the Services section](../../../../public/media/step-3-add-api-key-auth/image-2.png)
 
    Then click **Create Consumer**.
 
-   ![Create Consumer](../../public/media/step-2-add-api-key-auth/image-8.png)
+   ![Create Consumer](../../../../public/media/step-2-add-api-key-auth/image-8.png)
 
    Let's break down the configuration needed.
    - Subject: Also known as `sub`. This is a unique identifier of the API
@@ -90,7 +99,7 @@ Let's get started.
 
    <ModalScreenshot>
 
-   ![New Consumer](../../public/media/step-3-add-api-key-auth/image-3.png)
+   ![New Consumer](../../../../public/media/step-3-add-api-key-auth/image-3.png)
 
    </ModalScreenshot>
 
@@ -99,7 +108,7 @@ Let's get started.
    After your API Key consumer is created, copy your new API Key by clicking the
    copy button (next to the eye icon).
 
-   ![Copy Key](../../public/media/step-3-add-api-key-auth/image-4.png)
+   ![Copy Key](../../../../public/media/step-3-add-api-key-auth/image-4.png)
 
 4. Test out your API Key
 
@@ -108,7 +117,7 @@ Let's get started.
 
    <ModalScreenshot>
 
-   ![Failed unauthorized error](../../public/media/step-3-add-api-key-auth/test-policy.png)
+   ![Failed unauthorized error](../../../../public/media/step-3-add-api-key-auth/test-policy.png)
 
    </ModalScreenshot>
 
@@ -121,7 +130,7 @@ Let's get started.
 
    <ModalScreenshot>
 
-   ![successful response](../../public/media/step-3-add-api-key-auth/image-6.png)
+   ![successful response](../../../../public/media/step-3-add-api-key-auth/image-6.png)
 
    </ModalScreenshot>
 
@@ -130,7 +139,7 @@ Let's get started.
    We also offer an API for our API key service that allows you to
    programmatically create consumers and even create your own developer portal
    or integrate key management into your existing dashboard. See
-   [this document for details](./api-key-api.mdx).
+   [this document for details](../../../articles/api-key-api.mdx).
 
    :::
 
@@ -138,17 +147,17 @@ Let's get started.
 
    Whenever you deploy a new endpoint on Zuplo, it will automatically be added
    to your
-   [autogenerated developer documentation portal](../dev-portal/overview.mdx).
+   [autogenerated developer documentation portal](../../../dev-portal/overview.mdx).
 
    To access your API's developer portal, click the **Gateway deployed** button
    in your toolbar and click the link under Developer Portal.
-   ![Developer portal menu](../../public/media/step-2-add-rate-limiting/image-5.png)
+   ![Developer portal menu](../../../../public/media/step-2-add-rate-limiting/image-5.png)
 
    When you use certain policies like API keys, Zuplo will document properties
    like headers associated with that policy. As you can see on the right, the
    API key policy's `Authorization` header has been documented for you.
 
-   ![Developer Portal Endpoint](../../public/media/step-3-add-api-key-auth/image-7.png)
+   ![Developer Portal Endpoint](../../../../public/media/step-3-add-api-key-auth/image-7.png)
 
    Additionally, a new Authentication section has been added to your developer
    portal. Users of your API can sign in, view & manage their API keys, test
@@ -157,6 +166,3 @@ Let's get started.
    [our developer portal auth docs](/docs/dev-portal/zudoku/configuration/authentication).
 
 </Stepper>
-
-**NEXT** Try
-[Step 4 - Connect Source Control and Deploy to the Edge](./step-4-deploying-to-the-edge.mdx).

package/docs/{articles/step-3-add-api-key-auth-local.mdx → getting-started/gateway/add-api-key-auth/local.mdx}

@@ -1,11 +1,20 @@
 ---
-title: Step 3 - API Key Authentication
-sidebar_label: "3 - API Key Auth"
+category: API Management
+showLastModified: false
+suggestEdit: false
+title: Add API key authentication - Editor
+description:
+  Put API key authentication in front of your routes, issue a key to a consumer,
+  and reject calls that arrive without one with the Zuplo CLI and your editor.
 ---
 
+<WizardSteps build="gateway" method="local" step="add-api-key-auth" />
+
+<MethodTabs build="gateway" method="local" step="add-api-key-auth" />
+
 In this guide we'll add API Key authentication to a route. You can do this for
 any Zuplo project but will need a route, consider completing
-[Step 1](./step-1-setup-basic-gateway-local.mdx) first.
+[Step 1](../setup-a-basic-gateway/local.mdx) first.
 
 API Key authentication is one of our most popular **policies** as implementing
 this authentication method is considered one of the easiest to use by developers
@@ -14,10 +23,10 @@ other authentication methods.
 
 :::info{title="What's a Policy?"}
 
-[Policies](./policies.mdx) are modules that can intercept and transform an
-incoming request or outgoing response. Zuplo offers a wide range of policies
-built-in (including API key authentication) to save you time. You can check out
-[the full list](./policies.mdx).
+[Policies](../../../articles/policies.mdx) are modules that can intercept and
+transform an incoming request or outgoing response. Zuplo offers a wide range of
+policies built-in (including API key authentication) to save you time. You can
+check out [the full list](../../../articles/policies.mdx).
 
 :::
 
@@ -36,7 +45,7 @@ Let's get started.
 
    <BrowserScreenshot url="http://localhost:9100/?path=routes.oas.json">
 
-   ![Add Policy](../../public/media/step-3-add-api-key-auth-local/image.png)
+   ![Add Policy](../../../../public/media/step-3-add-api-key-auth-local/image.png)
 
    </BrowserScreenshot>
 
@@ -45,20 +54,19 @@ Let's get started.
 
    <ModalScreenshot>
 
-   ![Add API Key Authentication](../../public/media/step-3-add-api-key-auth/choose-policy.png)
+   ![Add API Key Authentication](../../../../public/media/step-3-add-api-key-auth/choose-policy.png)
 
    </ModalScreenshot>
 
    :::tip
 
    The API key authentication policy should usually be one of the first policies
-   executed. If you came here from
-   [Step 2](./step-2-add-rate-limiting-local.mdx) then you will want to drag it
-   above the rate limiting policy.
+   executed. If you came here from [Step 2](../add-rate-limiting/local.mdx) then
+   you will want to drag it above the rate limiting policy.
 
    :::
 
-   ![reorder policies](../../public/media/step-3-add-api-key-auth/image-1.gif)
+   ![reorder policies](../../../../public/media/step-3-add-api-key-auth/image-1.gif)
 
    If you test your route, you should get a 401 Unauthorized response
 
@@ -87,11 +95,11 @@ Let's get started.
 
    :::
 
-   ![The API Keys → Consumers page in the Services section](../../public/media/step-3-add-api-key-auth/image-2.png)
+   ![The API Keys → Consumers page in the Services section](../../../../public/media/step-3-add-api-key-auth/image-2.png)
 
    Then click **Create Consumer**.
 
-   ![Create Consumer](../../public/media/step-2-add-api-key-auth/image-8.png)
+   ![Create Consumer](../../../../public/media/step-2-add-api-key-auth/image-8.png)
 
    Let's break down the configuration needed.
    - Subject: Also known as `sub`. This is a unique identifier of the API
@@ -109,7 +117,7 @@ Let's get started.
 
    <ModalScreenshot>
 
-   ![New Consumer](../../public/media/step-3-add-api-key-auth/image-3.png)
+   ![New Consumer](../../../../public/media/step-3-add-api-key-auth/image-3.png)
 
    </ModalScreenshot>
 
@@ -118,7 +126,7 @@ Let's get started.
    After your API Key consumer is created, copy your new API Key by clicking the
    copy button (next to the eye icon).
 
-   ![Copy Key](../../public/media/step-3-add-api-key-auth/image-4.png)
+   ![Copy Key](../../../../public/media/step-3-add-api-key-auth/image-4.png)
 
 1. Test out your API Key
 
@@ -141,11 +149,8 @@ Let's get started.
    We also offer an API for our API key service that allows you to
    programmatically create consumers and even create your own developer portal
    or integrate key management into your existing dashboard. See
-   [this document for details](./api-key-api.mdx).
+   [this document for details](../../../articles/api-key-api.mdx).
 
    :::
 
 </Stepper>
-
-**NEXT** Try
-[Step 4 - Deploy to the Edge](./step-4-deploying-to-the-edge-local.mdx).