Merge branch 'main' into MV-8611

Author: nirmitpatel

.gitignore

@@ -25,3 +25,8 @@ some_file
 
 # NPM build files for /site since yarn is being used
 site/package-lock.json
+
+# Ignore vim files
+*.swp
+*.swo
+~*

site/docs/messaging/campaign-management/csp/campaign-api.mdx

@@ -800,7 +800,7 @@ Location: https://dashboard.bandwidth.com/api/accounts/{accountId}/campaignManag
 ## Update Campaign TN Relationship
 
 ### Assumption
-This endpoint assumes that TN(s) have already been ordered or ported into our system. For more info, please see [our number ordering](/docs/numbers/guides/searchingForNumbers/) or [number porting](/docs/numbers/guides/porting/portingNumbers/) guides.
+This endpoint assumes that TN(s) have already been ordered or ported into our system. For more info, please see [our number ordering](/docs/numbers/guides/searchingForNumbers/) or [number porting](/docs/numbers/porting/port-ins/) guides.
 
 ### Request URL
 <Highlight color="#079CEE">POST</Highlight> <code>https://dashboard.bandwidth.com/api/accounts/{accountId}/tnoptions</code>

site/docs/messaging/campaign-management/imports/imports-api.mdx

@@ -294,7 +294,7 @@ Location: https://dashboard.bandwidth.com/api/accounts/{accountId}/campaignManag
 ## Update Campaign TN Relationship
 
 ### Assumption
-This endpoint assumes that TN(s) have already been ordered or ported into our system. For more info, please see [our number ordering](/docs/numbers/guides/searchingForNumbers/) or [number porting](/docs/numbers/guides/porting/portingNumbers/) guides.
+This endpoint assumes that TN(s) have already been ordered or ported into our system. For more info, please see [our number ordering](/docs/numbers/guides/searchingForNumbers/) or [number porting](/docs/numbers/porting/port-ins/) guides.
 
 #### Request URL
 <Highlight color="#079CEE">POST</Highlight> <code>https://dashboard.bandwidth.com/api/accounts/{accountId}/tnoptions</code>

site/docs/numbers/porting/about.mdx

@@ -0,0 +1,51 @@
+---
+id: about
+title: Porting
+sidebar_label: Overview
+slug: /numbers/porting
+description: A general overview of Bandwidth's porting services
+keywords:
+  - bandwidth
+  - numbers
+  - porting
+hide_title: false
+image: "@site/static/img/bw-icon.svg"
+---
+
+# Bandwidth Porting Overview
+
+Telephone number porting is the process by which a telephone number is moved from one service provider to another. Bandwidth provides a number of tools and services to make porting telephone numbers as easy as possible.
+
+This section summarizes the Bandwidth tools available for porting automation and provides links that can be used to drill down for more detailed information.
+
+At a high level, Bandwidth provides porting tools in two broad categories: **Port-in** and **Port-out**.
+
+Bandwidth asynchronous APIs like porting use a common pattern that we refer to as “**orders**”. With orders, you can either poll to check the progress, or you can subscribe for **notifications **as the order progresses.
+
+## Port-in
+
+From the Bandwidth perspective, port-in means moving a telephone number from another service provider to Bandwidth, or to one of Bandwidth's off-net partners. It could also mean porting a number from one of Bandwidth’s service provider customers to another of Bandwidth’s service provider customers.
+
+For more detailed information about porting numbers in, please see [Port-ins Overview](/docs/numbers/porting/port-ins/).
+
+## Port-out
+
+Porting out is moving telephone numbers from Bandwidth to another service provider, or to another of Bandwidth’s service provider customers. Port-outs are of interest to the service provider that is porting the number in, or away from Bandwidth, and to Bandwidth customers who want to know which numbers are porting out of their account.
+
+For detailed information about port-out requests (called LSRs) and port-out notifications, please refer to [Port-outs Overview](/docs/numbers/porting/port-outs/).
+
+## Orders
+
+For APIs that can take longer than around 30 seconds, Bandwidth creates an order to track the progress of the API. There are many types of orders, but they all work in basically the same way. The `POST` operation creates the order and returns a unique order-id by which you can refer to the order. Using the order-id, you can `GET`, `PUT`, `PATCH` (in some cases), or `DELETE` the order.
+
+For more information about Orders, please refer to [Order Model](/docs/numbers/porting/orderModel/).
+
+## Notifications
+
+Since orders are asynchronous and can take time to progress through the various states to completion, you have two options for tracking progress. You can either use the `GET` operation with the order-id to poll for the current state of the order, or you can subscribe to notifications about order state changes, or notes. You may subscribe to email notifications, or webhook notifications.
+
+For detailed information about how to subscribe for order notifications, please see [Subscribe/Notify](/apis/numbers/#tag/Subscriptions/operation/CreateSubscriptions/).
+
+## Porting Terminology
+
+For a table of porting terms, please refer to [Porting Terminology](/docs/numbers/porting/terminology/).