Draft from Sep 9 (2)

communicate/status-pages/overview.mdx

@@ -30,13 +30,13 @@ Components belong to one status page. You manage them in the page's settings, wh
 
 Each component has one of five statuses:
 
-| Status | Meaning |
-|--------|---------|
-| Operational | Everything works |
-| Under maintenance | Planned maintenance is running |
-| Degraded performance | Slow, but working |
-| Partial outage | Some functionality is unavailable |
-| Major outage | The component is down |
+| Status | Meaning | Uptime calculation |
+| --- | --- | --- |
+| Operational | Everything works | N/A |
+| Under maintenance | Planned maintenance is running | 0% |
+| Degraded performance | Slow, but working | 0% |
+| Partial outage | Some functionality is unavailable | 30% |
+| Major outage | The component is down | 100% |
 
 A component's status is set by open [incidents](/communicate/status-pages/incidents): each incident declares an impact per affected component. The page header shows the worst status across all components.
 
@@ -54,9 +54,10 @@ Incident automation is available on Communicate Team and Enterprise plans. [View
 
 Uptime is calculated over the **last 90 days**, per component, from incident impacts:
 
-- **Major outage** time counts as full downtime.
-- **Partial outage** time counts as 30% downtime.
-- **Degraded performance** and **under maintenance** do not lower uptime.
+- **Major outage** counts as 100% downtime.
+- **Partial outage** counts as 30% downtime.
+- **Degraded performance** counts as 0% dowtime as the service is still usable.
+- **Under maintenance** counts as 0% downtime as it signals intentional shutdown of a service.
 
 ```
 Uptime = ((Total time - Weighted downtime) / Total time) × 100

docs.json

@@ -1226,7 +1226,6 @@
                 "pages": [
                   "learn/playwright/challenging-flows",
                   "learn/playwright/handling-test-data",
-                  "learn/playwright/how-to-parameterize-playwright-projects",
                   "learn/playwright/performance",
                   "learn/playwright/scraping-behind-login",
                   "learn/playwright/script-recorders",
@@ -1245,7 +1244,6 @@
                   "learn/playwright/file-download",
                   "learn/playwright/google-login-automation",
                   "learn/playwright/how-to-search",
-                  "learn/playwright/login-automation",
                   "learn/playwright/microsoft-login-automation",
                   "learn/playwright/testing-coupons",
                   "learn/playwright/testing-file-uploads",
@@ -1258,7 +1256,6 @@
                   "learn/playwright/debugging-errors",
                   "learn/playwright/debugging",
                   "learn/playwright/error-click-not-executed",
-                  "learn/playwright/error-element-not-found",
                   "learn/playwright/error-element-not-visible",
                   "learn/playwright/error-target-closed",
                   "learn/playwright/error-wait-not-respected"
@@ -1290,7 +1287,6 @@
               {
                 "group": "Classification",
                 "pages": [
-                  "learn/incidents/automation-incident-response",
                   "learn/incidents/incident-assessment-severity",
                   "learn/incidents/on-call-schedule",
                   "learn/incidents/playbooks"
@@ -1330,7 +1326,6 @@
               "learn/kubernetes/events",
               "learn/kubernetes/klog",
               "learn/kubernetes/logging-best-practices",
-              "learn/kubernetes/monitoring-challenges",
               "learn/kubernetes/node-problem-detector",
               "learn/kubernetes/operators-metrics",
               "learn/kubernetes/structured-logging"
@@ -1410,7 +1405,6 @@
           {
             "group": "Frameworks",
             "pages": [
-              "comparisons/frameworks/playwright-vs-cypress",
               "comparisons/frameworks/playwright-vs-selenium",
               "comparisons/frameworks/playwright-vs-others"
             ]

integrations/alerts/gitlab_alerts.mdx

@@ -27,4 +27,4 @@ Checkly integrates with [GitLab Alerts](https://docs.gitlab.com/ee/operations/in
 
    > Note that we provide a preconfigured message payload but you are free to edit the payload and add more or different variables. Just click the "Edit payload" button and reference the "Help & variables tab".
 
-Congratulations! You have successfully integrated Checkly with GitLab Alerts!
+Congratulations! You have successfully integrated Checkly with GitLab Alerts!

integrations/alerts/slack.mdx

@@ -52,6 +52,21 @@ After this, you can safely delete the deprecated channel.
 
 Checkly requests these Slack permissions for the Checkly Slack app to work within your workspace:
 
+| Permission | Description |
+| --- | --- |
+| `app_mentions:read` | Detects @mentions to start Cloud Agents and respond to requests |
+| `channels:history` | Reads previous messages in threads for extra context |
+| `channels:join` | Automatically joins public channels when invited or requested. |
+| `channels:read` | Accesses channel metadata (IDs and names) to post replies and updates |
+| `chat:write` | Sends status updates and notifications on triggered actions like rerunning checks |
+| `groups:history` | Reads previous messages in private channels for extra context |
+| `groups:read` | Accesses private channel metadata to post responses |
+| `im:history` | Accesses direct message history for extra context |
+| `mpim:history` | Accesses group DM history for multi-participant conversations |
+| `users:read` | Matches Slack users with Checkly accounts for permissions and secure access |
+| `links:read` | Read links for allow-listed domains like [app.checklyhq.com](http://app.checklyhq.com) to provide rich context |
+| `links:write` | Writes rich context for allow-listed domains like [app.checklyhq.com](http://app.checklyhq.com) |
+
 | Permission | Description |
 | :-- | :-- |
 | `app_mentions:read` | Detects @mentions to start Cloud Agents and respond to requests |
@@ -69,4 +84,4 @@ Checkly requests these Slack permissions for the Checkly Slack app to work withi
 
 ## Privacy Policy
 
-For information about how Checkly collects, uses, and protects your data, see our [Privacy Policy](https://checklyhq.com/privacy).
+For information about how Checkly collects, uses, and protects your data, see our [Privacy Policy](https://checklyhq.com/privacy).