diff --git a/gulpfile.mjs b/gulpfile.mjs
index 58ab2adea..d211635de 100644
--- a/gulpfile.mjs
+++ b/gulpfile.mjs
@@ -56,13 +56,6 @@ gulp.task('minify-css', () => {
.pipe(gulp.dest('./public/css'))
})
-// Copy Third Party Javascript
-
-gulp.task('copy-js', function () {
- return gulp.src('./src/js/xml2json.js')
- .pipe(gulp.dest('./public/js'))
-})
-
// Compile Javascript
gulp.task('js', (cb) => {
const myConfig = Object.assign({}, webpackConfig)
@@ -125,14 +118,14 @@ gulp.task('watch', () => {
})
// Development server with browsersync
-gulp.task('server', gulp.series(['hugo', 'css', 'copy-js', 'js', 'fonts', 'purgecss', 'minify-css', 'serve', 'watch']))
+gulp.task('server', gulp.series(['hugo', 'css', 'js', 'fonts', 'purgecss', 'minify-css', 'serve', 'watch']))
gulp.task('clean', () => {
return del(['./public/**/*'])
})
// Build/production tasks
-gulp.task('render', gulp.series(['css', 'copy-js', 'js', 'fonts', 'hugo', 'purgecss', 'minify-css']))
+gulp.task('render', gulp.series(['css', 'js', 'fonts', 'hugo', 'purgecss', 'minify-css']))
gulp.task('build', gulp.series(['clean', 'render', 'hash']))
/**
diff --git a/site/content/docs/CICD/vercel-deployment-protection.md b/site/content/docs/CICD/vercel-deployment-protection.md
index 8077623f6..1e32896dd 100644
--- a/site/content/docs/CICD/vercel-deployment-protection.md
+++ b/site/content/docs/CICD/vercel-deployment-protection.md
@@ -7,7 +7,7 @@ menu:
integrations:
parent: "Vercel"
identifier: vercel-deployment-protection
-cli: true
+
---
In some cases, you will need to provide authentication credentials to your Vercel deployment in order to run your browser
diff --git a/site/content/docs/alerting-and-retries/_index.md b/site/content/docs/alerting-and-retries/_index.md
index 189e09216..82ed4d010 100644
--- a/site/content/docs/alerting-and-retries/_index.md
+++ b/site/content/docs/alerting-and-retries/_index.md
@@ -7,7 +7,7 @@ slug: /
menu:
resources:
parent: "Alerting & retries"
-cli: true
+
aliases:
- /docs/alerting/
---
diff --git a/site/content/docs/alerting-and-retries/alert-channels.md b/site/content/docs/alerting-and-retries/alert-channels.md
index bcdde8ec7..d7c4125b0 100644
--- a/site/content/docs/alerting-and-retries/alert-channels.md
+++ b/site/content/docs/alerting-and-retries/alert-channels.md
@@ -6,7 +6,7 @@ weight: 31
menu:
resources:
parent: "Alerting & retries"
-cli: true
+
---
Alert channels are the channels through which alert notifications will reach you when a check starts failing, showing degraded performance or recover.
diff --git a/site/content/docs/alerting-and-retries/alert-settings.md b/site/content/docs/alerting-and-retries/alert-settings.md
index b70dfc52a..50353d6e2 100644
--- a/site/content/docs/alerting-and-retries/alert-settings.md
+++ b/site/content/docs/alerting-and-retries/alert-settings.md
@@ -9,7 +9,7 @@ menu:
aliases:
- /alerting/settings/
- /alerting/
-cli: true
+
---
Alert settings allow you to control when and how often you will be notified when a check starts failing, degrades or recovers.
diff --git a/site/content/docs/alerting-and-retries/retries.md b/site/content/docs/alerting-and-retries/retries.md
index 64a0c2a51..a65625e5d 100644
--- a/site/content/docs/alerting-and-retries/retries.md
+++ b/site/content/docs/alerting-and-retries/retries.md
@@ -6,7 +6,7 @@ weight: 32
menu:
resources:
parent: "Alerting & retries"
-cli: true
+
---
Sometimes the internet is flaky, or your app is just having a hiccup not worth pinging your on-call team about. Retries are your first line of defense against these types of false positives, leading to alert fatigue.
diff --git a/site/content/docs/alerting-and-retries/webhooks.md b/site/content/docs/alerting-and-retries/webhooks.md
index eb26cd83c..7f812d0d9 100644
--- a/site/content/docs/alerting-and-retries/webhooks.md
+++ b/site/content/docs/alerting-and-retries/webhooks.md
@@ -6,7 +6,7 @@ weight: 35
menu:
resources:
parent: "Alerting & retries"
-cli: true
+
---
Webhooks allow you to POST custom payloads to any endpoint in your own infrastructure or a third party provider. In a
diff --git a/site/content/docs/api-checks/_index.md b/site/content/docs/api-checks/_index.md
index e5d110b4d..616a0323e 100644
--- a/site/content/docs/api-checks/_index.md
+++ b/site/content/docs/api-checks/_index.md
@@ -10,7 +10,7 @@ menu:
identifier: overview-api-checks
aliases:
- 'docs/api-checks'
-cli: true
+
---
API checks consist of few parts:
diff --git a/site/content/docs/api-checks/assertions.md b/site/content/docs/api-checks/assertions.md
index a2d020e33..84f5b8846 100644
--- a/site/content/docs/api-checks/assertions.md
+++ b/site/content/docs/api-checks/assertions.md
@@ -6,7 +6,7 @@ weight: 10
menu:
resources:
parent: "API checks"
-cli: true
+
---
The response of an API request can be checked for correctness and timeliness by using assertions on the response data. Assertions are flexible statements that combine preset modifiers with custom values to meet the needs of a broad set of use cases.
diff --git a/site/content/docs/api-checks/limits.md b/site/content/docs/api-checks/limits.md
index d7444f96e..ac7a3ce0d 100644
--- a/site/content/docs/api-checks/limits.md
+++ b/site/content/docs/api-checks/limits.md
@@ -6,7 +6,7 @@ weight: 11
menu:
resources:
parent: "API checks"
-cli: true
+
---
diff --git a/site/content/docs/api-checks/request-settings.md b/site/content/docs/api-checks/request-settings.md
index d15134832..003cdfd29 100644
--- a/site/content/docs/api-checks/request-settings.md
+++ b/site/content/docs/api-checks/request-settings.md
@@ -6,7 +6,7 @@ weight: 8
menu:
resources:
parent: "API checks"
-cli: true
+
---
diff --git a/site/content/docs/api-checks/setup-script-examples.md b/site/content/docs/api-checks/setup-script-examples.md
index c2346ba7a..b72ce1654 100644
--- a/site/content/docs/api-checks/setup-script-examples.md
+++ b/site/content/docs/api-checks/setup-script-examples.md
@@ -7,7 +7,7 @@ menu:
resources:
parent: "Setup & teardown scripts"
identifier: setup-script-examples
-cli: true
+
---
Here are some examples on how to address common authentication use cases with setup scripts.
diff --git a/site/content/docs/api-checks/setup-teardown-scripts.md b/site/content/docs/api-checks/setup-teardown-scripts.md
index 6432fd48e..84c3d670d 100644
--- a/site/content/docs/api-checks/setup-teardown-scripts.md
+++ b/site/content/docs/api-checks/setup-teardown-scripts.md
@@ -6,7 +6,7 @@ weight: 12
menu:
resources:
parent: "API checks"
-cli: true
+
---
Setup and teardown scripts can be used to execute arbitrary JavaScript/TypeScript code before and/or after an API check.
diff --git a/site/content/docs/api-checks/teardown-script-examples.md b/site/content/docs/api-checks/teardown-script-examples.md
index 25da1f0c3..1ca984182 100644
--- a/site/content/docs/api-checks/teardown-script-examples.md
+++ b/site/content/docs/api-checks/teardown-script-examples.md
@@ -7,7 +7,7 @@ menu:
resources:
parent: "Setup & teardown scripts"
identifier: teardown-script-examples
-cli: true
+
---
## Update response status
diff --git a/site/content/docs/api-checks/timeouts-timing.md b/site/content/docs/api-checks/timeouts-timing.md
index 7059bced2..9b30d4d78 100644
--- a/site/content/docs/api-checks/timeouts-timing.md
+++ b/site/content/docs/api-checks/timeouts-timing.md
@@ -6,7 +6,7 @@ weight: 13
menu:
resources:
parent: "API checks"
-cli: true
+
---
All API checks are capped at a timeout of **30 seconds**. With each request, we record the most relevant timing phases. This can help you troubleshoot slow responses, e.g. your DNS might be slow.
diff --git a/site/content/docs/api-checks/variables.md b/site/content/docs/api-checks/variables.md
index 66cefec37..1358967af 100644
--- a/site/content/docs/api-checks/variables.md
+++ b/site/content/docs/api-checks/variables.md
@@ -7,7 +7,7 @@ menu:
resources:
parent: "API checks"
identifier: variables-api-checks
-cli: true
+
---
Multiple API checks can target the same server/service. In this case, your checks might need the same configuration item
diff --git a/site/content/docs/browser-checks/_index.md b/site/content/docs/browser-checks/_index.md
index 32c49d4b4..f7242bd17 100644
--- a/site/content/docs/browser-checks/_index.md
+++ b/site/content/docs/browser-checks/_index.md
@@ -10,7 +10,7 @@ menu:
aliases:
- /docs/browser-checks/quickstart/
- /docs/browser-checks/getting-started/
-cli: true
+
---
This guide gives you all the info to create your first Browser check with Checkly. You should have some prior
diff --git a/site/content/docs/browser-checks/degraded-state.md b/site/content/docs/browser-checks/degraded-state.md
index ef3af9ca0..9655db5ab 100644
--- a/site/content/docs/browser-checks/degraded-state.md
+++ b/site/content/docs/browser-checks/degraded-state.md
@@ -7,7 +7,7 @@ menu:
resources:
parent: "Browser checks"
identifier: "browser-degraded-state-soft-asserts"
-cli: true
+
---
If you want to monitor your service for non-critical errors or performance degradations you can use the degraded check state. This allows you to signal that parts of a Browser check performed slower than expected, or that it triggered assertions that are of lower criticality.
diff --git a/site/content/docs/browser-checks/file-system.md b/site/content/docs/browser-checks/file-system.md
index 9dd07d4de..a003314cd 100644
--- a/site/content/docs/browser-checks/file-system.md
+++ b/site/content/docs/browser-checks/file-system.md
@@ -8,7 +8,7 @@ menu:
parent: "Browser checks"
aliases:
- /docs/browser-checks/file-system/
-cli: true
+
---
You might want to use (binary) files in your browser checks. For example, you might want to upload a file to an upload
diff --git a/site/content/docs/browser-checks/login-scenarios.md b/site/content/docs/browser-checks/login-scenarios.md
index a71f76c99..8c2dbd24e 100644
--- a/site/content/docs/browser-checks/login-scenarios.md
+++ b/site/content/docs/browser-checks/login-scenarios.md
@@ -8,7 +8,7 @@ aliases:
menu:
resources:
parent: "Browser checks"
-cli: true
+
---
Scenarios where a user provides credentials to get access to a web app are extremely common. They are also
diff --git a/site/content/docs/browser-checks/multiple-tabs.md b/site/content/docs/browser-checks/multiple-tabs.md
index 4b6db383e..9f7d47def 100644
--- a/site/content/docs/browser-checks/multiple-tabs.md
+++ b/site/content/docs/browser-checks/multiple-tabs.md
@@ -8,7 +8,7 @@ aliases:
menu:
resources:
parent: "Browser checks"
-cli: true
+
---
Certain scenarios may require us to create new or multiple tabs simultaneously. Playwright Test supports this case and, as a consequence, Checkly does as well.
diff --git a/site/content/docs/browser-checks/playwright-test.md b/site/content/docs/browser-checks/playwright-test.md
index d816ef199..2b088cd1a 100644
--- a/site/content/docs/browser-checks/playwright-test.md
+++ b/site/content/docs/browser-checks/playwright-test.md
@@ -7,7 +7,7 @@ weight: 14
menu:
resources:
parent: "Browser checks"
-cli: true
+
---
Checkly natively supports running browser checks using the Playwright Test Runner, allowing you to write tests and use
diff --git a/site/content/docs/browser-checks/scraping-onpage-elements.md b/site/content/docs/browser-checks/scraping-onpage-elements.md
index 4e74e8b1f..3ed1226ce 100644
--- a/site/content/docs/browser-checks/scraping-onpage-elements.md
+++ b/site/content/docs/browser-checks/scraping-onpage-elements.md
@@ -7,7 +7,7 @@ weight: 15
menu:
resources:
parent: "Browser checks"
-cli: true
+
---
Any standard Node.js script that successfully finishes an execution is a valid, passing browser check. However, in
diff --git a/site/content/docs/browser-checks/screenshots.md b/site/content/docs/browser-checks/screenshots.md
index 044831598..aba709aab 100644
--- a/site/content/docs/browser-checks/screenshots.md
+++ b/site/content/docs/browser-checks/screenshots.md
@@ -6,7 +6,7 @@ weight: 19
menu:
resources:
parent: "Browser checks"
-cli: true
+
---
You can take up to 20 screenshots per browser check run. This is really handy when debugging a failure situation or just
diff --git a/site/content/docs/browser-checks/timeouts.md b/site/content/docs/browser-checks/timeouts.md
index b1b25f6c4..d3f1fda94 100644
--- a/site/content/docs/browser-checks/timeouts.md
+++ b/site/content/docs/browser-checks/timeouts.md
@@ -6,7 +6,7 @@ weight: 24
menu:
resources:
parent: "Browser checks"
-cli: true
+
---
There are different kinds of timeouts you will encounter while working with Browser checks:
diff --git a/site/content/docs/browser-checks/tracing-web-vitals.md b/site/content/docs/browser-checks/tracing-web-vitals.md
index 075d761a5..963f350dc 100644
--- a/site/content/docs/browser-checks/tracing-web-vitals.md
+++ b/site/content/docs/browser-checks/tracing-web-vitals.md
@@ -7,7 +7,7 @@ menu:
resources:
parent: "Browser checks"
identifier: tracing-web-vitals-browser-checks
-cli: true
+
---
For all your browser checks we automatically collect a comprehensive set of data like **console logs and network requests**
diff --git a/site/content/docs/browser-checks/variables.md b/site/content/docs/browser-checks/variables.md
index d091bd8e6..cc7e7c570 100644
--- a/site/content/docs/browser-checks/variables.md
+++ b/site/content/docs/browser-checks/variables.md
@@ -7,7 +7,7 @@ menu:
resources:
parent: "Browser checks"
identifier: variables-browser-checks
-cli: true
+
---
When creating browser checks, you probably run some code locally, store it in a Git repo or copy and paste it around
diff --git a/site/content/docs/browser-checks/visual-regression-snapshot-testing.md b/site/content/docs/browser-checks/visual-regression-snapshot-testing.md
index 8a5df0ce0..6594e9038 100644
--- a/site/content/docs/browser-checks/visual-regression-snapshot-testing.md
+++ b/site/content/docs/browser-checks/visual-regression-snapshot-testing.md
@@ -6,7 +6,7 @@ weight: 25
menu:
resources:
parent: "Browser checks"
-cli: true
+
aliases:
- "/docs/browser-checks/visual-comparison-snapshot-testing/"
---
diff --git a/site/content/docs/dashboards/_index.md b/site/content/docs/dashboards/_index.md
index 8561577ac..30a17f3e3 100644
--- a/site/content/docs/dashboards/_index.md
+++ b/site/content/docs/dashboards/_index.md
@@ -12,7 +12,7 @@ aliases:
- "/dashboards/overview/"
- "/docs/dashboards/overview/"
- "/docs/dashboards/"
-cli: true
+
---
You can use Checkly Dashboards to communicate check status and incidents to non-Checkly users. Use
diff --git a/site/content/docs/dashboards/custom-css.md b/site/content/docs/dashboards/custom-css.md
index 1624e4fd5..730140198 100644
--- a/site/content/docs/dashboards/custom-css.md
+++ b/site/content/docs/dashboards/custom-css.md
@@ -6,7 +6,7 @@ weight: 49
menu:
resources:
parent: "Dashboards"
-cli: true
+
---
You can completely customize the look & feel of your dashboard using custom CSS rules so the dashboard fits your company's
diff --git a/site/content/docs/dashboards/dashboard-customization.md b/site/content/docs/dashboards/dashboard-customization.md
index 1ccdde711..c8b4f8c71 100644
--- a/site/content/docs/dashboards/dashboard-customization.md
+++ b/site/content/docs/dashboards/dashboard-customization.md
@@ -6,7 +6,7 @@ weight: 47
menu:
resources:
parent: "Dashboards"
-cli: true
+
---
## Checkly URL
diff --git a/site/content/docs/dashboards/incidents.md b/site/content/docs/dashboards/incidents.md
index ef2bfe8c7..5cbfabd58 100644
--- a/site/content/docs/dashboards/incidents.md
+++ b/site/content/docs/dashboards/incidents.md
@@ -6,7 +6,7 @@ weight: 50
menu:
resources:
parent: "Dashboards"
-cli: true
+
---
Using **Incidents** you can communicate outages and planned maintenance to your audience — customers, co-workers, partners —
diff --git a/site/content/docs/groups/_index.md b/site/content/docs/groups/_index.md
index 37b775908..b0aa4763d 100644
--- a/site/content/docs/groups/_index.md
+++ b/site/content/docs/groups/_index.md
@@ -10,7 +10,7 @@ menu:
identifier: overview-groups
aliases:
- /docs/groups/
-cli: true
+
---
Groups allow you to organize your checks and centralize settings like base URL's, headers, variables and other properties
diff --git a/site/content/docs/groups/api-check-defaults.md b/site/content/docs/groups/api-check-defaults.md
index 70646c0fa..ba32177ff 100644
--- a/site/content/docs/groups/api-check-defaults.md
+++ b/site/content/docs/groups/api-check-defaults.md
@@ -6,7 +6,7 @@ weight: 27
menu:
resources:
parent: "Groups"
-cli: true
+
---
Using a set of shared defaults for API checks helps you manage checks that go to the same basic
diff --git a/site/content/docs/groups/variables.md b/site/content/docs/groups/variables.md
index 963de725d..c29774a5f 100644
--- a/site/content/docs/groups/variables.md
+++ b/site/content/docs/groups/variables.md
@@ -7,7 +7,7 @@ menu:
resources:
parent: "Groups"
identifier: variables-groups
-cli: true
+
---
You can set both variables and secrets for a Group of checks.
diff --git a/site/content/docs/heartbeat-checks/_index.md b/site/content/docs/heartbeat-checks/_index.md
index 04063e891..fdb32ea61 100644
--- a/site/content/docs/heartbeat-checks/_index.md
+++ b/site/content/docs/heartbeat-checks/_index.md
@@ -11,7 +11,7 @@ menu:
aliases:
- /docs/heartbeat-checks/quickstart/
- /docs/heartbeat-checks/getting-started/
-cli: true
+
---
This guide gives you all the info needed to get started with Checkly heartbeat checks.
diff --git a/site/content/docs/maintenance-windows/_index.md b/site/content/docs/maintenance-windows/_index.md
index 5307c46f6..65b87e085 100644
--- a/site/content/docs/maintenance-windows/_index.md
+++ b/site/content/docs/maintenance-windows/_index.md
@@ -10,7 +10,7 @@ menu:
identifier: overview-maintenance-windows
aliases:
- /docs/maintenance-windows/
-cli: true
+
---
You can schedule planned maintenance for your API, app or website using Checkly's maintenance windows. During maintenance
diff --git a/site/content/docs/multistep-checks/_index.md b/site/content/docs/multistep-checks/_index.md
index c4b14d146..93f3dfa7d 100644
--- a/site/content/docs/multistep-checks/_index.md
+++ b/site/content/docs/multistep-checks/_index.md
@@ -11,7 +11,7 @@ menu:
aliases:
- /docs/multistep-checks/quickstart/
- /docs/multistep-checks/getting-started/
-cli: true
+
---
This guide gives you all the info to create your first Multistep check with Checkly. You should have some prior
diff --git a/site/content/docs/multistep-checks/degraded-state.md b/site/content/docs/multistep-checks/degraded-state.md
index be0051d11..8c2482398 100644
--- a/site/content/docs/multistep-checks/degraded-state.md
+++ b/site/content/docs/multistep-checks/degraded-state.md
@@ -7,7 +7,7 @@ menu:
resources:
parent: "Multistep checks"
identifier: "multistep-degraded-state-soft-asserts"
-cli: true
+
---
If you want to monitor your API for non-critical errors or performance degradations you can use the degraded check state. This allows you to signal that parts of a Multistep check performed slower than expected, or that it triggered assertions that are of lower criticality.
diff --git a/site/content/docs/multistep-checks/example-checks.md b/site/content/docs/multistep-checks/example-checks.md
index d0f5d8a54..a0e792b6f 100644
--- a/site/content/docs/multistep-checks/example-checks.md
+++ b/site/content/docs/multistep-checks/example-checks.md
@@ -7,7 +7,7 @@ menu:
resources:
parent: "Multistep checks"
identifier: "multistep-example-checks"
-cli: true
+
---
Below are a number of checks showcasing how to use Multistep checks. These are similar to the templates provided in Checkly when creating a new Multistep check and should give you an idea of how to get started building various types of checks.
diff --git a/site/content/docs/multistep-checks/upload-downloads-filesystem.md b/site/content/docs/multistep-checks/upload-downloads-filesystem.md
index 1320d59aa..1871a9808 100644
--- a/site/content/docs/multistep-checks/upload-downloads-filesystem.md
+++ b/site/content/docs/multistep-checks/upload-downloads-filesystem.md
@@ -7,7 +7,7 @@ menu:
resources:
parent: "Multistep checks"
identifier: "multistep-checks-uploads"
-cli: true
+
---
You might want to use (binary) files in your Multistep checks. For example, you might want to upload a file to an API endpoint using a binary body. Or, you might want to validate some aspect of a file that is available for download on your
diff --git a/site/content/docs/multistep-checks/websockets.md b/site/content/docs/multistep-checks/websockets.md
index de1b30a79..286c9ab54 100644
--- a/site/content/docs/multistep-checks/websockets.md
+++ b/site/content/docs/multistep-checks/websockets.md
@@ -7,7 +7,7 @@ menu:
resources:
parent: "Multistep checks"
identifier: "multistep-checks-websockets"
-cli: true
+
---
To create a WebSocket check in Checkly, you'll need to write a script that establishes a WebSocket connection, sends messages, and validates responses.
diff --git a/site/content/docs/private-locations/_index.md b/site/content/docs/private-locations/_index.md
index 7de66b3f7..9c2fe2ecc 100644
--- a/site/content/docs/private-locations/_index.md
+++ b/site/content/docs/private-locations/_index.md
@@ -10,7 +10,7 @@ menu:
aliases:
- "/docs/private-locations/private-locations-getting-started/"
- "/docs/private-locations/"
-cli: true
+
---
A Private Location is a monitoring location that you manage by simply deploying a lightweight Checkly Agent.
diff --git a/site/content/docs/private-locations/checkly-agent-configuration.md b/site/content/docs/private-locations/checkly-agent-configuration.md
index f0289719c..f69d5bd45 100644
--- a/site/content/docs/private-locations/checkly-agent-configuration.md
+++ b/site/content/docs/private-locations/checkly-agent-configuration.md
@@ -8,7 +8,7 @@ menu:
parent: "Private Locations"
aliases:
- "/docs/private-locations/checkly-agent-guide/"
-cli: true
+
---
The Checkly Agent is a container that you need to deploy to run a Private Location in Checkly. The agent needs to be deployed on your infrastructure and executes checks on behalf of the Checkly application. For installation details, [check the getting started guide](/docs/private-locations/).
diff --git a/site/content/docs/private-locations/proxy.md b/site/content/docs/private-locations/proxy.md
index c266a2c68..052cb6787 100644
--- a/site/content/docs/private-locations/proxy.md
+++ b/site/content/docs/private-locations/proxy.md
@@ -6,7 +6,7 @@ weight: 56
menu:
resources:
parent: "Private Locations"
-cli: true
+
---
If you are operating our [Checkly Agent](/docs/private-locations/) behind an HTTP proxy,
diff --git a/site/content/docs/private-locations/running-on-kubernetes.md b/site/content/docs/private-locations/running-on-kubernetes.md
index 41146fe07..892ea3e9d 100644
--- a/site/content/docs/private-locations/running-on-kubernetes.md
+++ b/site/content/docs/private-locations/running-on-kubernetes.md
@@ -6,7 +6,7 @@ weight: 54
menu:
resources:
parent: "Private Locations"
-cli: true
+
---
We advise running any production-grade Checkly Agent deployments on a container orchestrator like Kubernetes. To help you get started, we created the [checkly-k8s repo](https://github.com/checkly/checkly-k8s) which contains a Helm chart and a few example Kubernetes manifests.
diff --git a/site/content/docs/private-locations/scaling-and-redundancy.md b/site/content/docs/private-locations/scaling-and-redundancy.md
index 289d8d4cb..f275fd9c3 100644
--- a/site/content/docs/private-locations/scaling-and-redundancy.md
+++ b/site/content/docs/private-locations/scaling-and-redundancy.md
@@ -6,7 +6,7 @@ weight: 55
menu:
resources:
parent: "Private Locations"
-cli: true
+
---
At least two running Checkly Agents per Private Location are recommended for redundancy. Agents are stateless and can be scaled horizontally as needed. You can add additional agents to a location at any time and remove them
diff --git a/site/content/docs/runtimes/_index.md b/site/content/docs/runtimes/_index.md
index 672f74c8b..0c43e6af4 100644
--- a/site/content/docs/runtimes/_index.md
+++ b/site/content/docs/runtimes/_index.md
@@ -9,7 +9,7 @@ menu:
parent: "Runtimes"
aliases:
- /docs/runtimes/
-cli: true
+
---
Checkly allows you to use JavaScript code in your [Browser checks](/docs/browser-checks/) and in the optional [setup & teardown scripts](/docs/api-checks/setup-teardown-scripts/) you can add to your API checks.
diff --git a/site/content/docs/runtimes/specs.md b/site/content/docs/runtimes/specs.md
index a495d30d9..ded8dc64f 100644
--- a/site/content/docs/runtimes/specs.md
+++ b/site/content/docs/runtimes/specs.md
@@ -8,7 +8,7 @@ menu:
parent: "Runtimes"
aliases:
- /docs/browser-checks/runner-specification/
-cli: true
+
---
By default, all our runners have their timezone set to UTC, regardless of their location.
diff --git a/site/content/docs/tcp-checks/_index.md b/site/content/docs/tcp-checks/_index.md
index 4ee630398..b350dacc7 100644
--- a/site/content/docs/tcp-checks/_index.md
+++ b/site/content/docs/tcp-checks/_index.md
@@ -7,7 +7,7 @@ menu:
parent: "TCP checks"
navTitle: Overview
slug: /
-cli: true
+
---
> **Early Access Feature:**
diff --git a/site/layouts/docs/baseof.html b/site/layouts/docs/baseof.html
index 29be5fdfd..757c9bdcc 100644
--- a/site/layouts/docs/baseof.html
+++ b/site/layouts/docs/baseof.html
@@ -21,7 +21,6 @@
{{ end }}
{{ .Scratch.Set "breadcrumb_text" $breadcrumb_text }}
{{ partial "head" . }}
-
diff --git a/site/layouts/docs/list.html b/site/layouts/docs/list.html
index 641eb1c63..05c5286e2 100644
--- a/site/layouts/docs/list.html
+++ b/site/layouts/docs/list.html
@@ -3,11 +3,6 @@
{{ partial "docs-menu" .}}
Table of contents
-