refactor(landing): bake integration landing content into generated json via docs-gen

Moves landing content (install walkthrough + privacy) out of a render-time augment and into the generation pipeline: generate-docs reads the pure-data content map and writes landingContent into integrations.json, so the page reads a single source (integration.landingContent). Canonical types live in integrations/data/types.ts.

Author: waleedlatif1

apps/sim/app/(landing)/integrations/(shell)/[slug]/page.tsx

@@ -9,7 +9,6 @@ import { TemplateCardButton } from '@/app/(landing)/integrations/(shell)/[slug]/
 import { IntegrationIcon } from '@/app/(landing)/integrations/components/integration-icon'
 import { blockTypeToIconMap } from '@/app/(landing)/integrations/data/icon-mapping'
 import integrations from '@/app/(landing)/integrations/data/integrations.json'
-import { INTEGRATION_LANDING_CONTENT } from '@/app/(landing)/integrations/data/landing-content'
 import type { AuthType, FAQItem, Integration } from '@/app/(landing)/integrations/data/types'
 import { TEMPLATES } from '@/app/workspace/[workspaceId]/home/components/template-prompts/consts'
 
@@ -218,7 +217,7 @@ export default async function IntegrationPage({ params }: { params: Promise<{ sl
   const { name, description, longDescription, bgColor, docsUrl, operations, triggers, authType } =
     integration
 
-  const landingContent = INTEGRATION_LANDING_CONTENT[slug]
+  const landingContent = integration.landingContent
 
   const IconComponent = blockTypeToIconMap[integration.type]
   const faqs = buildFAQs(integration)

apps/sim/app/(landing)/integrations/data/integrations.json

@@ -13306,7 +13306,35 @@
     "authType": "oauth",
     "category": "tools",
     "integrationTypes": ["communication", "developer-tools"],
-    "tags": ["messaging", "webhooks", "automation"]
+    "tags": ["messaging", "webhooks", "automation"],
+    "landingContent": {
+      "install": {
+        "heading": "Add Sim to your Slack workspace",
+        "intro": "Sim connects to Slack through Slack’s official OAuth flow. The “Add to Slack” button lives inside your Sim account (after sign-in) — connect from there and the Sim bot is installed in your Slack workspace. The steps below show exactly how to reach it.",
+        "steps": [
+          {
+            "title": "Create your free Sim account",
+            "body": "Sign up at sim.ai — no credit card required."
+          },
+          {
+            "title": "Add a Slack block",
+            "body": "Open a workflow, drag in a Slack block, and open its credential dropdown."
+          },
+          {
+            "title": "Connect Slack",
+            "body": "Click Connect Slack, choose your workspace, and approve the requested permissions. This installs the Sim bot in your Slack workspace."
+          },
+          {
+            "title": "Invite the bot and build",
+            "body": "Invite the Sim bot to the channels it should act in, pick a Slack action, wire it into your agent, and run."
+          }
+        ]
+      },
+      "privacy": {
+        "body": "Sim requests only the Slack permissions its actions and triggers need, and never shows private channel names or messages to people who are not members of those channels in Slack.",
+        "href": "/privacy"
+      }
+    }
   },
   {
     "type": "smtp",

apps/sim/app/(landing)/integrations/data/landing-content.ts

@@ -1,32 +1,12 @@
 /**
- * Hand-authored, integration-specific landing content that augments the
- * generated `integrations.json`. Kept in a separate module so it survives
- * regeneration by `scripts/generate-docs.ts`. Keyed by integration slug;
- * the integration detail page renders these sections only when present.
+ * Hand-authored, integration-specific landing content, keyed by integration
+ * slug. This is a pure-data generation input: `scripts/generate-docs.ts` reads
+ * it and bakes the matching entry into `integrations.json`, so the landing page
+ * consumes a single source (`integration.landingContent`) with no render-time
+ * augmentation. Has no app imports so the build script can import it safely.
  */
 
-export interface IntegrationInstallStep {
-  title: string
-  body: string
-}
-
-export interface IntegrationLandingContent {
-  /**
-   * Install walkthrough for OAuth apps whose connection lives behind sign-in.
-   * Provides the "Add to {app}" instructions that app marketplaces require
-   * when the install button sits behind a login.
-   */
-  install?: {
-    heading: string
-    intro: string
-    steps: IntegrationInstallStep[]
-  }
-  /** Short data-handling summary shown next to a privacy-policy link. */
-  privacy?: {
-    body: string
-    href: string
-  }
-}
+import type { IntegrationLandingContent } from '@/app/(landing)/integrations/data/types'
 
 export const INTEGRATION_LANDING_CONTENT: Record<string, IntegrationLandingContent> = {
   slack: {

apps/sim/app/(landing)/integrations/data/types.ts

@@ -19,6 +19,29 @@ export interface FAQItem {
   answer: string
 }
 
+export interface IntegrationInstallStep {
+  title: string
+  body: string
+}
+
+export interface IntegrationLandingContent {
+  /**
+   * Install walkthrough for OAuth apps whose connection lives behind sign-in.
+   * Provides the "Add to {app}" instructions that app marketplaces require
+   * when the install button sits behind a login.
+   */
+  install?: {
+    heading: string
+    intro: string
+    steps: IntegrationInstallStep[]
+  }
+  /** Short data-handling summary shown next to a privacy-policy link. */
+  privacy?: {
+    body: string
+    href: string
+  }
+}
+
 export interface Integration {
   type: string
   slug: string
@@ -36,4 +59,5 @@ export interface Integration {
   category: string
   integrationTypes?: string[]
   tags?: string[]
+  landingContent?: IntegrationLandingContent
 }

scripts/generate-docs.ts

@@ -1,7 +1,7 @@
 #!/usr/bin/env ts-node
 import fs from 'fs'
 import path from 'path'
-import { fileURLToPath } from 'url'
+import { fileURLToPath, pathToFileURL } from 'url'
 import { glob } from 'glob'
 
 console.log('Starting documentation generator...')
@@ -183,6 +183,7 @@ interface IntegrationEntry {
   category: string
   integrationTypes?: string[]
   tags?: string[]
+  landingContent?: Record<string, unknown>
 }
 
 /**
@@ -665,6 +666,19 @@ async function writeIntegrationsJson(iconMapping: Record<string, string>): Promi
 
     const triggerRegistry = await buildTriggerRegistry()
     const { desc: toolDescMap, name: toolNameMap } = await buildToolDescriptionMap()
+
+    // Hand-authored, integration-specific landing content (install walkthrough,
+    // privacy blurb), keyed by slug. Imported as pure data — its only import is
+    // type-only and erased at runtime — and baked into the entries below so the
+    // landing page reads a single source instead of augmenting at render time.
+    const landingContentModule = await import(
+      pathToFileURL(path.join(LANDING_INTEGRATIONS_DATA_PATH, 'landing-content.ts')).href
+    )
+    const landingContentMap = (landingContentModule.INTEGRATION_LANDING_CONTENT ?? {}) as Record<
+      string,
+      Record<string, unknown>
+    >
+
     const integrations: IntegrationEntry[] = []
     const seenBaseTypes = new Set<string>()
     const blockFiles = (await glob(`${BLOCKS_PATH}/*.ts`)).sort()
@@ -778,6 +792,7 @@ async function writeIntegrationsJson(iconMapping: Record<string, string>): Promi
               }
             : {}),
           ...(config.tags ? { tags: config.tags } : {}),
+          ...(landingContentMap[slug] ? { landingContent: landingContentMap[slug] } : {}),
         })
       }
     }