npm - zuplo - Versions diffs - 7.12.6 → 7.13.1 - Mend

zuplo 7.12.6 → 7.13.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (580) hide show

package/docs/concepts/where-zuplo-runs.mdx ADDED Viewed

@@ -0,0 +1,124 @@
+---
+title: Where Zuplo Runs
+description:
+  Zuplo runs at the edge, on a dedicated instance in the cloud of your choice,
+  or on your own Kubernetes cluster, and connects to backends on any cloud or on
+  premises.
+applies_to:
+  product: gateway
+  hosting: all
+---
+Zuplo runs the same gateway in three places: at the edge, on a dedicated
+instance in the cloud you choose, or on your own infrastructure. Wherever the
+gateway runs, it can route to backends on AWS, Google Cloud, Azure, other
+providers, or your own data center. This page explains the hosting options and
+how Zuplo fits into a single-cloud, multi-cloud, or hybrid environment.
+## Hosting options
+| Option                                         | Where the gateway runs                                                                    | Choose it when you want                                                              |
+| ---------------------------------------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
+| [Managed Edge](../managed-edge/overview.md)    | Serverless, across 300+ data centers worldwide                                            | Global low latency and automatic scaling with no infrastructure to manage            |
+| [Managed Dedicated](../dedicated/overview.mdx) | An isolated instance that Zuplo operates on the cloud provider and regions you choose     | A specific cloud or region, private networking, or dedicated compliance requirements |
+| [Self-Hosted](../self-hosted/overview.md)      | Your Kubernetes cluster, in any cloud or private data center, installed with a Helm chart | Full control of the infrastructure that serves your API traffic                      |
+Managed Edge is the default for every Zuplo project. For a closer look at each
+option, see [Hosting Options](../articles/hosting-options.mdx).
+### Managed Edge
+Your gateway runs in hundreds of data centers worldwide, close to your clients.
+Each request reaches the nearest location, runs through your policies, and goes
+straight to your backend, wherever that backend runs. If one location has an
+issue, traffic routes to the next nearest location automatically.
+### Managed Dedicated
+Zuplo runs a dedicated, isolated instance of the gateway for you on the cloud
+provider of your choice:
+- [Akamai Connected Cloud](../dedicated/akamai/architecture.mdx)
+- [AWS](../dedicated/aws/architecture.mdx)
+- [Azure](../dedicated/azure/architecture.mdx)
+- [Google Cloud](../dedicated/gcp/architecture.mdx)
+- Equinix, TerraSwitch, and other providers on request
+You pick the regions, so you can keep traffic in a specific country or next to
+your backends. You can also deploy instances in multiple regions for high
+availability and disaster recovery.
+### Self-Hosted
+You install Zuplo on your own Kubernetes cluster with a single Helm chart. The
+cluster can run in any cloud or in a private data center. API traffic to your
+gateways stays on your infrastructure, while Zuplo provides the portal and a
+small set of supporting services.
+## One project, any hosting option
+All three hosting options use the same runtime, project format, policies, and
+deployment workflow. Your routes, policies, custom code, and environment
+variables live in your Git repository, not in a cloud-specific configuration.
+This gives you two advantages:
+- **No cloud lock-in.** Zuplo isn't tied to one cloud provider's gateway, so
+  your API layer stays the same when your backends change clouds.
+- **Room to grow.** A team can start on Managed Edge and move to Managed
+  Dedicated or Self-Hosted later, for example when a compliance requirement
+  appears, without rewriting the gateway.
+## Connecting to backends on any cloud
+The gateway location and the backend location are independent. A single Zuplo
+project can send one route to AWS Lambda, another to Google Cloud Run, and
+another to a service in your own data center, while clients see one API with one
+set of authentication, rate limits, and analytics.
+<Diagram height="h-96">
+  <DiagramNode id="clients">Clients</DiagramNode>
+  <DiagramNode id="zuplo" variant="zuplo">
+    Zuplo Gateway
+  </DiagramNode>
+  <DiagramNode id="aws" variant="orange">
+    AWS
+  </DiagramNode>
+  <DiagramNode id="gcp" variant="blue">
+    Google Cloud
+  </DiagramNode>
+  <DiagramNode id="azure" variant="blue">
+    Azure
+  </DiagramNode>
+  <DiagramNode id="onprem" variant="green">
+    On-premises data center
+  </DiagramNode>
+  <DiagramEdge from="clients" to="zuplo" />
+  <DiagramEdge from="zuplo" to="aws" />
+  <DiagramEdge from="zuplo" to="gcp" />
+  <DiagramEdge from="zuplo" to="azure" />
+  <DiagramEdge from="zuplo" to="onprem" />
+</Diagram>
+Pick the connection method that matches where each backend runs:
+| Backend                                          | How Zuplo connects                                                                                                                     |
+| ------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
+| Behind AWS, Azure, or Google Cloud IAM           | [IAM authentication](../articles/upstream-iam-auth.mdx) policies sign each request with credentials your cloud provider trusts         |
+| Any backend that can check a certificate         | [mTLS](../articles/securing-backend-mtls.mdx), so the gateway and backend authenticate each other                                      |
+| No public endpoint, bare metal, or on premises   | A [secure tunnel](../articles/secure-tunnel.mdx) that opens an outbound connection from your network, with no inbound firewall rules   |
+| In a private VPC or VNet, with Managed Dedicated | [Private networking](../dedicated/networking.mdx) such as AWS PrivateLink, Azure Private Link, or Google Cloud Private Service Connect |
+| Any backend that can check a header              | A [shared secret](../articles/securing-your-backend.mdx#shared-secret-or-api-key) that the gateway adds to each request                |
+IAM authentication, mTLS, and secure tunnels are available on enterprise plans.
+Because each route sets its own backend URL, you can move a service from one
+cloud to another, or from your data center to the cloud, by changing that URL.
+Clients keep calling the same API.
+## Related resources
+- [How Zuplo Works](./how-zuplo-works.mdx)
+- [Hosting Options](../articles/hosting-options.mdx)
+- [Securing your backend](../articles/securing-your-backend.mdx)
+- [Managed Dedicated architecture](../dedicated/architecture.mdx)

package/docs/dedicated/akamai/ai-powered-applications.mdx CHANGED Viewed

@@ -4,6 +4,9 @@ sidebar_label: AI-Powered Applications
 description:
   Reference architecture for secure, AI-powered applications on Akamai Connected
   Cloud with Zuplo AI Gateway, MCP servers, and Akamai AI Firewall.
+applies_to:
+  product: gateway
+  hosting: [managed-dedicated]
 ---
 This document describes a reference architecture for AI-powered applications

package/docs/dedicated/akamai/architecture.mdx CHANGED Viewed

@@ -3,6 +3,9 @@ title: Akamai Dedicated Architecture
 sidebar_label: Architecture
 description:
   Architecture overview for Zuplo Gateway deployments on Akamai Connected Cloud.
+applies_to:
+  product: gateway
+  hosting: [managed-dedicated]
 ---
 Zuplo integrates with Akamai Connected Cloud to provide a secure, highly
@@ -239,7 +242,7 @@ Zuplo and your backend services. For complete documentation, see
 | **Zuplo JWT Service**       | Issue signed JWTs that your backend validates using Zuplo's JWKS endpoint. Provides cryptographic proof that requests originate from your gateway. |
 | **mTLS (Mutual TLS)**       | Certificate-based authentication where both gateway and backend present certificates. Provides zero-trust security for enterprise requirements.    |
 | **Cloud Provider IAM**      | Use AWS IAM, GCP Identity-Aware Proxy, or Microsoft Entra ID to authorize requests. No credentials to manage - uses federated identity.            |
-| **Secure Tunnel (VPN)**     | WireGuard-based tunnel for backends that can't be exposed to the internet. Useful for on-premise or bare-metal deployments.                        |
+| **Secure Tunnel (VPN)**     | Secure tunnel for backends that can't be exposed to the internet. Useful for on-premise or bare-metal deployments.                                 |
 | **Private Network**         | VPC peering, PrivateLink, or Transit Gateway for private connectivity without traversing the public internet.                                      |
 ### Recommendations by backend location

package/docs/dedicated/akamai/caching.mdx CHANGED Viewed

@@ -5,6 +5,9 @@ description:
   Cache Zuplo responses at the Akamai edge with the CDN Cache Control policy.
   Covers Edge-Control TTLs, Edge-Cache-Tag purge tags, and the Property Manager
   settings that make them work.
+applies_to:
+  product: gateway
+  hosting: [managed-dedicated]
 ---
 An Akamai property in front of a Zuplo gateway can absorb most of the read

package/docs/dedicated/akamai/cdn.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: Setting up Akamai CDNs
 sidebar_label: CDN Setup
+applies_to:
+  product: [gateway, developer-portal]
+  hosting: managed-dedicated
 ---
 <!-- vale Vale.Spelling["Edgescape","Maxage"] = NO -->

package/docs/dedicated/architecture.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: "Managed Dedicated: Architecture"
 sidebar_label: Architecture
+applies_to:
+  product: gateway
+  hosting: [managed-dedicated]
 ---
 Zuplo's managed dedicated instances are highly available, scalable, and secure.
@@ -17,10 +20,11 @@ A managed dedicated instance of Zuplo consists of the following components:
   receives incoming requests, routes them to the appropriate backend, and
   returns the response to the client. The gateway handles authentication,
   authorization, rate limiting, and other features.
-- **Gateway Services**: Zuplo, being a highly distributed gateway, uses services
-  to facilitate features such as
+- **Gateway Services**: Zuplo-hosted services that power features such as
   [Rate Limiting](../getting-started/gateway/add-rate-limiting/index.mdx) and
-  [API Key Authentication](../articles/api-key-management.mdx).
+  [API Key Authentication](../articles/api-key-management.mdx). Every Zuplo
+  deployment, including managed dedicated instances, uses the same gateway
+  services.
 - **Control Plane**: The Control Plane manages the configuration of the Zuplo
   Gateway. It deploys new configurations, manages the lifecycle of the Zuplo
   Gateway, and monitors its health.
@@ -89,9 +93,6 @@ instance of Zuplo and how the components interact with each other.
     <DiagramNode id="gateway" variant="zuplo">
       Zuplo Gateway
     </DiagramNode>
-    <DiagramNode id="services" variant="zuplo">
-      Gateway Services
-    </DiagramNode>
   </DiagramGroup>
   <DiagramGroup id="customer-vpc" label="Customer Private Network">
     <DiagramNode id="backend">Backend</DiagramNode>
@@ -99,6 +100,9 @@ instance of Zuplo and how the components interact with each other.
   <DiagramNode id="control" variant="zuplo">
     Control Plane
   </DiagramNode>
+  <DiagramNode id="services" variant="zuplo">
+    Gateway Services
+  </DiagramNode>
   <DiagramEdge from="client" to="gateway" />
   <DiagramEdge from="gateway" to="backend" />
   <DiagramEdge from="gateway" to="services" fromSide="bottom" toSide="top" />

package/docs/dedicated/aws/architecture.mdx CHANGED Viewed

@@ -4,6 +4,9 @@ sidebar_label: Architecture
 description:
   How a Zuplo Managed Dedicated instance runs on AWS, and what you need to know
   to connect clients and backends to it.
+applies_to:
+  product: gateway
+  hosting: [managed-dedicated]
 ---
 A Managed Dedicated instance on AWS runs in its own VPC, in an AWS account that

package/docs/dedicated/aws/private-networking.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: "Managed Dedicated: AWS Private Networking"
 sidebar_label: Private Networking
+applies_to:
+  product: gateway
+  hosting: [managed-dedicated]
 ---
 Zuplo Managed Dedicated can run on AWS and connect privately to backends that

package/docs/dedicated/azure/architecture.mdx CHANGED Viewed

@@ -4,6 +4,9 @@ sidebar_label: Architecture
 description:
   How a Zuplo Managed Dedicated instance runs on Azure, and what you need to
   know to connect clients and backends to it.
+applies_to:
+  product: gateway
+  hosting: [managed-dedicated]
 ---
 A Managed Dedicated instance on Azure runs in its own virtual network (VNet), in

package/docs/dedicated/azure/private-networking.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: "Managed Dedicated: Azure Private Networking"
 sidebar_label: Private Networking
+applies_to:
+  product: gateway
+  hosting: [managed-dedicated]
 ---
 Zuplo Managed Dedicated can run on Azure and connect privately to backends that

package/docs/dedicated/configuration/host-header-override.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: "Managed Dedicated: Host Header Override"
 sidebar_label: Host Header Override
+applies_to:
+  product: gateway
+  hosting: [managed-dedicated]
 ---
 By default, the `Host` header your gateway sends to a backend is derived from

package/docs/dedicated/configuration/overview.mdx CHANGED Viewed

@@ -2,6 +2,9 @@
 title: "Managed Dedicated: Configuration"
 sidebar_label: Overview
 description: Settings in zuplo.jsonc that apply to Managed Dedicated projects.
+applies_to:
+  product: gateway
+  hosting: [managed-dedicated]
 ---
 Managed Dedicated projects use the same `zuplo.jsonc` file as every other Zuplo

package/docs/dedicated/custom-domains.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: "Managed Dedicated: Custom Domains"
 sidebar_label: Custom Domains
+applies_to:
+  product: gateway
+  hosting: [managed-dedicated]
 ---
 Configuration of custom domains with your managed dedicated instance of Zuplo

package/docs/dedicated/federated-gateways.mdx CHANGED Viewed

@@ -1,6 +1,10 @@
 ---
 title: "Managed Dedicated: Federated Gateways"
 sidebar_label: Federated Gateways
+applies_to:
+  product: gateway
+  hosting: [managed-dedicated]
+  plan: enterprise
 ---
 <EnterpriseFeature name="Federated Gateways" />

package/docs/dedicated/gcp/architecture.mdx CHANGED Viewed

@@ -4,6 +4,9 @@ sidebar_label: Architecture
 description:
   How a Zuplo Managed Dedicated instance runs on Google Cloud, and what you need
   to know to connect clients and backends to it.
+applies_to:
+  product: gateway
+  hosting: [managed-dedicated]
 ---
 A Managed Dedicated instance on Google Cloud runs in its own VPC network, in a

package/docs/dedicated/gcp/private-networking.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: "Managed Dedicated: GCP Private Networking"
 sidebar_label: Private Networking
+applies_to:
+  product: gateway
+  hosting: [managed-dedicated]
 ---
 Zuplo Managed Dedicated can run on Google Cloud and connect privately to

package/docs/dedicated/networking.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: "Managed Dedicated: Networking"
 sidebar_label: Networking
+applies_to:
+  product: gateway
+  hosting: [managed-dedicated]
 ---
 Your dedicated managed instance of Zuplo will be deployed to the cloud provider

package/docs/dedicated/overview.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: Zuplo Managed Dedicated
 sidebar_label: Overview
+applies_to:
+  product: gateway
+  hosting: [managed-dedicated]
 ---
 Zuplo Managed Dedicated is a deployment model where Zuplo runs one or more

package/docs/dedicated/source-control.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: "Managed Dedicated: Source Control"
 sidebar_label: "Source Control"
+applies_to:
+  product: gateway
+  hosting: [managed-dedicated]
 ---
 Zuplo supports GitOps workflows for managing your Zuplo Gateway configuration.

package/docs/dev-portal/auth-provider-api-identities.md CHANGED Viewed

@@ -6,6 +6,9 @@ description:
   Learn how to create a custom API identity plugin for the Dev Portal to
   authenticate API playground requests with OAuth JWT tokens or other custom
   credentials.
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 The Dev Portal API playground allows users to make authenticated requests to

package/docs/dev-portal/branding.mdx CHANGED Viewed

@@ -4,6 +4,9 @@ sidebar_label: Zuplo Branding
 description:
   Learn which plans show the "Powered by Zuplo" badge on the Developer Portal
   and how to remove it.
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 Developer Portals on Zuplo's self-serve plans display a "Powered by Zuplo"

package/docs/dev-portal/dev-portal-create-consumer-on-auth.mdx CHANGED Viewed

@@ -6,6 +6,9 @@ description:
   Learn how to automatically create an API Key Consumer for users upon login to
   your Developer Portal using Auth0 actions. This guide provides step-by-step
   instructions for integrating with the Dev Portal.
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 By default, users who log into your Zuplo powered Developer Portal won't have an

package/docs/dev-portal/documenting-mcp-servers.mdx CHANGED Viewed

@@ -5,6 +5,9 @@ navigation_icon: bot
 description:
   Use the x-mcp-server OpenAPI extension to render an MCP setup card in the Dev
   Portal for external or proxied MCP servers.
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 The Dev Portal renders a dedicated

package/docs/dev-portal/migration.mdx CHANGED Viewed

@@ -3,6 +3,15 @@ title: Dev Portal Migration Guide
 sidebar_label: Migration Guide
 description:
   Instruction for migrating from the legacy developer portal to Zudoku.
+applies_to:
+  product: developer-portal
+  hosting: all
+  differs:
+    managed-dedicated: >-
+      The in-browser **Migrate to Zudoku** button isn't available because
+      working copy environments aren't available. Use the CLI or manual
+      migration in [local development](../articles/local-development.mdx)
+      instead.
 ---
 This guide walks you through migrating your existing documentation from the

package/docs/dev-portal/node-modules.mdx CHANGED Viewed

@@ -2,6 +2,9 @@
 title: Node Modules & Customization
 description:
   Guide to installing custom node modules in Zuplo's developer portal.
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 The Dev Portal supports installing and using custom node modules in your

package/docs/dev-portal/overview.mdx CHANGED Viewed

@@ -4,6 +4,16 @@ sidebar_label: Overview
 description:
   Build and publish an API developer portal with interactive documentation,
   authentication, and API key self-service.
+applies_to:
+  product: developer-portal
+  hosting: all
+  differs:
+    managed-dedicated: >-
+      Zuplo hosts the Developer Portal the same way on every hosting option. If
+      you prefer, you can deploy it to your own infrastructure instead.
+    self-hosted: >-
+      Zuplo hosts the Developer Portal the same way on every hosting option. If
+      you prefer, you can deploy it to your own infrastructure instead.
 ---
 <span id="what-is-the-dev-portal" />

package/docs/dev-portal/server-side-rendering.mdx CHANGED Viewed

@@ -4,6 +4,10 @@ sidebar_icon: server-cog
 description:
   Run the Dev Portal on a server for each deployment so protected routes are
   enforced server-side.
+applies_to:
+  product: developer-portal
+  hosting: all
+  plan: enterprise
 ---
 <EnterpriseFeature name="Dev Portal Server-Side Rendering" />

package/docs/dev-portal/updating.mdx CHANGED Viewed

@@ -3,6 +3,9 @@ title: Updating Versions
 description:
   How to update Zuplo's developer portal to keep it up to date with the latest
   changes.
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 When developing your Dev Portal locally, you likely want to keep your version of

package/docs/dev-portal/zudoku/components/alert.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: Alert
 sidebar_icon: triangle-alert
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 import { Alert, AlertDescription, AlertTitle } from "zudoku/ui/Alert";

package/docs/dev-portal/zudoku/components/badge.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: Badge
 sidebar_icon: tag
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 A small badge component used to display status information or labels.

package/docs/dev-portal/zudoku/components/browser-window.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: Browser Window
 sidebar_icon: app-window
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 import { BrowserWindow } from "zudoku/components";

package/docs/dev-portal/zudoku/components/button.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: Button
 sidebar_icon: mouse-pointer-click
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 import { Button } from "zudoku/ui/Button";

package/docs/dev-portal/zudoku/components/callout.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: Callout
 sidebar_icon: circle-alert
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 import { Callout } from "zudoku/ui/Callout";

package/docs/dev-portal/zudoku/components/card.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: Card
 sidebar_icon: square
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 import {

package/docs/dev-portal/zudoku/components/checkbox.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: Checkbox
 sidebar_icon: check-square
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 import { Checkbox } from "zudoku/ui/Checkbox";

package/docs/dev-portal/zudoku/components/client-only.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: ClientOnly
 sidebar_icon: monitor
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 A component that only renders its children on the client-side, preventing hydration mismatches

package/docs/dev-portal/zudoku/components/code-tabs.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: CodeTabs
 sidebar_icon: columns-2
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 A tabbed code block component that groups multiple code blocks into a single unified view. Useful

package/docs/dev-portal/zudoku/components/dialog.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: Dialog
 sidebar_icon: rectangle-horizontal
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 import {

package/docs/dev-portal/zudoku/components/head.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: Head
 sidebar_icon: circle-fading-plus
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 The Head component allows you to manage document head elements like title, meta tags, and links from

package/docs/dev-portal/zudoku/components/icons.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: Icons
 sidebar_icon: flag
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 import { AtomIcon, PackagePlusIcon } from "zudoku/icons";

package/docs/dev-portal/zudoku/components/input.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: Input
 sidebar_icon: type
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 import { Input } from "zudoku/ui/Input";

package/docs/dev-portal/zudoku/components/label.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: Label
 sidebar_icon: tag
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 import { Label } from "zudoku/ui/Label";

package/docs/dev-portal/zudoku/components/landing-page.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: Landing Page
 sidebar_icon: layout-template
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 import { BrowserWindow, LandingPage } from "zudoku/components";

package/docs/dev-portal/zudoku/components/link.mdx CHANGED Viewed

@@ -1,6 +1,9 @@
 ---
 title: Link
 sidebar_icon: link
+applies_to:
+  product: developer-portal
+  hosting: all
 ---
 A navigation component that provides client-side routing capabilities for internal links and