docs(readme): improve open source positioning

[oalami]

Summary

• Refresh the README introduction around CrewAI’s open-source framework strengths: Crews, Flows, Python-native control, and production-ready multi-agent workflows
• Add a link to the CrewAI Open Source page
• Clarify the boundary between the open-source framework and CrewAI AMP
• Update feature, FAQ, and “When to Use CrewAI” copy for clearer messaging

Summary by CodeRabbit

• Documentation
  • Rewrote the README’s marketing, overview, and FAQ content for clearer positioning.
  • Updated the navigation and table of contents, including added Examples links and removed comparison-focused entries.
  • Refreshed “Why CrewAI,” “Key Features,” and “When to Use CrewAI” sections with updated messaging and guidance.
  • Revised several FAQ entries and added a new question about whether CrewAI is standalone.

[corridor-security]

Summary: This PR updates README documentation and external links without changing executable code, authentication, authorization, data handling, or runtime behavior.

Risk: Low risk. No exploitable security vulnerabilities were identified because the changes are documentation-only and do not introduce new attack surfaces or modify security boundaries.

[coderabbitai]

📝 Walkthrough

Walkthrough

README text was rewritten to emphasize open-source positioning, update the top navigation and section order, replace comparison content with usage guidance, and revise several FAQ answers.

Changes

README copy and FAQ rewrite

Layer / File(s)	Summary
Top navigation and intro copy README.md	Updates the top navigation, hero copy, AMP Suite text, and table of contents to match the new open-source framing and examples section order.
Why CrewAI and key features README.md	Rewrites the Why CrewAI section and the Key Features section with new capability, customization, and production-oriented bullets.
When to use and FAQ navigation README.md	Replaces the comparison section with When to Use CrewAI, and updates the FAQ navigation by adding the standalone-framework question and removing LangChain comparison entries.
FAQ answers README.md	Rephrases the CrewAI definition, standalone-framework scope, production readiness, and scalability FAQ answers.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the README update focused on improving CrewAI’s open-source positioning.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/readme-positioning

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

🧹 Nitpick comments (1)

README.md (1)

138-146: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Inconsistent capitalization in feature bullets.

The bullet list mixes sentence case ("Purpose-built architecture") with title case ("High Performance", "Flexible Low-Level Customization", etc.). Standardize to one style—prefer sentence case for readability.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 138 - 146, The feature bullets in the README use
mixed capitalization styles, so standardize them to one consistent style. Update
the bullet list under the CrewAI overview to use sentence case throughout, and
keep the wording aligned with the existing intent in the surrounding
description. Use the current bullet entries and the final CrewAI summary
sentence as anchors while editing to ensure the section reads consistently.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@README.md`:
- Around line 138-146: The feature bullets in the README use mixed
capitalization styles, so standardize them to one consistent style. Update the
bullet list under the CrewAI overview to use sentence case throughout, and keep
the wording aligned with the existing intent in the surrounding description. Use
the current bullet entries and the final CrewAI summary sentence as anchors
while editing to ensure the section reads consistently.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 53d73650-5b89-4712-8612-a4420c3cbf63

📥 Commits

Reviewing files that changed from the base of the PR and between e716f3d and 21efe0e.

📒 Files selected for processing (1)

• README.md