remove old icons

docs/articles/api-key-end-users.md

@@ -10,8 +10,8 @@ Zuplo provides several options depending on the level of customization required.
 
 For development and testing, the easiest way to obtain an API key is right in
 the [Zuplo Management Portal](https://portal.zuplo.com). From inside the **API
-Key Consumers** section in the <SettingsTabIcon /> **Settings** tab you can
-create and manage consumers and their keys.
+Key Consumers** section in the **Settings** tab you can create and manage
+consumers and their keys.
 
 For quick access the newest, non-expired API key is shown in this section.
 

docs/articles/custom-domains.md

@@ -22,10 +22,9 @@ for your Zuplo project.
 
 ### 1. Navigate to your project's Custom Domain Settings
 
-Go to your project in the Zuplo portal and open to the <SettingsTabIcon />
-**Settings** tab (1), then select **Custom Domain** (2) and click on the
-`Add New Custom Domain` button to open the `New Custom Domain` configuration
-modal.
+Go to your project in the Zuplo portal and open to the **Settings** tab (1),
+then select **Custom Domain** (2) and click on the `Add New Custom Domain`
+button to open the `New Custom Domain` configuration modal.
 
 ![Custom Domain](../../public/media/custom-domains/image.png)
 

docs/articles/dev-portal-auth0-auth.md

@@ -65,8 +65,8 @@ different URLs.
 
 ### 4/ Configure the Developer Portal
 
-Inside of the Zuplo Developer portal navigate to the <CodeEditorTabIcon />
-**Code Editor** tab and open the `dev-portal.json` file. You can
+Inside of the Zuplo Developer portal navigate to the **Code Editor** tab and
+open the `dev-portal.json` file. You can
 [edit the JSON manually](./dev-portal-json.md), but in this tutorial we will use
 the UI editor.
 

docs/articles/dev-portal-clerk-auth.md

@@ -41,9 +41,9 @@ to the value of the `client_secret` value in the API response.
 
 ### 2/ Configure the Developer Portal
 
-Inside of the Zuplo Developer portal navigate to the <CodeEditorTabIcon />
-**Code Editor** tab and open the `dev-portal.json` file. Open the JSON tab and
-edit the file to look like the following.
+Inside of the Zuplo Developer portal navigate to the **Code Editor** tab and
+open the `dev-portal.json` file. Open the JSON tab and edit the file to look
+like the following.
 
 ```json
 {

docs/articles/dev-portal-keycloak-auth.md

@@ -46,11 +46,11 @@ Dev Portal.
 
 ### 3/ Configure the Developer Portal
 
-Inside of the Zuplo Developer portal navigate to the <CodeEditorTabIcon />
-**Code Editor** tab and open the `dev-portal.json` file. Under the
-"Authentication" section, set the "Provider" to "OpenID Connect". Set the
-"Authority" value to the `issuer` value you copied from the JSON file in the
-previous step. Set the "Client ID" value to the value you set in step 1 (in our
-example this is `zuplo-dev-portal`). Click "Save".
+Inside of the Zuplo Developer portal navigate to the **Code Editor** tab and
+open the `dev-portal.json` file. Under the "Authentication" section, set the
+"Provider" to "OpenID Connect". Set the "Authority" value to the `issuer` value
+you copied from the JSON file in the previous step. Set the "Client ID" value to
+the value you set in step 1 (in our example this is `zuplo-dev-portal`). Click
+"Save".
 
 ![alt text](../../public/media/dev-portal-keycloak-auth/image-6.png)

docs/articles/environment-variables.md

@@ -17,8 +17,8 @@ write-only, meaning the value cannot be retrieved once it is set.
 
 ## Environment Variable Editor
 
-To set environment variables in your project, open the <SettingsTabIcon />
-**Settings** tab and then select the **Environment Variables** section.
+To set environment variables in your project, open the **Settings** tab and then
+select the **Environment Variables** section.
 
 To create a new variable, click **Add new variable**.
 

docs/articles/monetization-dev-portal-setup.md

@@ -90,10 +90,9 @@ Next, you will enable the monetization pages in your Developer Portal.
 
 ![Pricing Table](../../public/media/monetization-dev-portal-setup/image-2a.png)
 
-6. Finally, click the <EnvironmentVariablePicker/> icon next to the **Secret
-   Key** field and select the environment variable `STRIPE_SECRET_KEY` you
-   created earlier. This will prefill the form with the value
-   `$env(STRIPE_SECRET_KEY)`.
+6. Finally, click the icon next to the **Secret Key** field and select the
+   environment variable `STRIPE_SECRET_KEY` you created earlier. This will
+   prefill the form with the value `$env(STRIPE_SECRET_KEY)`.
 7. Click save to publish your changes.
 
 ## 3/ Preview Your Developer Portal

docs/handlers/openapi.md

@@ -14,8 +14,8 @@ spec.
 ## Setup via Portal
 
 The Forward Handler can be added to any route using the Route Designer. Open the
-**Route Designer** by navigating to the <CodeEditorTabIcon /> **Files** tab then
-click **routes.oas.json**. Inside any route, select **OpenAPI Spec** from the
+**Route Designer** by navigating to the **Files** tab then click
+**routes.oas.json**. Inside any route, select **OpenAPI Spec** from the
 **Request Handlers** drop-down.
 
 The handler should be defaulted to the OpenAPI file you currently have open, but

docs/handlers/redirect.md

@@ -10,9 +10,9 @@ status in routes.oas.json.
 ## Setup via Portal
 
 The Redirect Handler can be added to any route using the Route Designer. Open
-the **Route Designer** by navigating to the <CodeEditorTabIcon /> **Code
-Editor** tab then click **routes.oas.json**. Inside any route, select
-**Redirect** from the **Request Handlers** drop-down.
+the **Route Designer** by navigating to the **Code Editor** tab then click
+**routes.oas.json**. Inside any route, select **Redirect** from the **Request
+Handlers** drop-down.
 
 In the text box enter the URL location for the redirect.
 

docs/handlers/url-forward.md

@@ -20,9 +20,9 @@ forward any search parameters.
 ## Setup via Portal
 
 The Forward Handler can be added to any route using the Route Designer. Open the
-**Route Designer** by navigating to the <CodeEditorTabIcon /> **Files** tab then
-click **routes.oas.json**. Inside any route, select **URL Forward** from the
-**Request Handlers** drop-down.
+**Route Designer** by navigating to the **Files** tab then click
+**routes.oas.json**. Inside any route, select **URL Forward** from the **Request
+Handlers** drop-down.
 
 In the text box enter the URL to rewrite the request. Values can be mixed into
 the URL string using Javascript string interpolation syntax. For example:

docs/handlers/url-rewrite.md

@@ -13,9 +13,9 @@ virtually any aspect of your request.
 ## Setup via Portal
 
 The Rewrite Handler can be added to any route using the Route Designer. Open the
-**Route Designer** by navigating to the <CodeEditorTabIcon /> **Files** tab then
-click **routes.oas.json**. Inside any route, select **URL Rewrite** from the
-**Request Handlers** drop-down.
+**Route Designer** by navigating to the **Files** tab then click
+**routes.oas.json**. Inside any route, select **URL Rewrite** from the **Request
+Handlers** drop-down.
 
 ![Url Rewrite Handler selection](../../public/media/url-rewrite-handler-selection.png)
 

src/components/markdown/index.tsx

@@ -6,10 +6,8 @@ import { Card, CardGroup } from "./Card";
 import Icon from "./Icon";
 import { EnterpriseFeature } from "./Plans";
 import ZupIt from "./ZupIt";
-import * as UIIcons from "./ui-icons";
 
 const components: React.ComponentProps<typeof MDXProvider>["components"] = {
-  ...UIIcons,
   Icon,
   EnterpriseFeature,
   GithubButton,