Update why.md#199
Conversation
Edited to align with overall messaging
sharya-unamboowe
requested review from
KavinduZoysa,
NipunaRanasinghe,
anupama-pathirage and
rosensilva
as code owners
|
|
|
Note
|
| Cohort / File(s) | Summary |
|---|---|
Documentation Updates en/docs/get-started/why.md |
Rewrote opening value proposition to explicitly list AI agents, APIs, data, and events; updated connector count from 200+ to 600+; clarified Central to Ballerina Central. |
Estimated code review effort
🎯 1 (Trivial) | ⏱️ ~2 minutes
Poem
🐰 A rabbit hops through lines so bright,
Six hundred connectors shining light!
From generic prose to specifics clear—
AI agents, APIs, data dear,
And events flowing, far and near! ✨
🚥 Pre-merge checks | ✅ 3 | ❌ 2
❌ Failed checks (1 warning, 1 inconclusive)
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Description check | The description only includes the phrase 'Edited to align with overall messaging' followed by the template structure with all sections left unfilled with placeholder text. | Complete the required sections with actual details: fill in Purpose, Goals, Approach, and other relevant sections based on the changes made to why.md, rather than leaving only template placeholders. | |
| Title check | ❓ Inconclusive | The title 'Update why.md' is vague and does not convey the specific content changes made to the file. | Use a more descriptive title that highlights the main changes, such as 'Update why.md with expanded connector count and messaging focus' or similar. |
✅ Passed checks (3 passed)
| Check name | Status | Explanation |
|---|---|---|
| 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. |
✏️ Tip: You can configure your own custom pre-merge checks in the settings.
✨ Finishing Touches
🧪 Generate unit tests (beta)
- Create PR with unit tests
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.
Review rate limit: 0/1 reviews remaining, refill in 60 minutes.Comment @coderabbitai help to get the list of available commands and usage tips.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@en/docs/get-started/why.md`:
- Line 37: The heading "More than 600 connectors" and its surrounding claim are
incorrect; verify the actual documented connector count (the connector catalog
referenced) and either replace "More than 600 connectors" and the body copy with
the substantiated number (e.g., "95 connectors") or change it to a non-numeric
claim like "Extensive connector catalog" / "Many connectors" that does not
assert an unverified figure; update the heading text and any sentences that
mention "600+" so they match the verified count or use neutral wording to avoid
misleading readers.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 7ef7e2d2-909a-4f2f-b0e4-6b6ee74fe446
📒 Files selected for processing (1)
en/docs/get-started/why.md
There was a problem hiding this comment.
Pull request overview
Updates the “Why WSO2 Integrator” get-started documentation to better align the opening messaging and connector/packaging references with current product positioning.
Changes:
- Refined the opening positioning statement to emphasize AI agents, APIs, data, and events.
- Updated connector count messaging from 200 to 600.
- Clarified the package registry reference to explicitly name “Ballerina Central”.
| # Why WSO2 Integrator | ||
|
|
||
| Connect anything, and solve any integration challenge. Connect AI agents, APIs, data, and events across cloud, on-premises, and hybrid environments. Build any type of integration and AI agent with the 100% open-source WSO2 Integrator. | ||
| Connect AI agents, APIs, data, and events across cloud, on-premises, and hybrid environments. Build any type of integration and AI agent with the 100% open-source WSO2 Integrator. |
There was a problem hiding this comment.
The lead sentence mixes plural and singular and slightly conflicts with the next heading (line 11). Consider aligning the phrasing (e.g., keep the same singular/plural form for “AI agent(s)” and mirror “AI agent or integration”) to improve readability and consistency.
| Connect AI agents, APIs, data, and events across cloud, on-premises, and hybrid environments. Build any type of integration and AI agent with the 100% open-source WSO2 Integrator. | |
| Connect AI agents, APIs, data, and events across cloud, on-premises, and hybrid environments. Build any type of AI agent or integration with the 100% open-source WSO2 Integrator. |
Edited to align with overall messaging
Purpose
Goals
Approach
User stories
Release note
Documentation
Training
Certification
Marketing
Automation tests
Security checks
Samples
Related PRs
Migrations (if applicable)
Test environment
Learning
Summary by CodeRabbit