docs: hide outdated CLI install paths, reframe as Robusta Classic

The robusta CLI install flow (robusta gen-config / pipx / docker) is
outdated. Drop those paths from the install docs in favor of the SaaS
signup wizard, and reframe non-Holmes/non-SaaS content as Robusta
Classic so the primary docs focus on the AI agent + Robusta Platform
(with HolmesGPT OSS docs living separately at holmesgpt.dev).

- Rename "Other Features" toctree caption to "Robusta Classic"
- Consolidate install pages into a single Install Robusta page
  (drop the all-in-one Prometheus and Build-from-Source variants;
  Holmes users always have an existing observability stack)
- Strip robusta gen-config / robusta-cli references from the
  Slack sink, multi-cluster, and help/troubleshooting pages
- Update conf.py redirects for removed pages

https://claude.ai/code/session_019GQrc8wVq14if8f7F3pp4f

Author: claude

docs/conf.py

@@ -71,7 +71,10 @@
     "developer-guide/actions/findings-api.html": "/master/playbook-reference/actions/develop-actions/findings-api.html",
     "tutorials/my-first-custom-action.html": "/master/playbook-reference/actions/develop-actions/index.html",
     "user-guide/self-hosting.html": "/master/how-it-works/oss-vs-saas.html",
-    "getting-started/installation.html": "/master/setup-robusta/installation/all-in-one-installation.html",
+    "getting-started/installation.html": "/master/setup-robusta/installation/index.html",
+    "setup-robusta/installation/all-in-one-installation.html": "/master/setup-robusta/installation/index.html",
+    "setup-robusta/installation/standalone-installation.html": "/master/setup-robusta/installation/index.html",
+    "setup-robusta/installation/dev-setup.html": "/master/help.html",
     "tutorials/java-troubleshooting.html": "/master/tutorials/application-troubleshooting-java.html",
     "catalog/sinks/index.html": "/master/configuration/sinks/index.html",
     "tutorials/prometheus-enrichment.html": "/master/tutorials/alert-custom-enrichment.html",
@@ -216,7 +219,7 @@
     "playbook-reference/overview.html": "/master/playbook-reference/index.html",
     "playbook-reference/defining-playbooks/playbook-basics.html": "/master/playbook-reference/index.html",
     "how-it-works/alert-builtin-enrichment.html": "/master/playbook-reference/builtin-alert-enrichment.html",
-    "setup-robusta/installation/extend-prometheus-installation.html": "/master/setup-robusta/installation/standalone-installation.html",
+    "setup-robusta/installation/extend-prometheus-installation.html": "/master/setup-robusta/installation/index.html",
     "playbook-reference/defining-playbooks/index.html": "/master/playbook-reference/index.html",
     "configuration/alertmanager-integration/alert-custom-prometheus.html": "/master/configuration/alertmanager-integration/embedded-prometheus.html#creating-custom-prometheus-alerts",
     "configuration/alertmanager-integration/index.html": "/master/configuration/index.html",

docs/configuration/sinks/sinks-development.rst

@@ -27,7 +27,7 @@ Each sink consists of a sink class and a config class. Optionally, helpers are u
 
 To implement a new sink you must:
 
-1. :ref:`Build Robusta from source <Build from Source>`
+1. Clone the `Robusta repo <https://github.com/robusta-dev/robusta>`_ and follow the README to build from source
 2. Add a new Python module inside `src/robusta/core/sinks <https://github.com/robusta-dev/robusta/tree/master/src/robusta/core/sinks>`_ containing your sink’s source code
 3. Implement a sink config class
 4. Implement a sink class

docs/configuration/sinks/slack.rst

@@ -20,14 +20,14 @@ Quick Start
 
 **Option 1: Automatic Setup (Recommended)**
 
-When installing Robusta, run ``robusta gen-config`` and follow the prompts. This automatically configures Slack using our `official
+Sign up for a `free Robusta account <https://platform.robusta.dev/signup>`_ and connect Slack during the signup wizard. This automatically configures Slack using our `official
 Slack app <https://slack.com/apps/A0214S5PHB4-robusta?tab=more_info>`_.
 
 Note: Robusta can only write messages and doesn't require read permissions.
 
 **Option 2: Manual Configuration**
 
-Generate a Slack API key by running ``robusta integrations slack``, then add to your ``generated_values.yaml``:
+Generate a Slack API key on your own, then add it to your ``generated_values.yaml``:
 
 .. code-block:: yaml
 

docs/help.rst

@@ -41,54 +41,12 @@ Issues are organized by installation phase to help you quickly find solutions.
 
    <div style="margin: 20px 0; padding: 15px; background-color: #f0f7ff; border-left: 4px solid #0066cc;">
    <strong>Where are you stuck?</strong><br>
-   • <a href="#phase-1-configuration-generation">Phase 1: Configuration Generation</a> - Issues with robusta gen-config<br>
-   • <a href="#phase-2-helm-installation">Phase 2: Helm Installation</a> - Helm install/upgrade failures<br>
-   • <a href="#phase-3-runtime-issues">Phase 3: Runtime Issues</a> - Alerts not arriving, pods crashing<br>
-   • <a href="#phase-4-integration-issues">Phase 4: Integration Issues</a> - Slack, Prometheus connection problems
+   • <a href="#phase-1-helm-installation">Phase 1: Helm Installation</a> - Helm install/upgrade failures<br>
+   • <a href="#phase-2-runtime-issues">Phase 2: Runtime Issues</a> - Alerts not arriving, pods crashing<br>
+   • <a href="#phase-3-integration-issues">Phase 3: Integration Issues</a> - Slack, Prometheus connection problems
    </div>
 
-Phase 1: Configuration Generation
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Issues when running ``robusta gen-config`` or generating initial configuration.
-
-.. details:: command not found: robusta (CLI not in path)
-
-    1. Determine where the Robusta-cli binary file is located
-
-    .. code-block:: bash
-        :name: cb-find-python-cli-loc
-
-        find / -regex '.*/bin/robusta' 2>/dev/null
-
-    2. Add the path you found (e.g ``/opt/homebrew/bin/``) to your PATH. To do so, find your shell config file ( ~/.profile or ~/.bash_profile or ~/.zshrc etc...) and append the following:
-
-    .. code-block:: bash
-        :name: add-path-var
-
-        export PATH="$PATH:<new-path>"
-
-    3. Reopen the terminal or run:
-
-    .. code-block:: bash
-        :name: cb-refresh-terminal
-
-        source <your-shell-config-file>
-
-    .. admonition:: Alternative Solution
-
-      Instead of modifying PATH, run Robusta commands via the python3 binary: ``python3 -m robusta.cli.main gen-config``
-
-.. details:: SSL certificate errors on Mac OS
-
-    This implies a python package with certificates is missing on your system.
-
-    To fix it, run ``/Applications/Python 3.9/Install Certificates.command``
-
-    For more info see:
-    https://stackoverflow.com/questions/52805115/certificate-verify-failed-unable-to-get-local-issuer-certificate
-
-Phase 2: Helm Installation
+Phase 1: Helm Installation
 ^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Problems when running ``helm install`` command or installing via GitOps.
@@ -128,7 +86,7 @@ Problems when running ``helm install`` command or installing via GitOps.
 
       Follow this guide for :ref:`upgrading CRDs from an older version <Manual Upgrade>`.
 
-Phase 3: Runtime Issues
+Phase 2: Runtime Issues
 ^^^^^^^^^^^^^^^^^^^^^^^
 
 Issues after installation when pods are running but not working correctly.
@@ -252,7 +210,7 @@ Holmes
 
         See :ref:`Using Existing Secrets <Reading the Robusta UI Token from a secret in HolmesGPT>` to configure Holmes to read the ``token``
 
-Phase 4: Integration Issues
+Phase 3: Integration Issues
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Problems with external service integrations after Robusta is running.

docs/index.rst

@@ -43,7 +43,7 @@
 
 .. toctree::
    :maxdepth: 4
-   :caption: Other Features
+   :caption: Robusta Classic
    :hidden:
 
    Send Alerts to Robusta <configuration/index>