Plan

The Plan component is used 75 times on 71 pages.

See all examples of pages that use Plan

Used 75 times.

Pages

/1.1.1.1/ - Source
/ai-crawl-control/features/manage-ai-crawlers/ - Source
/ai-crawl-control/ - Source
/ai-gateway/ - Source
/ai-search/ - Source
/ai/ - Source
/api-shield/ - Source
/api-shield/management-and-monitoring/endpoint-management/ - Source
/api-shield/security/schema-validation/ - Source
/argo-smart-routing/ - Source
/bots/ - Source
/browser-run/ - Source
/browser-run/pricing/ - Source
/byoip/ - Source
/cache/ - Source
/client-side-security/ - Source
/cloudflare-network-firewall/ - Source
/cloudflare-one/ - Source
/cloudflare-one/insights/logs/logpush/ - Source
/cloudflare-one/traffic-policies/packet-filtering/network-firewall-overview/ - Source
/containers/ - Source
/d1/ - Source
/data-localization/ - Source
/ddos-protection/ - Source
/dmarc-management/ - Source
/dns/dns-firewall/ - Source
/dns/ - Source
/dns/internal-dns/ - Source
/dns/private-origins/ - Source
/durable-objects/ - Source
/email-security/ - Source
/email-service/ - Source
/fundamentals/organizations/ - Source
/hyperdrive/ - Source
/images/ - Source
/kv/ - Source
/load-balancing/ - Source
/magic-transit/ - Source
/multi-cloud-networking/ - Source
/network-flow/ - Source
/network-interconnect/ - Source
/network/ - Source
/notifications/ - Source
/pages/ - Source
/pipelines/ - Source
/privacy-gateway/ - Source
/privacy-proxy/ - Source
/queues/ - Source
/radar/ - Source
/registrar/ - Source
/resource-tagging/ - Source
/rules/ - Source
/rules/trace-request/ - Source
/sandbox/ - Source
/secrets-store/ - Source
/spectrum/ - Source
/speed/ - Source
/ssl/ - Source
/tunnel/ - Source
/version-management/ - Source
/waf/ - Source
/waiting-room/ - Source
/warp-client/ - Source
/web-analytics/ - Source
/web3/ - Source
/workers-ai/ - Source
/workers-vpc/ - Source
/workflows/ - Source
/zaraz/ - Source
/zaraz/reference/settings/ - Source

Partials

src/content/partials/networking-services/cloudflare-wan/overview.mdx

The plan component lets you define what type of plan your product needs. There are two ways to use it: in the main Overview page of your product, or in a page where you need to talk about a specific feature with additional requirements.

In the Overview page, use <Plan type="<PLAN_TYPE>" /> To specify a special feature use <Plan id="<FIRST_PRODUCT>.<SECOND-PRODUCT>.properties.availability.summary" />. This component pulls information from the index.json file in src/content/plans/.

Refer to the examples below for more information.

import { Plan } from "~/components"

<Plan type="all" />
<Plan type="paid" />
<Plan type="pro" />
<Plan type="business" />
<Plan type="add-on" />
<Plan type="ent-add-on" />
<Plan type="workers-all" />
<Plan type="workers-paid" />
<Plan id="web3.ethereum.properties.availability.summary" />