-);
diff --git a/src/stale/hyperglass/docs/components/supported-icon.tsx b/src/stale/hyperglass/docs/components/supported-icon.tsx
deleted file mode 100644
index f053c38..0000000
--- a/src/stale/hyperglass/docs/components/supported-icon.tsx
+++ /dev/null
@@ -1,13 +0,0 @@
-export const Supported = (props: React.ComponentProps<"svg">) => (
-
-);
diff --git a/src/stale/hyperglass/docs/favicon-formats.ts b/src/stale/hyperglass/docs/favicon-formats.ts
deleted file mode 100644
index 1ac6233..0000000
--- a/src/stale/hyperglass/docs/favicon-formats.ts
+++ /dev/null
@@ -1,80 +0,0 @@
-interface Favicon {
- rel: string | null;
- dimensions: [number, number];
- image_format: string;
- prefix: string;
-}
-
-export default [
- { dimensions: [48, 48], image_format: "ico", prefix: "favicon", rel: null },
- { dimensions: [16, 16], image_format: "png", prefix: "favicon", rel: "icon" },
- { dimensions: [32, 32], image_format: "png", prefix: "favicon", rel: "icon" },
- { dimensions: [64, 64], image_format: "png", prefix: "favicon", rel: "icon" },
- { dimensions: [96, 96], image_format: "png", prefix: "favicon", rel: "icon" },
- { dimensions: [180, 180], image_format: "png", prefix: "favicon", rel: "icon" },
- {
- dimensions: [57, 57],
- image_format: "png",
- prefix: "apple-touch-icon",
- rel: "apple-touch-icon",
- },
- {
- dimensions: [60, 60],
- image_format: "png",
- prefix: "apple-touch-icon",
- rel: "apple-touch-icon",
- },
- {
- dimensions: [72, 72],
- image_format: "png",
- prefix: "apple-touch-icon",
- rel: "apple-touch-icon",
- },
- {
- dimensions: [76, 76],
- image_format: "png",
- prefix: "apple-touch-icon",
- rel: "apple-touch-icon",
- },
- {
- dimensions: [114, 114],
- image_format: "png",
- prefix: "apple-touch-icon",
- rel: "apple-touch-icon",
- },
- {
- dimensions: [120, 120],
- image_format: "png",
- prefix: "apple-touch-icon",
- rel: "apple-touch-icon",
- },
- {
- dimensions: [144, 144],
- image_format: "png",
- prefix: "apple-touch-icon",
- rel: "apple-touch-icon",
- },
- {
- dimensions: [152, 152],
- image_format: "png",
- prefix: "apple-touch-icon",
- rel: "apple-touch-icon",
- },
- {
- dimensions: [167, 167],
- image_format: "png",
- prefix: "apple-touch-icon",
- rel: "apple-touch-icon",
- },
- {
- dimensions: [180, 180],
- image_format: "png",
- prefix: "apple-touch-icon",
- rel: "apple-touch-icon",
- },
- { dimensions: [70, 70], image_format: "png", prefix: "mstile", rel: null },
- { dimensions: [270, 270], image_format: "png", prefix: "mstile", rel: null },
- { dimensions: [310, 310], image_format: "png", prefix: "mstile", rel: null },
- { dimensions: [310, 150], image_format: "png", prefix: "mstile", rel: null },
- { dimensions: [196, 196], image_format: "png", prefix: "favicon", rel: "shortcut icon" },
-] as Favicon[];
diff --git a/src/stale/hyperglass/docs/global.d.ts b/src/stale/hyperglass/docs/global.d.ts
deleted file mode 100644
index 75facdc..0000000
--- a/src/stale/hyperglass/docs/global.d.ts
+++ /dev/null
@@ -1,8 +0,0 @@
-declare global {
- namespace NodeJS {
- interface ProcessEnv {
- NODE_ENV: 'development' | 'production';
- CF_PAGES_BRANCH: string;
- }
- }
-}
diff --git a/src/stale/hyperglass/docs/global.module.css b/src/stale/hyperglass/docs/global.module.css
deleted file mode 100644
index d6df9b3..0000000
--- a/src/stale/hyperglass/docs/global.module.css
+++ /dev/null
@@ -1,7 +0,0 @@
-.logo {
- color: #d84b4b;
-}
-
-html[class~=dark] .logo {
- color: #fff;
-}
\ No newline at end of file
diff --git a/src/stale/hyperglass/docs/next-env.d.ts b/src/stale/hyperglass/docs/next-env.d.ts
deleted file mode 100644
index 4f11a03..0000000
--- a/src/stale/hyperglass/docs/next-env.d.ts
+++ /dev/null
@@ -1,5 +0,0 @@
-///
-///
-
-// NOTE: This file should not be edited
-// see https://nextjs.org/docs/basic-features/typescript for more information.
diff --git a/src/stale/hyperglass/docs/next.config.mjs b/src/stale/hyperglass/docs/next.config.mjs
deleted file mode 100644
index 9223adc..0000000
--- a/src/stale/hyperglass/docs/next.config.mjs
+++ /dev/null
@@ -1,35 +0,0 @@
-import fs from "node:fs";
-import path from "node:path";
-import { fileURLToPath } from "node:url";
-import withNextra from "nextra";
-
-function copyChangelog() {
- const dir = path.dirname(fileURLToPath(import.meta.url));
- const src = path.resolve(dir, "..", "CHANGELOG.md");
- const data = fs.readFileSync(src);
- const replaced = data.toString().replace("# Changelog\n\n", "");
- const dst = path.resolve(dir, "pages", "changelog.mdx");
- fs.writeFileSync(dst, replaced);
-}
-
-copyChangelog();
-
-/**
- * @type {import('nextra').NextraConfig}
- */
-const nextraConfig = {
- theme: "nextra-theme-docs",
- themeConfig: "./theme.config.tsx",
-};
-
-/**
- * @type {import('next').NextConfig}
- */
-const config = {
- images: {
- unoptimized: true,
- },
- output: "export",
-};
-
-export default withNextra(nextraConfig)(config);
diff --git a/src/stale/hyperglass/docs/package.json b/src/stale/hyperglass/docs/package.json
deleted file mode 100644
index a63a8e9..0000000
--- a/src/stale/hyperglass/docs/package.json
+++ /dev/null
@@ -1,24 +0,0 @@
-{
- "name": "hyperglass-docs",
- "version": "2.0.0",
- "description": "hyperglass documentation",
- "private": true,
- "scripts": {
- "dev": "next dev",
- "start": "next start",
- "typecheck": "tsc --noEmit"
- },
- "author": "thatmattlove ",
- "license": "BSD-3-Clause-Clear",
- "dependencies": {
- "next": "^14.1.1",
- "nextra": "3.0.0-alpha.24",
- "nextra-theme-docs": "3.0.0-alpha.24",
- "react": "^18.2.0",
- "react-dom": "^18.2.0"
- },
- "devDependencies": {
- "@types/node": "^20.11.24",
- "typescript": "^5.3.3"
- }
-}
diff --git a/src/stale/hyperglass/docs/pages/_meta.tsx b/src/stale/hyperglass/docs/pages/_meta.tsx
deleted file mode 100644
index 78bc398..0000000
--- a/src/stale/hyperglass/docs/pages/_meta.tsx
+++ /dev/null
@@ -1,42 +0,0 @@
-export default {
- index: { title: "Introduction", theme: { breadcrumb: false } },
- "---": {
- type: "separator",
- },
- installation: "Installation",
- configuration: "Configuration",
- platforms: "Platforms",
- plugins: "Plugins",
- documentation: {
- title: "Documentation",
- type: "menu",
- items: {
- installation: {
- title: "Installation",
- href: "/installation",
- },
- configuration: {
- title: "Configuration",
- href: "/configuration",
- },
- plugins: {
- title: "Plugins",
- href: "/plugins",
- },
- changelog: {
- title: "Changelog",
- href: "/changelog",
- },
- license: {
- title: "License",
- href: "/license",
- },
- },
- },
- demo: {
- title: "Demo",
- type: "page",
- href: "https://demo.hyperglass.dev",
- newWindow: true,
- },
-};
diff --git a/src/stale/hyperglass/docs/pages/configuration/_meta.tsx b/src/stale/hyperglass/docs/pages/configuration/_meta.tsx
deleted file mode 100644
index 713550e..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/_meta.tsx
+++ /dev/null
@@ -1,7 +0,0 @@
-export default {
- overview: "Overview",
- config: "Config File",
- devices: "Devices File",
- directives: "Directives File",
- examples: "Examples",
-};
diff --git a/src/stale/hyperglass/docs/pages/configuration/config.mdx b/src/stale/hyperglass/docs/pages/configuration/config.mdx
deleted file mode 100644
index 85262af..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/config.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Configuration File
-description: hyperglass config.yaml file reference
----
-
-The `config.yaml` file is broken into multiple sections:
-
-## Top Level Parameters
-
-| Parameter | Type | Default Value | Description |
-| :----------------- | :-------------- | :------------------------------- | :------------------------------------------------------------ |
-| `org_name` | String | Beloved Hyperglass User | Your organization's name. |
-| `plugins` | List of Strings | | List of hyperglass [plugins](/plugins) to load. |
-| `primary_asn` | String | 65000 | Your organization's primary ASN. Used to set default UI text. |
-| `request_timeout` | Number | 90 | Global timeout in seconds for all requests. |
-| `site_description` | String | `org_name` Network Looking Glass | `` description, also used in the API documentation. |
-| `site_title` | String | `org_name` | Browser title, also used in the default terms & conditions. |
-
-#### Example with Defaults
-
-```yaml filename="config.yaml"
-org_name: Beloved Hyperglass User
-plugins: []
-primary_asn: 65000
-request_timeout: 90
-site_description: Beloved Hyperglass User Network Looking Glass
-site_title: Beloved Hyperglass User
-```
-
-## Other Configuration Sections
-
-| Parameter | Docs | Description |
-| :----------- | :--------------------------------------------------------------------- | :--------------------------------------------------------------- |
-| `cache` | [Caching Docs](/configuration/config/caching.mdx) | Customize how hyperglass caches responses. |
-| `logging` | [Logging Docs](/configuration/config/logging.mdx) | Customize file logging, syslog, webhooks, etc. |
-| `messages` | [Messages Docs](/configuration/config/messages.mdx) | Customize messages shown to users. |
-| `structured` | [Structured Output Docs](/configuration/config/structured-ouptput.mdx) | Customize how hyperglass handles structured output from devices. |
-| `web` | [Web UI Docs](/configuration/config/web-ui.mdx) | Customize the look and feel of hyperglass's web UI. |
-
-## Caveats
-
-### Arista EOS
-
-For whatever reason, the tested version of Arista EOS does not supply certain details about routes in its JSON output when running commands `show ip bgp regex ` or `show ip bgp community `. Specifically, the the route's timestamp and any attached communities are not supplied. When these commands are used with Arista EOS, hyperglass sets the timestamp to the current time, and the community to an empty list.
diff --git a/src/stale/hyperglass/docs/pages/configuration/config/_meta.tsx b/src/stale/hyperglass/docs/pages/configuration/config/_meta.tsx
deleted file mode 100644
index c91b461..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/config/_meta.tsx
+++ /dev/null
@@ -1,8 +0,0 @@
-export default {
- "api-docs": "API Docs",
- caching: "Caching",
- logging: "Logging & Webhooks",
- messages: "Messages",
- "structured-output": "Structured Output",
- "web-ui": "Web UI",
-};
diff --git a/src/stale/hyperglass/docs/pages/configuration/config/api-docs.mdx b/src/stale/hyperglass/docs/pages/configuration/config/api-docs.mdx
deleted file mode 100644
index a88dd43..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/config/api-docs.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
-## API Docs
-
-hyperglass automatically generates documentation for the REST API. The `docs` section allows users to customize the look, feel, and text used for the REST API documentation.
-
-| Parameter | Type | Default Value | Description |
-| :----------------- | :------ | :----------------------------- | :---------------------------------------------------------------------------------------------- |
-| `docs.base_url` | String | https://lg.example.com | Used for REST API samples. See the [demo](https://demo.hyperglass.dev/api/docs) for an example. |
-| `docs.enable` | Boolean | `true` | Enable or disable the REST API documentation. |
-| `docs.path` | String | /api/docs | Path to the REST API documentation. |
-| `docs.title` | String | `site_title` API Documentation | API docs title. Uses the `site_title` parameter from the [global](#global) parameters. |
-| `docs.description` | String | | API docs description. Appears below the title. |
-
-The documentation for API endpoints follow a common schema:
-
-- `devices`
-- `info`
-- `queries`
-- `query`
-
-### Schema
-
-| Parameter | Type | Description |
-| :------------ | :----- | :------------------------------------------------------------------------------- |
-| `title` | String | API endpoint title, displayed as the header text above the API endpoint section. |
-| `description` | String | API endpoint description, displayed inside each API endpoint section. |
-| `summary` | String | API endpoint summary, displayed beside the API endpoint path. |
-
-### Parameters
-
-| Parameter | Default Value |
-| :------------------------- | :------------------------------------------------------------------------------------------ |
-| `docs.devices.title` | Devices |
-| `docs.devices.description` | List of all devices/locations with associated identifiers, display names, networks, & VRFs. |
-| `docs.devices.summary` | Devices List |
-| `docs.info.title` | System Information |
-| `docs.info.description` | General information about this looking glass. |
-| `docs.info.summary` | System Information |
-| `docs.queries.title` | Supported Queries |
-| `docs.queries.description` | List of supported query types. |
-| `docs.queries.summary` | Query Types |
-| `docs.query.title` | Supported Query |
-| `docs.query.description` | Request a query response per-location. |
-| `docs.query.summary` | Query the Looking Glass |
-
-#### Example with Defaults
-
-```yaml filename="config.yaml"
-docs:
- base_url: https://lg.example.com
- enable: true
- mode: redoc
- path: /api/docs
- title: Beloved Hyperglass User Looking Glass API Documentation
- description: null
- # API Endpoints ↓
- devices:
- title: Devices
- description: List of all devices/locations with associated identifiers, display names, networks, & VRFs.
- summary: Devices List
- info:
- title: System Information
- description: General information about this looking glass.
- summary: System Information
- queries:
- title: Supported Queries
- description: List of supported query types.
- summary: Query Types
- query:
- title: Supported Query
- description: Request a query response per-location.
- summary: Query the Looking Glass
-```
diff --git a/src/stale/hyperglass/docs/pages/configuration/config/caching.mdx b/src/stale/hyperglass/docs/pages/configuration/config/caching.mdx
deleted file mode 100644
index 839b8e1..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/config/caching.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
-## Cache
-
-hyperglass automatically caches responses to reduce the number of times devices are queried for the same information.
-
-| Parameter | Type | Default Value | Description |
-| :---------------- | :------ | :------------ | :------------------------------------------------------------------------------ |
-| `cache.timeout` | Number | 120 | Number of seconds for which to cache device responses. |
-| `cache.show_text` | Boolean | True | If true, an indication that a user is viewing cached information will be shown. |
-
-### Example with Defaults
-
-```yaml filename="config.yaml"
-cache:
- timeout: 120
- show_text: true
-```
diff --git a/src/stale/hyperglass/docs/pages/configuration/config/logging.mdx b/src/stale/hyperglass/docs/pages/configuration/config/logging.mdx
deleted file mode 100644
index 5f1e834..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/config/logging.mdx
+++ /dev/null
@@ -1,90 +0,0 @@
-## Logging
-
-Console, file, HTTP, and/or syslog logging configuration.
-
-| Parameter | Type | Default Value | Description |
-| :---------- | :----- | :------------ | :---------------------------------------------- |
-| `directory` | String | /tmp | Path to directory where logs will be created. |
-| `format` | String | text | Log text format, must be `text` or `json`. |
-| `max_size` | String | 50MB | Maximum log file size before being overwritten. |
-
-### Syslog
-
-| Parameter | Type | Default Value | Description |
-| :-------- | :----- | :------------ | :---------------------- |
-| `host` | String | | Syslog target host. |
-| `port` | Number | 514 | Syslog target UDP port. |
-
-##### Syslog Example
-
-```yaml filename="config.yaml" copy
-logging:
- syslog:
- host: log.example.com
- port: 514
-```
-
-### HTTP Logging
-
-If enabled, logs will be sent by HTTP `POST` method.
-
-| Parameter | Type | Default Value | Description |
-| :----------- | :------ | :------------ | :---------------------------------------------- |
-| `provider` | String | generic | Must be `generic`, `msteams`, or `slack`. |
-| `host` | String | | URL |
-| `headers` | Map | | |
-| `params` | Map | | |
-| `verify_ssl` | Boolean | true | Enable or disable SSL certificate verification. |
-| `timeout` | Number | 5 | HTTP connection timeout in seconds. |
-
-#### Authentication
-
-Authentication is supported using HTTP basic authentication or an API key.
-
-| Parameter | Type | Default Value | Description |
-| :----------------------------- | :----- | :------------ | :--------------------------------------------------------------------------------------------------------- |
-| `http.authentication.mode` | String | basic | Must be `basic` or `api_key`. |
-| `http.authentication.username` | String | | Basic authentication username if `mode` is set to `basic`. |
-| `http.authentication.password` | String | | Basic authentication password if `mode` is set to `basic`, or API key value if `mode` is set to `api_key`. |
-| `http.authentication.header` | String | X-API-Key | Header name if `mode` is set to `api_key`. |
-
-#### Examples
-
-##### Generic
-
-```yaml filename="config.yaml" copy
-logging:
- http:
- provider: generic
- host: https://httpbin.org
- headers:
- x-special-header: super special header value
- params:
- source: hyperglass
- verify_ssl: true
- timeout: 5
- authentication:
- mode: basic
- username: your username
- password: super secret password
-```
-
-In the above example, hyperglass will send a `POST` request to `https://httpbin.org?source=hyperglass` with Basic Authentication headers set.
-
-##### Microsoft Teams Webhook
-
-```yaml filename="config.yaml" copy
-logging:
- http:
- provider: msteams
- host:
-```
-
-##### Slack
-
-```yaml filename="config.yaml" copy
-logging:
- http:
- provider: slack
- host:
-```
diff --git a/src/stale/hyperglass/docs/pages/configuration/config/messages.mdx b/src/stale/hyperglass/docs/pages/configuration/config/messages.mdx
deleted file mode 100644
index 135a788..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/config/messages.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
-## Message Customization
-
-hyperglass provides as much control over user-facing text/messages as possible. The following messages may be adjusted as needed:
-
-| Parameter | Type | Default Value | Description |
-| :------------------------------ | :----- | :------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `messages.authentication_error` | String | Authentication error occurred. | Displayed when hyperglass is unable to authenticate to a device. Usually, this indicates a configuration error. |
-| `messages.connection_error` | String | Error connecting to \{device_name\}: \{error\} | Displayed when hyperglass is unable to connect to a device. Usually, this indicates a configuration error. `{device_name}` and `{error}` will be used to display the device in question and the specific connection error. |
-| `messages.general` | String | Something went wrong. | Displayed when errors occur that hyperglass didn't anticipate or handle correctly. Seeing this error message may indicate a bug in hyperglass. If you see this in the wild, try enabling [debug mode](#global) and review the logs to pinpoint the source of the error. |
-| `messages.invalid_input` | String | \{target\} is not valid. | Displayed when a query target's value is invalid in relation to the corresponding query type. `{target}` will be used to display the invalid target. |
-| `messages.invalid_query` | String | \{target\} is not a valid \{query_type\} target. | Displayed when a query target's value is invalid in relation to the corresponding query type. `{target}` and `{query_type}` may be used to display the invalid target and corresponding query type. |
-| `messages.no_input` | String | \{field\} must be specified. | Displayed when a required field is not specified. `{field}` will be used to display the name of the field that was omitted. |
-| `messages.no_output` | String | The query completed, but no matching results were found. | Displayed when hyperglass can connect to a device and execute a query, but the response is empty. |
-| `messages.not_found` | String | \{type\} '\{name\}' not found. | Displayed when an object property does not exist in the configuration. `{type}` corresponds to a user-friendly name of the object type (for example, 'Device'), `{name}` corresponds to the object name that was not found. |
-| `messages.request_timeout` | String | Request timed out. | Displayed when the [`request_timeout`](#global) time expires. |
-| `messages.target_not_allowed` | String | \{target\} is not allowed. | Displayed when a query target is implicitly denied by a configured rule. `{target}` will be used to display the denied query target. |
-
-##### Example
-
-```yaml filename="config.yaml"
-message:
- general: Something with wrong.
-```
diff --git a/src/stale/hyperglass/docs/pages/configuration/config/structured-output.mdx b/src/stale/hyperglass/docs/pages/configuration/config/structured-output.mdx
deleted file mode 100644
index df93625..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/config/structured-output.mdx
+++ /dev/null
@@ -1,61 +0,0 @@
-## Structured
-
-Devices that support responding to a query with structured or easily parsable data can have their response data placed into an easier to read table (or JSON, when using the REST API). Currently, the following platforms have structured data supported in hyperglass:
-
-- Arista EOS
-- Juniper Junos
-
-When structured output is available, hyperglass checks the RPKI state of each BGP prefix returned using one of two methods:
-
-1. From the router's perspective
-2. From the perspective of [Cloudflare's RPKI Service](https://rpki.cloudflare.com/)
-
-Additionally, hyperglass provides the ability to control which BGP communities are shown to the end user.
-
-| Parameter | Type | Default Value | Description |
-| :----------------------------- | :-------------- | :------------ | :---------------------------------------------------------------------------------------------------------------------------- |
-| `structured.rpki.mode` | String | router | Use `router` to use the router's view of the RPKI state (1 above), or `external` to use Cloudflare's view (2 above). |
-| `structured.communities.mode` | String | deny | Use `deny` to deny any communities listed in `structured.communities.items`, or `permit` to _only_ permit communities listed. |
-| `structured.communities.items` | List of Strings | | List of communities to match. |
-
-### RPKI Examples
-
-#### Show RPKI State from the Device's Perspective
-
-```yaml filename="config.yaml" copy {2}
-structured:
- rpki:
- mode: router
-```
-
-#### Show RPKI State from a Public/External Perspective
-
-```yaml filename="config.yaml" copy {2}
-structured:
- rpki:
- mode: external
-```
-
-### Community Filtering Examples
-
-#### Deny Listed Communities by Regex pattern
-
-```yaml filename="config.yaml" {5-6}
-structured:
- communities:
- mode: deny
- items:
- - '^65000:1\d+$' # don't show any communities starting with 65000:1. 65000:1234 would be denied, but 65000:4321 would be permitted.
- - "65000:2345" # don't show the 65000:2345 community.
-```
-
-#### Permit only Listed Communities
-
-```yaml filename="config.yaml" {5-6}
-structured:
- communities:
- mode: permit
- items:
- - "^65000:.*$" # permit any communities starting with 65000, but no others.
- - "1234:1" # permit only the 1234:1 community.
-```
diff --git a/src/stale/hyperglass/docs/pages/configuration/config/web-ui.mdx b/src/stale/hyperglass/docs/pages/configuration/config/web-ui.mdx
deleted file mode 100644
index 7613447..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/config/web-ui.mdx
+++ /dev/null
@@ -1,294 +0,0 @@
-import { Callout } from "nextra/components";
-import { Color } from "~/components/color";
-
-## Web UI
-
-hyperglass provides extensive customization options for the look and feel of the web UI.
-
-| Parameter | Type | Default Value | Description |
-| :-------------------------- | :----- | :------------ | :----------------------------------------------------------------------------------------------------------------------------------------- |
-| `web.location_display_mode` | String | auto | Show the locations field as a `dropdown`, `gallery`. When using `auto`, if there are more than 5 location groups, `dropdown` will be used. |
-| `web.custom_javascript` | String | | Path to a javascript file that will be loaded with the website. |
-| `web.custom_html` | String | | Path to a custom HTML file that will be loaded with the website and rendered beneath the app. |
-
-### DNS over HTTPS
-
-[DNS over HTTPS](https://www.rfc-editor.org/rfc/rfc8484) is used to look up an FQDN query target from the perspective of the user's browser.
-
-| Parameter | Type | Default Value | Description |
-| :------------------ | :----- | :------------------------------------- | :-------------------------------------------------------------------------- |
-| `dns_provider.name` | String | cloudflare | If `cloudflare` or `google` are provided, no URL is necessary. |
-| `dns_provider.url` | String | `https://cloudflare-dns.com/dns-query` | Provide a custom DNS over HTTPS URL if you'd like to use your own resolver. |
-
-### Logo
-
-| Parameter | Type | Default Value | Description |
-| :----------------- | :--------------- | :------------ | :------------------------------------------------- |
-| `web.logo.light` | String | | Path to logo to show in light mode. |
-| `web.logo.dark` | String | | Path to logo to show in dark mode. |
-| `web.logo.favicon` | String | | Path to icon/logo from which to generate favicons. |
-| `web.logo.width` | Number or String | 100% | Width of logo, either as pixels or a percentage. |
-| `web.logo.height` | Number or String | | Height of logo, either as pixels or a percentage. |
-
-##### Example
-
-```yaml filename="config.yaml" copy
-web:
- logo:
- light: /path/to/light-logo.svg
- dark: /path/to/dark-logo.svg
- favicon: /path/to/favicon.svg
- width: 100%
- height: null
-```
-
-### Greeting
-
-The greeting is an optional modal/popup window that will present itself to users in the Web UI. It can be used for anything you want; for example:
-
-- A data privacy acknowledgement that must be acknowledged prior to proceeding
-- Information about your company
-- Instructions on how to use hyperglass
-
-| Parameter | Type | Default Value | Description |
-| :---------------------- | :------ | :------------ | :--------------------------------------------------------------------------------------------------- |
-| `web.greeting.enable` | Boolean | False | Enable or disable the greeting. |
-| `web.greeting.file` | String | | Path to markdown or plain text file that contains greeting content. |
-| `web.greeting.title` | String | Welcome | Text to be used as the greeting title. |
-| `web.greeting.button` | String | Continue | Text to be used for the button that acknowledges/closes the greeting. |
-| `web.greeting.required` | Boolean | False | If `true`, users cannot close the modal or run any queries until the greeting has been acknowledged. |
-
-##### Example
-
-```yaml filename="config.yaml" copy
-web:
- greeting:
- enable: true
- file: /path/to/your/file.md
- title: Welcome
- button: Continue
- required: false
-```
-
-### OpenGraph
-
-[OpenGraph](https://ogp.me/) is the thing that generates the pretty pictures, titles, and descriptions for links when you post them to sites/tools such as Facebook, Twitter, Slack, etc. By default, [this Opengraph image](/opengraph.jpg) is used, but you can provide your own image. You don't need to worry about sizing or formatting it properly, hyperglass will handle this for you.
-
-| Parameter | Type | Default Value | Description |
-| :-------------------- | :----- | :------------ | :---------------------------- |
-| `web.opengraph.image` | String | | Path to your OpenGraph image. |
-
-### Highlighting
-
-hyperglass can highlight special values in your router output and provide users with additional information about the content. For example, your organization's BGP communities or IP address space can be visually highlighted, and a tooltip can be shown when a user hovers over the highlighted value.
-
-Each value you wish to be highlighted is defined with the following schema:
-
-| Parameter | Type | Default Value | Description |
-| :-------- | :----- | :------------ | :------------------------------------------------------ |
-| `pattern` | String | | RegEx pattern or string to match against router output. |
-| `label` | String | | Tooltip value when the highlighted text is hovered. |
-| `color` | String | | Color name from [`web.theme.colors`](#colors). |
-
-##### Example
-
-```yaml filename="config.yaml" copy
-web:
- highlight:
- - pattern: "65000:1234"
- label: Special snowflake community that does a thing
- color: primary
- - pattern: '^192\.0\.2\.[0-9]+$'
- label: Magical IP Address
- color: blue
-```
-
-### Menus
-
-hyperglass can show completely-customizable menus in the footer. Each menu can be configured with the following schema:
-
-| Parameter | Type | Default Value | Description |
-| :-------- | :----- | :------------ | :------------------------------------------------------------------------------------------------------------------------- |
-| `title` | String | | Menu title, will be the text that shows on footer. |
-| `content` | String | | Plain text or markdown content of the menu or path to a file that contains plain text or markdown content. |
-| `side` | String | left | Side of the footer with which the menu will be grouped. |
-| `order` | Number | 0 | Optionally specify an order for each menu item. If not specified, menus will be rendered in the order they are configured. |
-
-##### Example
-
-```yaml filename="config.yaml" copy
-web:
- menus:
- - title: Terms & Conditions
- content:
- | **Don't** break stuff!
- _please_
- side: right
- order: 1
- - title: Help
- content: /path/to/help/file.md
- side: left
- order: 0
-```
-
-### Links
-
-hyperglass can show customizable links to anything you think your users might find helpful. Each link can be configured with the following schema:
-
-| Parameter | Type | Default Value | Description |
-| :---------- | :------ | :------------ | :-------------------------------------------------------------------------------------------------------------------- |
-| `title` | String | | Link text. |
-| `url` | String | | Link URL. |
-| `show_icon` | Boolean | True | If `true`, an icon indicating the link is an external link is shown. |
-| `side` | String | left | Side of the footer with which the link will be grouped. |
-| `order` | Number | 0 | Optionally specify an order for each link. If not specified, links will be rendered in the order they are configured. |
-
-##### Example
-
-```yaml filename="config.yaml" copy
-web:
- links:
- - title: PeeringDB
- url: https://www.peeringdb.com/65000
- show_icon: true
- side: right
- order: 1
- - title: Our Website
- url: https://example.com
- show_icon: false
- side: left
- order: 0
-```
-
-### Credit
-
-| Parameter | Type | Default | Description |
-| :-------- | :-----: | :-----: | :--------------------------------------------------------------------------------------- |
-| `enable` | Boolean | `true` | Enable or disable the display of developer credit & link to hyperglass GitHub repository |
-
-
- **Note from the Developer**
- If your organization's policy allows, and you don't mind, I request that you keep `credit`
- enabled. Remember: my goal for this project is get more networks to use looking glasses to make all
- of our lives easier. Because it's primarily other network operators who will use this tool to begin
- with, I'd love for any operators that use your looking glass to know where they can get their own.
-
-
-### Text
-
-Most of the text in the hyperglass UI can be overridden to suit your needs.
-
-| Parameter | Type | Default Value | Description |
-| :--------------------------- | :----- | :------------------------------------ | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `web.text.title_mode` | String | logo_only | See [title mode section](#title-mode) |
-| `web.text.title` | String | hyperglass | Title text. |
-| `web.text.subtitle` | String | Network Looking Glass | Subtitle text. |
-| `web.text.query_location` | String | Location | Text used to label the query location (router) field. |
-| `web.text.query_type` | String | Query Type | Text used to label the query type (directive) field. |
-| `web.text.query_target` | String | Target | Text used to label the query target field. |
-| `web.text.fqdn_tooltip` | String | Use \{protocol\} | Tooltip text used when a user hovers over the FQDN tooltip. |
-| `web.text.fqdn_message` | String | Your browser has resolved \{fqdn\} to | Text used when prompting a user to select a resolve IPv4 or IPv6 address for an FQDN query. |
-| `web.text.fqdn_error` | String | Unable to resolve \{fqdn\} | Text used when an FQDN is not resolvable. |
-| `web.text.fqdn_error_button` | String | Try Again | Button text used when an FQDN is not resolvable. |
-| `web.text.cache_prefix` | String | Results cached for | Text displayed with the cache timeout countdown. |
-| `web.text.cache_icon` | String | Cached from \{time\} UTC | Text used when a user hovers over the cache icon, which is displayed when a response was a cached response. `{time}` is replaced with the _original_ query's timestamp. |
-| `web.text.complete_time` | String | Completed in \{seconds\} | Text used when a user hovers over the success icon for a query result. `{seconds}` will be replaced with 'n seconds' where n is the time a query took to complete. |
-| `web.text.rpki_invalid` | String | Invalid | Text used in table output when a route's RPKI status is invalid. |
-| `web.text.rpki_valid` | String | Valid | Text used in table output when a route's RPKI status is valid. |
-| `web.text.rpki_unknown` | String | No ROAs Exist | Text used in table output when a route's RPKI status is unknown. |
-| `web.text.rpki_unverified` | String | Not Verified | Text used in table output when a route's RPKI status is unverified. |
-| `web.text.no_communities` | String | No Communities | Text used in table output when a route has no communities. |
-| `web.text.ip_error` | String | Unable to determine IP Address | Error displayed if hyperglass is unable to determine the user's IP. |
-| `web.text.no_ip` | String | No \{protocol\} Address | Text displayed if the user doesn't have an IP address of \{protocol\} (IPv4 or IPv6). |
-| `web.text.ip_select` | String | Select an IP Address | Text used to label the IP Address selection for the user's IP. |
-| `web.text.ip_button` | String | My IP | Text used for the user IP button. |
-
-#### Title Mode
-
-Available title modes are:
-
-| `title_mode` Value | Action |
-| :----------------- | :------------------------------------------------------------------ |
-| `logo_only` | Only the logo is displayed, no title or subtitle will be visible. |
-| `text_only` | Only the title and subtitle are displayed, no logo will be visible. |
-| `logo_subtitle` | Only the logo and subtitle are displayed, no title will be visible. |
-| `all` | Logo, title, and subtitle will all be visible. |
-
-##### Example
-
-```yaml filename="config.yaml"
-web:
- text:
- title: Our Looking Glass
- subtitle: Company Name, Inc.
- title_mode: text_only
-```
-
-### Theme
-
-hyperglass allows you to customize the colors and fonts used in the Web UI.
-
-| Parameter | Type | Default Value | Description |
-| :----------------------------- | :----- | :------------ | :--------------------------------------------------------------------------------------------------------------- |
-| `web.theme.default_color_mode` | String | | Set hyperglass's default color mode. By default, the user's system preference is used. Must be `light` or `dark` |
-
-#### Colors
-
-##### Intrinsic Colors
-
-| Parameter | Default Value |
-| :------------------------ | :---------------------- |
-| `web.theme.colors.black` | |
-| `web.theme.colors.white` | |
-| `web.theme.colors.dark` | |
-| `web.theme.colors.light` | |
-| `web.theme.colors.gray` | |
-| `web.theme.colors.red` | |
-| `web.theme.colors.orange` | |
-| `web.theme.colors.yellow` | |
-| `web.theme.colors.green` | |
-| `web.theme.colors.blue` | |
-| `web.theme.colors.teal` | |
-| `web.theme.colors.cyan` | |
-| `web.theme.colors.pink` | |
-| `web.theme.colors.purple` | |
-
-##### Functional Colors
-
-| Parameter | Default Value |
-| :--------------------------- | :--------------------- |
-| `web.theme.colors.primary` | |
-| `web.theme.colors.secondary` | |
-| `web.theme.colors.success` | |
-| `web.theme.colors.warning` | |
-| `web.theme.colors.error` | |
-| `web.theme.colors.danger` | |
-
-###### Example
-
-To override hyperglass's primary color, it's recommended to override its mapped intrinsic color. For example, to override the default primary color to cyan:
-
-```yaml filename="config.yaml"
-web:
- theme:
- colors:
- cyan: "#00ffff"
-```
-
-#### Fonts
-
-hyperglass's fonts are loaded from [Google Fonts](https://fonts.google.com/). Any Google font name may be specified to override the default fonts.
-
-| Parameter | Type | Default Value | Description |
-| :--------------------- | :----- | :------------ | :--------------------------------------------------------------------------------------- |
-| `web.theme.fonts.body` | String | Nunito | Font for all standard body text, including headings. |
-| `web.theme.fonts.mono` | String | Fire Code | Font for all monospace text such as inline code or code blocks, including device output. |
-
-##### Example
-
-```yaml filename="config.yaml"
-web:
- theme:
- fonts:
- body: Inter
-```
diff --git a/src/stale/hyperglass/docs/pages/configuration/devices.mdx b/src/stale/hyperglass/docs/pages/configuration/devices.mdx
deleted file mode 100644
index f30799a..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/devices.mdx
+++ /dev/null
@@ -1,135 +0,0 @@
-import { Callout } from "nextra/components";
-import { SupportedPlatforms } from "~/components/platforms";
-import { DocsButton } from "~/components/docs-button";
-
-## Device Configuration Parameters
-
-Each configured device may have the following parameters:
-
-| Parameter | Type | Default Value | Description |
-| :------------------ | :-------------- | :------------ | :----------------------------------------------------------------------------------------------------------------------------------------- |
-| `name` | String | | Display name of the device. |
-| `description` | String | | Description of the device, displayed as a subtle label. |
-| `avatar` | String | | Path to an avatar/logo image for this site. Used when [`web.location_display_mode`](/configuration/config/web-ui.mdx) is set to `gallery`. |
-| `address` | String | | IPv4 address, IPv6 address, or hostname of the device. |
-| `group` | String | | Group name, used to visually group devices in the UI. |
-| `port` | Number | | TCP port on which to connect to the device. |
-| `platform` | String | | Device platform/OS. Must be a [supported platform](/platforms.mdx). |
-| `structured_output` | Boolean | True | Disable structured output for a device that supports it. |
-| `directives` | List of Strings | | Enable referenced directives configured in the [directives config file](/configuration/directives.mdx). |
-| `driver` | String | netmiko | Specify which driver to use for this device. Currently, only `netmiko` is supported. |
-| `driver_config` | Mapping | | Mapping/dict of options to pass to the connection driver. |
-| `attrs` | Mapping | | Mapping/dict of variables, as referenced in configured directives. |
-| `credential` | Mapping | | Mapping/dict of a [credential configuration](/configuration/devices/credentials.mdx). |
-| `http` | Mapping | | Mapping/dict of [HTTP client options](/configuration/devices/http-device.mdx), if this device is connected via HTTP. |
-| `proxy` | Mapping | | Mapping/dict of [SSH proxy config](/configuration/devices/ssh-proxy.mdx) to use for this device's requests. |
-
-
-
-hyperglass ships with predefined [directives](/configuration/directives.mdx) (commands) for the following [platforms](platforms.mdx):
-
-
-
-All built in directives require that the following `attrs` be defined on each device using the directive:
-
-| Attribute | Value |
-| :-------- | :-------------------------------------------------------- |
-| `source4` | IPv4 address used to source Ping and Traceroute commands. |
-| `source6` | IPv6 address used to source Ping and Traceroute commands. |
-
-**Example**
-
-```yaml filename="devices.yaml" {5-7} copy
-devices:
- - name: New York, NY
- address: 192.0.2.1
- platform: cisco_ios
- attrs:
- source4: 192.0.2.1
- source6: "2001:db8::1"
-```
-
-
-
-
- If you do not utilize IPv6 in your network, you'll need to create your own directive that only
- has IPv4 commands.
-
-
-## Examples
-
-### Simple
-
-```yaml filename="devices.yaml" copy
-devices:
- - name: New York, NY
- address: 192.0.2.1
- platform: cisco_ios
- credential:
- username: you
- password: your password
- - name: San Francisco, CA
- address: 192.0.2.2
- platform: juniper
- credential:
- username: you
- password: your password
-```
-
-
- {" "}
- With Directives
-
-
-In this example, an additional directive `cisco-show-lldp-neighbors` is added to the built-in directives.
-
-```yaml filename="devices.yaml" copy {8-9}
-devices:
- - name: New York, NY
- address: 192.0.2.1
- platform: cisco_ios
- credential:
- username: you
- password: your password
- directives:
- - cisco-show-lldp-neighbors
-```
-
-
- {" "}
- Disable Built-in Directives
-
-
-In this example, _only_ the `cisco-show-lldp-neighbors` directive will be available. Built-in directives are disabled.
-
-```yaml filename="devices.yaml" copy {8-10}
-devices:
- - name: New York, NY
- address: 192.0.2.1
- platform: cisco_ios
- credential:
- username: you
- password: your password
- directives:
- - builtin: false
- - cisco-show-lldp-neighbors
-```
-
-
- {" "}
- Enable Specifc Built-in Directives
-
-
-In this example, only specified built-in directives are made available.
-
-```yaml filename="devices.yaml" copy {8-9}
-devices:
- - name: New York, NY
- address: 192.0.2.1
- platform: cisco_ios
- credential:
- username: you
- password: your password
- directives:
- - builtin: [bgp_route, traceroute]
-```
diff --git a/src/stale/hyperglass/docs/pages/configuration/devices/_meta.tsx b/src/stale/hyperglass/docs/pages/configuration/devices/_meta.tsx
deleted file mode 100644
index cc95490..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/devices/_meta.tsx
+++ /dev/null
@@ -1,5 +0,0 @@
-export default {
- credentials: "Credentials",
- "http-device": "HTTP Device",
- "ssh-proxy": "SSH Proxy",
-};
diff --git a/src/stale/hyperglass/docs/pages/configuration/devices/credentials.mdx b/src/stale/hyperglass/docs/pages/configuration/devices/credentials.mdx
deleted file mode 100644
index 463ff68..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/devices/credentials.mdx
+++ /dev/null
@@ -1,35 +0,0 @@
-Each device must be configured with credentials with which hyperglass can log into the device and execute commands.
-
-## Credential Configuration
-
-| Parameter | Type | Default Value | Description |
-| :-------------------- | :----- | :------------ | :----------------------------------------------------- |
-| `credential.username` | String | | Username to use for authentication to the device. |
-| `credential.password` | String | | Password to use for authentication to the device. |
-| `credential.key` | String | | Path to SSH key used for authentication to the device. |
-
-### Examples
-
-#### Username & Password
-
-```yaml filename="devices.yaml" copy {5-7}
-devices:
- - name: New York, NY
- address: 192.0.2.1
- platform: cisco_ios
- credential:
- username: you
- password: your password
-```
-
-#### SSH Private Key
-
-```yaml filename="devices.yaml" copy {5-7}
-devices:
- - name: San Francisco, CA
- address: 192.0.2.2
- platform: juniper
- credential:
- username: you
- key: /path/to/your/ssh/key
-```
diff --git a/src/stale/hyperglass/docs/pages/configuration/devices/http-device.mdx b/src/stale/hyperglass/docs/pages/configuration/devices/http-device.mdx
deleted file mode 100644
index ce14abe..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/devices/http-device.mdx
+++ /dev/null
@@ -1,85 +0,0 @@
-hyperglass supports collecting output from a generic HTTP endpoint.
-
-## HTTP Configuration
-
-| Parameter | Type | Default Value | Description |
-| :---------------------- | :------ | :------------ | :--------------------------------------------------------------------------------------------------------------------- |
-| `http.attribute_map` | Mapping | | Mapping/dict of hyperglass query fields as keys, and hyperglass query field replacements as values. |
-| `http.basic_auth` | Mapping | | If basic authentication is required, provide a mapping/dict containing the basic authentication username and password. |
-| `http.body_format` | String | json | Body format, options are `json` `yaml` `xml` `text` |
-| `http.follow_redirects` | Boolean | `false` | Follow HTTP redirects from server. |
-| `http.headers` | Mapping | | Mapping/dict of http headers to append to requests. |
-| `http.method` | String | GET | HTTP method to use for requests. |
-| `http.path` | String | / | HTTP URI/Path. |
-| `http.query` | Mapping | | Mapping/Dict of URL Query Parameters. |
-| `http.retries` | Number | 0 | Number of retries to perform before request failure. |
-| `http.scheme` | String | https | HTTP schema, must be `http` or `https` |
-| `http.source` | String | | Request source IP address. |
-| `http.ssl_ca` | String | | Path to SSL CA certificate file for SSL validation. |
-| `http.ssl_client` | String | | Path to client SSL certificates for request. |
-| `http.timeout` | Number | 5 | Request timeout in seconds. |
-| `http.verify_ssl` | Boolean | `true` | If `false`, invalid certificates for HTTPS hosts will be ignored. |
-
-### Example
-
-#### Basic
-
-The following example will send an HTTP POST request to `https://192.0.2/path/to/query/device` with HTTP basic authentication, and will not verify the SSL certificate.
-
-```yaml filename="devices.yaml" copy
-devices:
- - name: New York, NY
- address: 192.0.2.1
- http:
- path: /path/to/query/device
- method: POST
- verify_ssl: false
- basic_auth:
- username: you
- password: your password
-```
-
-Given the following hyperglass query:
-
-| Field | Value |
-| :------------- | :------------------ |
-| Query Target | `192.0.2.0/24` |
-| Query Location | `your_location` |
-| Query Type | `example_directive` |
-
-The body of the request will be:
-
-```json
-{
- "query_target": "192.0.2.0/24",
- "query_location": "your_location",
- "query_type": "example_directive"
-}
-```
-
-#### Non-HTTPS Request
-
-The following example will send an HTTP GET request to `http://192.0.2.1/path/to/query/device`:
-
-```yaml filename="devices.yaml" {6} copy
-devices:
- - name: New York, NY
- address: 192.0.2.1
- http:
- path: /path/to/query/device
- scheme: http
-```
-
-#### Header Authentication
-
-The following example will send an HTTP GET request to `https://192.0.2.1/path/to/query/device` with an `Authorization` header:
-
-```yaml filename="devices.yaml" {6-7} copy
-devices:
- - name: New York, NY
- address: 192.0.2.1
- http:
- path: /path/to/query/device
- headers:
- Authorization: your special token
-```
diff --git a/src/stale/hyperglass/docs/pages/configuration/devices/ssh-proxy.mdx b/src/stale/hyperglass/docs/pages/configuration/devices/ssh-proxy.mdx
deleted file mode 100644
index 99d19f1..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/devices/ssh-proxy.mdx
+++ /dev/null
@@ -1,30 +0,0 @@
-In cases where access to the devices is secured behind a "jump box" or other intermediary server/device, hyperglass can use SSH local port forwarding to SSH to an intermedary device first, and then to the device.
-
-## SSH Proxy Configuration
-
-| Parameter | Type | Default Value | Description |
-| :----------------- | :------ | :------------ | :----------------------------------------------------------------------------------- |
-| `proxy.address` | String | | IPv4 address, IPv6 address, or hostname of SSH proxy. |
-| `proxy.port` | Number | 22 | TCP port to use for connecting to the SSH proxy. |
-| `proxy.platform` | String | linux_ssh | Currently, only `linux_ssh` is supported. |
-| `proxy.credential` | Mapping | | Mapping/dict of a [credential configuration](/configuration/config/credentials.mdx). |
-
-### Examples
-
-#### Use an SSH Proxy When Connecting to a Device
-
-```yaml filename="devices.yaml" copy
-devices:
- - name: New York, NY
- address: 192.0.2.1
- credential:
- username: you
- password: your password
- proxy:
- address: 203.0.113.1
- credential:
- username: your proxy username
- password: your proxy password
-```
-
-In the above example, the credentials `your proxy username`/`your proxy password` will be used to authenticate from the hyperglass server to the SSH proxy, and the credentials `you`/`your password` will be used to authentiate from the SSH proxy to the device.
diff --git a/src/stale/hyperglass/docs/pages/configuration/directives.mdx b/src/stale/hyperglass/docs/pages/configuration/directives.mdx
deleted file mode 100644
index 9da3812..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/directives.mdx
+++ /dev/null
@@ -1,188 +0,0 @@
-import { Callout } from "nextra/components";
-
-## What is a directive?
-
-
-
-A directive is a defined configuration for one or more **commands** to run on a device. For example, a BGP Route query is a built-in directive. A directive defines:
-
-- What command (or commands) to run on the device
-- Type of UI field, text input or select
-- If the field can accept multiple values
-- Help information to show about the directive
-- Validation rules
-
-
-
-Each directive has the following options:
-
-| Parameter | Type | Default Value | Description |
-| :------------------- | :-------------- | :------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `name` | String | | Display name of the directive. |
-| `rules` | List of Rules | | List of [rule configs](#rules) |
-| `field` | Mapping | | Mapping/dict of [fields config](#fields) |
-| `info` | String | | File path to markdown-formatted help information about the directive. |
-| `plugins` | List of Strings | | List of plugin names to use with this directive. |
-| `groups` | List of Strings | | List of names by which directives are grouped in the UI. |
-| `multiple` | Boolean | `false` | Command supports receiving multiple values. For example, Cisco IOS's `show ip bgp community` accepts multiple communities as arguments. |
-| `multiple_separator` | String | `" "` | String by which multiple values are separated. For example, a list of values `[65001, 65002, 65003]` would be rendered as `65001 65002 65003` for when the command is run. |
-
-## Rules
-
-A rule is a way of saying "if a query target matches the rule's conditions, run this command".
-
-| Parameter | Type | Default Value | Description |
-| :---------- | :-------------- | :------------ | :--------------------------------------------------------------------------------------------- |
-| `condition` | String | | Regular expression to match or IP prefix in which the value being evaluated must be contained. |
-| `action` | String | permit | `permit` or `deny` the directive target when this rule is matched. |
-| `commands` | List of Strings | | Commands to run when this rule matches. `{target}` is replaced with the query target. |
-
-### IP Rule
-
-| Parameter | Type | Default Value | Description |
-| :------------------ | :------ | :------------ | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `ge` | Number | 0 | Prefix length greater than defined will be matched. |
-| `le` | Number | 32,128 | `32` for IPv4 evaluations, `128` for IPv6 evaluations. Prefix length less than defined will be matched. |
-| `allow_reserved` | Boolean | `false` | Allow reserved ([RFC1918](https://www.rfc-editor.org/rfc/rfc1918), [RFC5735](https://www.rfc-editor.org/rfc/rfc5735), [RFC5737](https://www.rfc-editor.org/rfc/rfc5737.html), etc.) addresses to pass validation. |
-| `allow_unspecified` | Boolean | `false` | Allow unspecified addresses (`0.0.0.0` `::`) to pass validation. |
-| `allow_loopback` | Boolean | `false` | Allow [loopback addresses](https://www.rfc-editor.org/rfc/rfc1700.html) (`127.0.0.0/8` `::1`) to pass validation. |
-
-#### Examples
-
-##### Require IPv4 Queries between /8 and /24
-
-```yaml filename="directives.yaml" {5-6} /{target} {mask}/ copy
-your-directive:
- name: IP Route
- rules:
- - condition: 0.0.0.0/0
- ge: 8
- le: 24
- command: "show ip route {target} {mask}"
-```
-
-Given a query target of 198.18.0.0/15, the command run on the device would be:
-
-```none /198.18.0.0 255.254.0.0/
-show ip route 198.18.0.0 255.254.0.0
-```
-
-##### Deny a Specific Prefix
-
-```yaml filename="directives.yaml" {5} copy
-your directive:
- name: BGP Route
- rules:
- - condition: "192.0.2.0/24"
- action: deny
- - condition: "0.0.0.0/0"
- command: "show ip bgp {target}"
-```
-
-In this example, a query of any IP address or prefix contained within 192.0.2.0/24 will result in an error.
-
-##### Run Multiple Commands
-
-```yaml filename="directives.yaml" /{target}/ {6-7} copy
-your-directive:
- name: BGP Communities
- rules:
- - condition: "65000:[0-9]+"
- commands:
- - "show route table inet.0 community {target} detail"
- - "show route table inet6.0 community {target} detail"
-```
-
-In this example, a query of `65000:1` would result in the following commands being sent to the device:
-
-```none /65000:1/
-show route table inet.0 community 65000:1 detail
-show route table inet6.0 community 65000:1 detail
-```
-
-The output for both commands will be shown as the query result.
-
-### Regex Validation
-
-To validate input by regex pattern, just specify a regex pattern as the `condition`
-
-```yaml filename="directives.yaml" copy
-your-directive:
- name: DNS Query
- rules:
- - condition: '^.+\.yourdomain\.com$'
-```
-
-### No Validation
-
-```yaml filename="directives.yaml" /{target}/ copy {4}
-your-directive:
- name: IP Route
- rules:
- - condition: null
- command: show ip route {target}
-```
-
-In this example, any query would pass, regardless of query input. For instance, if a user selected this directive/query type and queried `your mom`, the real command sent to the device will be:
-
-```none /your mom/
-show ip route your mom
-```
-
-## Fields
-
-### Text Input
-
-| Parameter | Type | Default Value | Description |
-| :------------ | :----- | :------------ | :---------------------------------------------------- |
-| `description` | String | | Field description, displayed as a label or help text. |
-| `validation` | String | | Regex pattern to validate text input. |
-
-### Select
-
-| Parameter | Type | Default Value | Description |
-| :------------ | :-------------- | :------------ | :---------------------------------------------------- |
-| `description` | String | | Field description, displayed as a label or help text. |
-| `options` | List of Options | | |
-
-#### Options
-
-Each select option uses the following schema:
-
-| Parameter | Type | Default Value | Description |
-| :------------ | :----- | :------------ | :------------------------------------------------------- |
-| `description` | String | | Field description, displayed as a label or help text. |
-| `name` | String | | If specified, will be used as the option's display name. |
-| `value` | String | | Option value sent to the device. |
-
-### Examples
-
-Example of a text directive expecting a string value matching a regex pattern:
-
-```yaml filename="directives.yaml" copy {6-7}
-your-directive:
- name: IP Route
- rules:
- - condition: null
- command: show ip route {target}
- field:
- description: IP of target
- validation: '[0-9a-f\.\:]+'
-```
-
-Example of a select directive:
-
-```yaml filename="directives.yaml" copy {6-12}
-your-directive:
- name: BGP Community
- rules:
- - condition: null
- command: show ip bgp community {target}
- field:
- description: BGP community to show
- options:
- - value: "65001:1"
- description: Provider A Routes
- - value: "65001:2"
- description: Provider B Routes
-```
diff --git a/src/stale/hyperglass/docs/pages/configuration/examples/_meta.tsx b/src/stale/hyperglass/docs/pages/configuration/examples/_meta.tsx
deleted file mode 100644
index d415124..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/examples/_meta.tsx
+++ /dev/null
@@ -1,5 +0,0 @@
-export default {
- "basic-configuration": "Basic Configuration",
- "add-your-own-command": "Add Your Own Command",
- "customize-the-ui": "Customize the UI",
-};
diff --git a/src/stale/hyperglass/docs/pages/configuration/examples/add-your-own-command.mdx b/src/stale/hyperglass/docs/pages/configuration/examples/add-your-own-command.mdx
deleted file mode 100644
index a8f588a..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/examples/add-your-own-command.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
-import { Steps } from "nextra/components";
-
-## Add Your Own Command
-
-While hyperglass does come with several built-in [directives](/configuration/configuration/directives.mdx) (commands), you can also add your own. For example, say you want to add a command that shows the BGP summary from a device:
-
-
-
-### Create the Directive
-
-```yaml filename="directives.yaml" copy
-show-bgp-summary:
- name: BGP Summary
- rules:
- - condition: null
- command: show bgp all summary
- field: null
-```
-
-### Associate the Directive with the Device
-
-```yaml filename="devices.yaml" {5-6} copy
-devices:
- - name: Your Router
- address: 192.0.2.1
- platform: cisco_ios
- directives:
- - show-bgp-summary
-```
-
-
-
-## Default Directives
-
-By default, all built-in directives are _also_ enabled. If you wish to _only_ enable directives you specify, you can use `builtins: false` as a directive:
-
-```yaml filename="devices.yaml" {6-7} copy
-devices:
- - name: Your Router
- address: 192.0.2.1
- platform: cisco_ios
- directives:
- - builtins: false
- - show-bgp-summary
-```
-
-In the above example, _only_ the `show-bgp-summary` directive will be enabled.
-
-You can also selectively enable certain built-in directives:
-
-```yaml filename="devices.yaml" {6} copy
-devices:
- - name: Your Router
- address: 192.0.2.1
- platform: cisco_ios
- directives:
- - builtins: [bgp_route, traceroute]
-```
-
-In the above example, _only_ the BGP Route and Traceroute built-in directives will be enabled.
diff --git a/src/stale/hyperglass/docs/pages/configuration/examples/basic-configuration.mdx b/src/stale/hyperglass/docs/pages/configuration/examples/basic-configuration.mdx
deleted file mode 100644
index c7e64c5..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/examples/basic-configuration.mdx
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: Basic Configuration
-description: Get started with a basic hyperglass configuration
----
-
-import { Callout } from "nextra/components";
-
-To get started, hyperglass only needs to know about your devices.
-
-
- **Devices** are your routers, switches, or whatever else you want to call the endpoints
- hyperglass will query for information.
-
-
-## Simple Device Configuration
-
-```yaml filename="devices.yaml"
-devices:
- - name: NYC Router 1
- address:
- credential:
- username:
- password:
- platform: cisco_ios
- attrs:
- source4:
- source6:
-```
-
-That's it!
diff --git a/src/stale/hyperglass/docs/pages/configuration/examples/customize-the-ui.mdx b/src/stale/hyperglass/docs/pages/configuration/examples/customize-the-ui.mdx
deleted file mode 100644
index 24e564a..0000000
--- a/src/stale/hyperglass/docs/pages/configuration/examples/customize-the-ui.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-description: Customize hyperglass to fit your needs.
----
-
-import { DocsButton } from "~/components/docs-button";
-
-
- {" "}
- Change the Title and Organization Name
-
-
-```yaml filename="config.yaml"
-site_title: Our super neat looking glass
-org_name: Cool Company
-```
-
-