Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs: document FAQ section decisions in toolkits ADR
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sushmithamallesh committed
Feb 9, 2026 at 12:55 UTC
e33bc37354f0491d07c3766d6e37bf83dc906c96
1 file changed
+23
docs/.claude/decisions/toolkits.md
+23
@@ -192,6 +192,29 @@ Run: `bun run generate:toolkits`
192
193
---
194
195
+## FAQ Section
196
+
197
+### How It Works
198
+- Per-toolkit FAQ sourced from plain markdown files in `content/toolkit-faq/{toolkit-slug}.md`
199
+- `##` headings are questions, body text is the answer
200
+- Markdown is converted to HTML at build time using `remark-parse` + `remark-rehype` + `hast-util-to-html` (all transitive deps from Fumadocs, no new packages)
201
+- Rendered as Fumadocs `Accordion` components between the Header and Auth Details sections
202
+- Only shown if a `.md` file exists for that toolkit and has valid Q&A content
203
+
204
+### Copy Page / LLM Markdown
205
+- FAQ content is also included in the `/toolkits/{slug}.md` LLM route output
206
+- Heading levels are bumped (`##` → `###`) so questions are children of the `## Frequently Asked Questions` section
207
+
208
+### No Sitemap Impact
209
+- FAQ is embedded within existing toolkit pages — no new URLs are created
210
+- No changes to sitemap or routing
211
+
212
+### Adding FAQ Content
213
+- Create/edit `content/toolkit-faq/{toolkit-slug}.md` — no code changes needed
214
+- Empty files or files with no valid `##` headings are safely ignored
215
+
216
+---
217
+
218
## Future: CI Hooks
219
220
- Trigger docs regeneration from toolkit repo changes