Files
composiohq__composio/docs
Sarah Simionescu bfcd99447f docs(white-labeling): document the Connect Link theme editor (PRDE-1196)
The Auth Screen branding settings now ship a full theme editor (colors,
typefaces, geometry, and per-element styling with a live preview and JSON
mode), so both white-labeling guides need to cover it.

- Split "Customizing the Connect Link" into Logo and name (Branding tab)
  and Colors, fonts, and per-element styling (Styling tab).
- Align to the shipped UI: White Labeling nav item, Branding/Styling tabs,
  Typefaces, JSON toggle, Save Changes, and the enforced-contrast gate.
- Add the editor screenshot; drop the stale branding-only walkthrough video.
- Mirror the section into the legacy direct-execution page.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-08-19 17:22:28 -07:00
..

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 // @noErrors to skip checking for partial snippets
  • Use // ---cut--- to hide setup code from output
  • Run bun run build locally to validate before pushing

See CLAUDE.md for detailed patterns and troubleshooting.

Docs search uses Algolia when NEXT_PUBLIC_ALGOLIA_SEARCH_API_KEY is set; otherwise it falls back to the local Fumadocs /api/search endpoint for development and tests. The sync script builds a first-party index from MDX/OpenAPI/toolkit data (no crawler required), splits long pages into section-sized records, configures searchable attributes/custom ranking/distinct, requests clickAnalytics, and sends search result view/click events with search-insights.

NEXT_PUBLIC_ALGOLIA_APP_ID=62HI9PQZ1L # optional; default shown
NEXT_PUBLIC_ALGOLIA_SEARCH_API_KEY=...
NEXT_PUBLIC_ALGOLIA_INDEX_NAME=docs_composio # optional; default shown

Sync the Algolia index with an admin key:

ALGOLIA_APP_ID=62HI9PQZ1L
ALGOLIA_ADMIN_API_KEY=...
ALGOLIA_INDEX_NAME=docs_composio bun run sync:search

Preview the generated records or test live relevance:

bun run sync:search --dry-run --samples
ALGOLIA_SEARCH_API_KEY=... bun run test:search "oauth auth config" "gmail send email"

Commands

Command Description
bun run dev Dev server
bun run build Production build (validates TS code blocks)
bun run types:check Type check
bun run sync:search Sync docs search records to Algolia
bun run test:search Query the configured Algolia index from the terminal