From b2e20aa93446db8260907c27d6b9e65d600ffd57 Mon Sep 17 00:00:00 2001 From: Manthan Date: Mon, 2 Mar 2026 09:42:18 -0800 Subject: [PATCH] Add design-partner flow and 3-step onboarding path --- docs/docs.html | 29 ++++++++++ docs/index.html | 96 ++++++++++++++++++++++++++++++--- docs/script.js | 40 ++++++++++++++ docs/styles.css | 141 ++++++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 299 insertions(+), 7 deletions(-) diff --git a/docs/docs.html b/docs/docs.html index e927c75..b03cf32 100644 --- a/docs/docs.html +++ b/docs/docs.html @@ -68,6 +68,7 @@ @@ -267,6 +268,34 @@

Full Configuration Reference

host: 0.0.0.0 +

Opinionated Onboarding: AWS + Kubernetes + PagerDuty + Slack

+

Use this path if you want the fastest practical production setup for one on-call team.

+ +

Step 1: Install the CLI and verify cloud/cluster access

+

Install RunbookAI, then validate AWS identity and Kubernetes connectivity. Reference: Installation, AWS integration, Kubernetes integration.

+
+
Terminal
+
npm install -g @runbook-agent/runbook
+aws sts get-caller-identity
+kubectl config current-context
+
+ +

Step 2: Run setup wizard with this integration profile

+

Run the wizard and enable AWS, Kubernetes, PagerDuty, and Slack when prompted. Reference: Configuration, PagerDuty, Slack.

+
+
Terminal
+
runbook init
+
+ +

Step 3: Validate incident workflow end to end

+

Verify infra access, investigate a PagerDuty incident, and start Slack intake. Reference: runbook status, runbook investigate, runbook slack-gateway.

+
+
Terminal
+
runbook status
+runbook investigate PD-12345
+runbook slack-gateway --mode socket
+
+

Your First Query

Test your installation by running a simple infrastructure query:

diff --git a/docs/index.html b/docs/index.html index 5d2ba59..d701f30 100644 --- a/docs/index.html +++ b/docs/index.html @@ -53,6 +53,8 @@ + +
+
+
+ +

Pick your path in under 60 seconds

+
+ +
+
+ Design Partner +

Share your stack and incident pain

+

Tell us your role, infra setup, top incident pain, and how to reach you. We use this to prioritize roadmap work.

+ Open intake form +
+ +
+ Onboarding +

Use the AWS + Kubernetes + PagerDuty + Slack path

+

Follow an opinionated 3-step setup sequence with exact commands and links to the right docs sections.

+ Open 3-step onboarding +
+
+
+
+ + +
+
+
+ +

Tell us where incidents hurt

+
+ +
+
+

We are onboarding a small number of teams running production workloads on AWS and Kubernetes. Share a few details and we will follow up with a focused setup session.

+

If the form submit does not open your mail app, use the fallback link below.

+
+ +
+ + + + + + + + +
+ + Mailto fallback +
+

+
+
+
+
+