mirror of
https://github.com/ComposioHQ/composio.git
synced 2026-09-22 11:46:35 +08:00
Alberto Schiabel
00803f09e6
# Description Adds five FAQs to the Slack toolkit FAQ snippet (`docs/content/toolkits/faq/slack.md`) covering the most common Slack OAuth install/approval friction points: 1. Why users see "This app isn't listed in the Slack Marketplace…" during install 2. Whether workspace owner is required to install the app 3. Why Slack asks the user to submit a request during auth 4. How a workspace member can complete the connection without permissions/approvals 5. The recommended solution (custom OAuth app) These FAQs are placed right after the existing "How do I set up custom OAuth credentials for Slack?" entry, since they're all about the OAuth install flow and the resolution path consistently points back to using a custom OAuth app. Format follows the existing snippet style: plain markdown, `## Question?` headers, paragraph or short bullet-list answers, `**bold**` for UI/setting names, relative/external links matching what's already in the file. No frontmatter (matches the rest of `content/toolkits/faq/`). # How did I test this PR - Read existing FAQ snippets (`slack.md`, `gmail.md`, `notion.md`) to match style — short headers, `**bold**` for Slack setting names, no Fumadocs components, ends with `---` - Verified the file structure is unchanged: 5 new `## Question?` sections inserted between the existing custom-OAuth question (line 9) and the Slack-vs-Slackbot question; closing `---` separator still present at EOF - All links in the new content point to `https://composio.dev/auth/slack`, which already exists in the same file — no new link surface introduced - Confirmed `bun run scripts/validate-links.ts` failure is pre-existing on `origin/next` (sandbox dependency mismatch on `fumadocs-core/content/md/frontmatter`), not caused by this change - No code blocks added, so Twoslash type-check is not affected Triggered by: uday@composio.dev | Source: slack Session: https://zen-api-production-4c98.up.railway.app/dashboard/#/chat/zen-7f4c8629aad8
Composio Docs
Documentation site for Composio, built with Fumadocs.
Getting Started
bun install
bun run dev
Open http://localhost:3000.
Project Structure
docs/
├── app/ # Next.js app router
├── content/ # MDX content
│ ├── docs/
│ ├── examples/
│ ├── changelog/
│ └── reference/
├── components/ # React components
├── lib/ # Utilities
└── public/ # Static assets
Adding Content
Create an .mdx file in content/, add frontmatter, then add to meta.json:
---
title: Page Title
description: Brief description
---
Content here...
Components
<Tabs items={['Python', 'TypeScript']}>
<Tab value="Python">...</Tab>
<Tab value="TypeScript">...</Tab>
</Tabs>
<Callout type="info">Note</Callout>
<Cards>
<Card title="Title" href="/path" />
</Cards>
Sidebar
Each folder has meta.json for ordering:
{
"pages": ["page-one", "page-two"]
}
TypeScript Code Blocks
All TypeScript code blocks in MDX files are type-checked at build time using Twoslash. This ensures docs stay in sync with the SDK.
- Use
// @noErrorsto skip checking for partial snippets - Use
// ---cut---to hide setup code from output - Run
bun run buildlocally to validate before pushing
See CLAUDE.md for detailed patterns and troubleshooting.
Commands
| Command | Description |
|---|---|
bun run dev |
Dev server |
bun run build |
Production build (validates TS code blocks) |
bun run types:check |
Type check |