Remove Slack provider from connectors docs (matches ui-ex#5017)#219
Remove Slack provider from connectors docs (matches ui-ex#5017)#219kcmartin wants to merge 2 commits into
Conversation
The dashboard is hiding the Slack connector provider until the non-Fly- workspace bug (superfly/ui-ex#5017) is fixed, so the docs should stop documenting Slack as a provider. Per jae, GitHub becomes the permanent running example throughout the connectors page; only the two provider- table rows get restored when the bug lands. - Drop the 'Slack as User' and 'Slack as Bot' rows from the provider table - Remove Slack from the OAuth setup bullet (GitHub remains) - Switch the gateway curl example to a GitHub repo-issues POST - Switch the OAuth authorize example to GitHub scopes (repo, read:org) - Reword the access-policy prose and endpoint patterns to GitHub - Replace the Slack agent-task example with a GitHub PR comment - Drop Slack from intro and coding-agent prose
|
Companion restore issue: #220 (restore the two provider-table rows when |
Preview Deployment
Commit: |
Lighthouse Results
|
E2E Test Results✅ Tests success Ran against: https://pr-219-superfly-sprites-docs.fly.dev |
|
Slug confirmed: the public API reference ( |
|
@jbellerb here's the companion PR for your UI change. https://github.com/superfly/ui-ex/pull/5017 |
The four connector screenshots were confirmatory, not load-bearing: each sat directly below prose that already described it. They were also dark- only (the docs default to light), stale-prone, and Slack-contaminated pending ui-ex#5017, which would have meant a screenshot-retaking follow-up. Remove all four images and the now-unreferenced PNG assets, and stitch the one sentence that introduced the add-connection screenshot so it reads as continuous prose. No factual content is lost.
|
Added a second commit: dropped all four dashboard screenshots (list / add-menu / detail / managed) in favor of the prose that already described them, and deleted the now-unreferenced PNGs. This removes the screenshot-retaking follow-up — issue #220 is now just the two provider-table rows. |
|
That's fine! The screenshots needed updating anyways since they're of the old dashboard. The text is clear enough without them. |
2 participants
Two related cleanups to the connectors page (
src/content/docs/concepts/connectors.mdx), no other page touched.1. Remove Slack as a documented provider
The dashboard is hiding the Slack connector provider until
superfly/ui-ex#5017(private) is fixed — Slack connectors currently only work for the Fly workspace. This makes the docs match that state. Per jae, GitHub becomes the permanent running example; when the bug lands, only the two provider-table rows come back (tracked in #220).POST /v1/gateway/github/<conn>/repos/acme/website/issues), OAuth authorize (/v1/oauth/github/authorize?scopes=repo,read:org), endpoint patterns (/repos/...), update-policy labels (["github"]), and the agent-task example (GitHub PR comment).Gateway slug
githubconfirmed against the API reference (providerenum:"slack" | "slack_bot" | "github" | "openrouter" | "custom_api").2. Drop the dashboard screenshots in favor of prose
The four connector screenshots (
list,add-menu,detail,managed) were confirmatory, not load-bearing — each sat directly below prose that already described it. They were also dark-only (docs default to light), stale-prone, and Slack-contaminated pending ui-ex#5017 (which would otherwise have needed a screenshot-retaking follow-up).![...]embeds and deleted the now-unreferenced PNG assets underpublic/images/connectors/.This removes the earlier "screenshots need retaking after ui-ex#5017" follow-up entirely.
Verification
pnpm buildandpnpm lintclean. The built page contains zeroslackand no image references. Whole-reposlackgrep: all hits were on this page (no out-of-page references).Merge when
ui-ex#5017deploys, not before (the Slack-removal half must match the dashboard; the screenshot cleanup is independent but folded into this PR).