mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-02 13:48:09 +00:00
93dafe2637
Switch docs.crewai.com from navigation-only versioning (every version selector entry rendered the same docs/<lang>/* source files) to Mintlify's directory-based versioning so each version selector entry renders its own snapshot. Add an "Edge" channel under docs/edge/<lang>/* that always reflects main HEAD for unreleased work, eliminating pre-release leakage onto frozen release labels. External links to canonical /<lang>/* URLs are preserved via wildcard redirects that always land on the current default version. Layout: - docs/edge/<lang>/* rolling source (you edit here) - docs/edge/enterprise-api.*.yaml - docs/v<X.Y.Z>/<lang>/* frozen, immutable snapshots - docs/v<X.Y.Z>/enterprise-api.*.yaml - docs/images/ shared, append-only - docs/docs.json nav + redirects URLs follow the Mintlify-idiomatic shape: /edge/<lang>/<page> for Edge, /v<X.Y.Z>/<lang>/<page> for every frozen snapshot. The wildcard redirects /<lang>/:slug* -> /<default>/<lang>/:slug* keep stale links working, and every freeze rewrites them (plus all per-section/per-page redirects) so destinations always resolve to the current default without depending on a second redirect hop. Release flow integration (devtools release): - New module crewai_devtools.docs_versioning.freeze() materialises docs/v<X.Y.Z>/ from docs/edge/, rewrites openapi: refs inside the snapshot, inserts the version into every language block in docs.json, and refreshes all redirect destinations. - _update_docs_and_create_pr() in cli.py now calls that freeze during Phase 2 of devtools release. Edge changelogs are updated first (so the snapshot freeze picks them up), then the snapshot is staged alongside docs.json, branched as docs/freeze-v<X.Y.Z>, and the PR is titled [docs-freeze] docs: snapshot and changelog for v<X.Y.Z> — the title prefix the new CI guard reads. - The PR still gates tag, GitHub release, PyPI publish, and the enterprise release as before; no new PRs are added. - Pre-releases (1.X.YaN, 1.X.YbN, ...) skip the snapshot — they ride Edge — and the docs PR title omits the [docs-freeze] prefix. - docs_check (AI-generated docs scaffolding) writes to docs/edge/<lang>/* so newly-generated unreleased docs land in Edge and never accidentally touch a frozen snapshot. Migration scripts (one-shot): - scripts/docs/freeze_historical_versions.py reconstructs all 16 historical snapshots (v1.10.0 .. v1.14.7) from git tags via git archive | tar, rewriting openapi: MDX refs so each snapshot reads its own enterprise-api YAML rather than the live one. - scripts/docs/prefix_version_paths.py one-shot-migrates docs.json: rewrites every page path in 16 versioned blocks to point under docs/v<X.Y.Z>/, inserts a new Edge entry per language, tags v1.14.7 as Latest (default), prunes pages whose target file doesn't exist in the snapshot (e.g. docs/ar/ didn't exist before v1.12.0), and writes the wildcard + per-section redirects. - scripts/docs/freeze_current_edge.py is now a thin CLI wrapper around docs_versioning.freeze for manual one-off freezes (e.g. retroactively snapshotting a forgotten release). CI guards (.github/workflows/docs-snapshots.yml): - Frozen snapshots under docs/v[0-9]*/ are immutable; only PRs whose title contains [docs-freeze] (i.e. release-cut PRs generated by devtools release or the manual wrapper) may modify them. - Images under docs/images/ are append-only since snapshots share a single image directory. Deleting or renaming an image breaks every historical snapshot that still references it. Restored docs/images/crewai-otel-export.png from PR #3673; it was deleted in PR #4908 but v1.10.0 / v1.10.1 snapshots still reference it. Restoring instead of editing the snapshots preserves historical rendering fidelity and validates the new append-only rule retroactively. Tests: - lib/devtools/tests/test_docs_versioning.py covers the freeze: file copy, openapi rewrite, version insertion, default demotion, redirect upserts, per-section redirect rewriting, idempotency, and invalid inputs. Verified locally with mintlify broken-links: 0 broken links across the full site (Edge + 16 frozen versions, 4 locales). AGENTS.md (repo root) is the contributor guide for the new model; RELEASING.md is the release-cut runbook; README's Contribution section links to both. Co-authored-by: Cursor <cursoragent@cursor.com>
89 lines
2.9 KiB
Plaintext
89 lines
2.9 KiB
Plaintext
---
|
|
title: "Crew Studio"
|
|
description: "AI 보조, 비주얼 에디터, 통합 테스트로 새로운 자동화를 구축하세요."
|
|
icon: "pencil"
|
|
mode: "wide"
|
|
---
|
|
|
|
## 개요
|
|
|
|
Crew Studio는 자연어와 시각적 워크플로 에디터로 처음부터 자동화를 만드는 인터랙티브한 AI 보조 작업 공간입니다.
|
|
|
|
<Frame>
|
|
|
|
</Frame>
|
|
|
|
## 프롬프트 기반 생성
|
|
|
|
- 원하는 자동화를 설명하면, AI가 에이전트/태스크/도구를 생성합니다.
|
|
- 마이크 아이콘으로 음성 입력을 사용할 수 있습니다.
|
|
- 공통 사용 사례용 프롬프트 템플릿으로 시작할 수 있습니다.
|
|
|
|
<Frame>
|
|
|
|
</Frame>
|
|
|
|
## 비주얼 에디터
|
|
|
|
캔버스는 노드/엣지 형태로 플로우를 표현하며, 세 개의 보조 패널로 코드 없이 쉽게 구성할 수 있습니다 (일명 "vibe coding AI Agents"):
|
|
|
|
- **AI Thoughts (좌측)**: 설계 중 스트리밍 추론
|
|
- **Canvas (중앙)**: 에이전트/태스크 노드와 연결
|
|
- **Resources (우측)**: 드래그앤드롭 컴포넌트 (에이전트, 태스크, 도구)
|
|
|
|
드래그앤드롭으로 캔버스를 구성하거나, 채팅 섹션으로 에이전트를 생성할 수 있으며 두 방식은 상태를 공유합니다.
|
|
|
|
<Frame>
|
|
|
|
</Frame>
|
|
|
|
## 실행 & 디버깅
|
|
|
|
<b>Execution</b> 뷰로 전환하여 실행을 관찰하세요:
|
|
|
|
- 이벤트 타임라인
|
|
- 상세 로그 (Details, Messages, Raw Data)
|
|
- 게시 전 로컬 실행
|
|
|
|
<Frame>
|
|
|
|
</Frame>
|
|
|
|
## 게시 & 내보내기
|
|
|
|
- <b>Publish</b>로 라이브 자동화 배포
|
|
- <b>Download</b>로 소스 ZIP 다운로드 (로컬 개발용)
|
|
|
|
<Frame>
|
|
|
|
</Frame>
|
|
|
|
게시 후 **Options** 드롭다운에서 `chat with this crew`, `Export React Component`, `Export as MCP`를 사용할 수 있습니다.
|
|
|
|
<Frame>
|
|
|
|
</Frame>
|
|
|
|
## 모범 사례
|
|
|
|
- Studio에서 빠르게 반복하고, 안정화 후 게시
|
|
- 도구 권한은 최소한으로 제한
|
|
- Traces로 동작/성능 검증
|
|
|
|
## 관련 문서
|
|
|
|
<CardGroup cols={4}>
|
|
<Card title="Crew Studio 활성화" href="/ko/enterprise/guides/enable-crew-studio" icon="palette">
|
|
Crew Studio를 활성화하세요.
|
|
</Card>
|
|
<Card title="크루 빌드" href="/ko/enterprise/guides/build-crew" icon="paintbrush">
|
|
크루를 빌드하세요.
|
|
</Card>
|
|
<Card title="크루 배포" href="/ko/enterprise/guides/deploy-to-amp" icon="rocket">
|
|
GitHub 또는 ZIP 파일로 크루 배포.
|
|
</Card>
|
|
<Card title="React 컴포넌트 내보내기" href="/ko/enterprise/guides/react-component-export" icon="download">
|
|
React 컴포넌트를 내보내세요.
|
|
</Card>
|
|
</CardGroup>
|