Files
composiohq__composio/docs/source.config.ts
T
Rahul Tarak f7397e07ca docs: mark migration guides legacy + timestamp; surface example code & legacy status in llms output (#3775)
Follow-up doc fixes from a re-audit of the June "Pi Slack-bot friction"
report against the current docs. Low-risk changes across the migration
guides, the example `.md` output, and legacy handling.

## 1. Migration guides: selective legacy + a "Written {date}" stamp
Migration guides are point-in-time documents, but not all are legacy.
Two mechanisms, decoupled:
- **`legacy: true`** (existing Legacy badge) — only on guides that
migrate off something dead: **new-sdk** (deprecated v1 SDK) and
**tool-router-beta** (removed experimental tool router).
- **`written: "{Month YYYY}"`** (new frontmatter field, dates from git
creation) — renders a standalone **"Written {date}"** stamp on *every*
guide, independent of legacy. So current guides (direct-to-sessions,
mcp-servers-to-sessions, toolkit-versioning, the hub) show their date
without being mislabeled legacy.

Files: `source.config.ts` (new `written` field),
`components/legacy-badge.tsx` (plain badge again), docs page (badge +
date row), 6 migration guides.

## 2. Real example code now in the `.md`/llms output
`<FileBuildup>` / `<RepoBrowser>` render an example's actual source
(`bot.ts`, `install.ts`, …) interactively, but they're React components
that don't serialize to markdown — so
`examples/general-agent-with-pi.md` (what an agent fetches) had all the
prose and **no code**. `mdxToCleanMarkdown` now resolves them from the
`FILE_BUILDS` registry. That example's `.md` grows **6.5 KB → 34 KB**
with the real
`createSessionTools`/`proxyExecute`/`waitForConnections`/`verifyWebhook`
code. Also fixes standup-slackbot and local-workbench.

## 3. Legacy pages: flag in `.md`, skip the current-pattern guardrail
`getLLMText` now prepends "Legacy · written {date}" (or "Written {date}"
for current-dated pages) to the `.md`, and **skips the "enforce ONLY the
current patterns" guardrail block on legacy pages** — appending it to a
legacy guide contradicted the guide's own older content (e.g. new-sdk
showing `tools.execute()` as the v3 target).

## 4. Note that `subscribe()` uses Pusher under the hood
Short aside on the triggers subscribe doc, for readers on runtimes that
restrict WebSocket clients.

---
🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-09 00:34:50 -07:00

193 lines
6.1 KiB
TypeScript

import {
defineConfig,
defineDocs,
defineCollections,
frontmatterSchema,
metaSchema,
applyMdxPreset,
} from 'fumadocs-mdx/config';
import { transformerTwoslash } from '@shikijs/twoslash';
import { createFileSystemTypesCache } from '@shikijs/vitepress-twoslash/cache-fs';
import { remarkMdxMermaid } from 'fumadocs-core/mdx-plugins';
import { z } from 'zod';
// You can customise Zod schemas for frontmatter and `meta.json` here
// see https://fumadocs.dev/docs/mdx/collections
// Extended schema with keywords for search
const docsSchema = frontmatterSchema.extend({
keywords: z.array(z.string()).optional(),
/** When true, the page shows an "Experimental" badge in the sidebar. */
experimental: z.boolean().optional(),
/** When true, the page shows a "New" badge in the sidebar. */
isNew: z.boolean().optional(),
/** When true, the page shows a "Legacy" badge at the top of the page. */
legacy: z.boolean().optional(),
/** Human-readable date the page/guide was written (e.g. "December 2025").
* Renders a "Written <date>" stamp at the top of the page, independent of the
* `legacy` flag, so time-sensitive guides carry their own date whether or not
* they're legacy. */
written: z.string().optional(),
/** Controls which LLM guardrail set is appended to the .md output.
* - undefined / omitted → default session-based guardrails
* - "direct-execution" → softer guardrails acknowledging this is the low-level API
* - "none" → no guardrails appended */
llmGuardrails: z.enum(['direct-execution', 'none']).optional(),
/** Links rendered in the right-hand "Related" rail under the table of contents. */
related: z
.array(
z.object({
title: z.string(),
href: z.string(),
description: z.string().optional(),
}),
)
.optional(),
/** Presentation metadata for the /examples featured gallery. The card's
* title and description come from `title`/`description`; this controls the
* category lane, toolkit logos, and whether it surfaces in "Featured". */
gallery: z
.object({
/** Category lanes this example belongs to (can be more than one). */
categories: z
.array(
z.enum(['General agents', 'Background agents', 'Coding agents']),
)
.min(1),
/** Toolkit logo slugs (logos.composio.dev/api/<slug>) shown on the card. */
logos: z.array(z.string()).default([]),
/** Surface in the default "Featured" view. */
featured: z.boolean().optional(),
/** Sort order within the grid (lower first). */
order: z.number().optional(),
})
.optional(),
});
export const docs = defineDocs({
dir: 'content/docs',
docs: {
schema: docsSchema,
postprocess: {
includeProcessedMarkdown: true,
},
},
meta: {
schema: metaSchema,
},
});
// Reference docs use defineCollections with custom mdxOptions to exclude twoslash
// (SDK reference docs are auto-generated and don't need type checking)
export const reference = defineDocs({
dir: 'content/reference',
docs: {
schema: docsSchema,
postprocess: {
includeProcessedMarkdown: true,
},
mdxOptions: applyMdxPreset({
// Match the global remark plugins so mermaid diagrams in merged
// api-overviews render (applyMdxPreset replaces, not merges).
remarkPlugins: [remarkMdxMermaid],
rehypeCodeOptions: {
themes: {
light: 'github-light',
dark: 'github-dark',
},
// No twoslash transformer - SDK reference docs skip type checking
},
}),
},
meta: {
schema: metaSchema,
},
});
export const examples = defineDocs({
dir: 'content/examples',
docs: {
schema: docsSchema,
postprocess: {
includeProcessedMarkdown: true,
},
},
meta: {
schema: metaSchema,
},
});
export const toolkits = defineDocs({
dir: 'content/toolkits',
docs: {
schema: docsSchema,
files: ['**/*', '!faq/**'],
postprocess: {
includeProcessedMarkdown: true,
},
},
meta: {
schema: metaSchema,
},
});
export const changelog = defineCollections({
type: 'doc',
dir: 'content/changelog',
postprocess: {
includeProcessedMarkdown: true,
},
schema: frontmatterSchema.extend({
date: z.string().regex(/^\d{4}-\d{2}-\d{2}$/, {
message: 'Date must be in YYYY-MM-DD format (e.g., "2025-12-29")',
}),
}),
});
export default defineConfig({
mdxOptions: {
remarkPlugins: [remarkMdxMermaid],
rehypeCodeOptions: {
themes: {
light: 'github-light',
dark: 'github-dark',
},
// Twoslash for type checking only - no hover UI
transformers:
process.env.NODE_ENV === 'production'
? [
transformerTwoslash({
explicitTrigger: false,
twoslashOptions: {
compilerOptions: {
jsx: 4, // JsxEmit.ReactJSX
jsxImportSource: 'react',
// Twoslash type-checks code blocks in its own virtual TS
// environment, which carries a `baseUrl` default that TS 6
// flags as deprecated (TS5101). Silence it here, mirroring
// the root tsconfig.json, so production builds don't fail.
ignoreDeprecations: '6.0',
// TS 6 no longer auto-includes `@types/node` ambiently the
// way 5.9 did, so code blocks using Node globals (`crypto`,
// `process`, `Buffer`) fail to resolve them (TS2591). Pull
// node types in explicitly to restore that.
types: ['node'],
},
},
typesCache: createFileSystemTypesCache({
dir: '.next/cache/twoslash',
}),
renderer: {
// Empty renderer - type checks but renders nothing
nodeStaticInfo: () => ({}),
nodeError: () => ({}),
nodeQuery: () => ({}),
nodeCompletion: () => ({}),
},
}),
]
: [],
},
},
});