mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
cogwirrel
24b981de16
The @ag-ui/aws-strands TypeScript adapter ships alongside the Python ag_ui_strands package but the docs only showed Python snippets. Add a TypeScript tab next to every Python snippet (Python default, `persist` on the tab group so a reader's choice sticks across pages) covering: - quickstart: project init, install, agent file, run command - frontend-tools: @tool stub + createStrandsApp server - shared-state (read + write): StrandsAgentConfig.stateContextBuilder - generative-ui tool-rendering: backend tool definition - generative-ui state-rendering: ToolBehavior.stateFromArgs Also applied to the parallel showcase/shell-docs tree. Non-code pages (deploy-agentcore, copilot-runtime, inspector, etc.) remain untouched since they either re-export shared snippets or have no framework code.
fumadocs-test
This is a Next.js application generated with Create Fumadocs.
Run development server:
npm run dev
# or
pnpm dev
# or
yarn dev
Open http://localhost:3000 with your browser to see the result.
Learn More
To learn more about Next.js and Fumadocs, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
- Fumadocs - learn about Fumadocs
Vercel Deployment with Git LFS
Docs assets are tracked with Git LFS. To ensure production builds always receive
real asset bytes (not pointer files), deploy docs through GitHub Actions using
.github/workflows/deploy_docs_vercel.yml.
Required GitHub repository secrets:
VERCEL_TOKENVERCEL_ORG_IDVERCEL_PROJECT_ID_DOCS
PR previews:
.github/workflows/deploy_docs_vercel_preview.ymldeploys docs previews for non-fork pull requests.- The workflow posts/updates a sticky PR comment with a clickable
Open Docs Previewlink.
Recommended Vercel project setting:
- Disable automatic Git-based deployments for the docs project and let the GitHub Actions workflow handle production deploys.