feat(slack): add install + privacy section to integration landing page#4799
Conversation
Adds a hand-authored, slug-keyed landing-content module (separate from the generated integrations.json so it survives regeneration) and renders an install walkthrough + privacy-policy link on integration pages when present. Also refreshes generated docs (data-enrichment entry, icon mappings, tool mdx).
PR SummaryLow Risk Overview The same PR refreshes generated docs/assets: Data Enrichment in the integrations catalog, Reviewed by Cursor Bugbot for commit 90021e7. Configure here. |
Greptile SummaryThis PR adds integration-specific install-walkthrough and privacy-policy sections to the landing page for integrations that opt in via a new
Confidence Score: 5/5Safe to merge — changes are additive content and UI sections with no impact on existing integrations or data flows. The new page sections are purely additive and opt-in; all existing integration pages are unaffected. The data pipeline (landing-content.ts → generate-docs → integrations.json → page) is correctly implemented and idempotent. The IntegrationCtaButton correctly opens the sign-up auth modal. No auth, data, or runtime logic is modified. No files require special attention. The landing-content.ts comment is slightly inaccurate (see inline suggestion) but has no runtime effect. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[landing-content.ts\nhand-authored, slug-keyed] -->|generate-docs.ts bakes content| B[integrations.json\nlandingContent field]
B -->|imported at build time| C[bySlug map]
C -->|integration.landingContent| D[page.tsx]
D -->|landingContent?.install| E[Install Walkthrough Section\nheading + steps + CTA button]
D -->|landingContent?.privacy| F[Privacy Section\nbody + policy link]
E -->|IntegrationCtaButton| G[AuthModal sign-up]
Reviews (3): Last reviewed commit: "refactor(landing): bake integration land..." | Re-trigger Greptile |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@greptile |
|
@cursor review |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 611f55d. Configure here.
…on 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.
|
@greptile |
|
@cursor review |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 90021e7. Configure here.
Summary
landing-content.tsmodule (kept separate from the auto-generatedintegrations.jsonso it survivesgenerate-docsregeneration) and render an install walkthrough + privacy-policy link on integration detail pages when content exists for that slug/privacy— addresses Slack Marketplace landing-page requirements (install instructions behind login + visible privacy link)INTEGRATION_LANDING_CONTENT[slug]), so any integration can opt in; no Slack-specific code in the pagegenerate-docsrefresh (new Data Enrichment entry, icon mappings, and apollo/enrichment/resend/wiza/zoominfo tool docs)Type of Change
Testing
bun run lint,tsc, andbiomepass. Docs generation is idempotent (re-running produces no further changes).integrations.jsonvalidated as JSON.Checklist