docs(index): restructure homepage information and add missing sections#1874
Conversation
Reorder homepage to a developer-first reading path: **What → Try → Compare → Features → Not → Governance → License.** - Promote `## Get started with A2A` directly under the hero. - Rename `## Why use the A2A Protocol` → `## Key Features`; add an **Extensible** card linking to the extensions governance page. - Rewrite `## How does A2A work with MCP?` → `## How A2A Works with MCP` as a clean A2A↔MCP comparison. Keep the existing PNG. Add a "See also" link to `topics/a2a-and-mcp.md`. - Add `## What A2A Is Not` — explicit scope-setting. - Add `## Governance & Open Source` — moves the LF/TSC paragraph out of the intro; links to `GOVERNANCE.md` and `MAINTAINERS.md`. - Add `## License` — Apache 2.0 + contributions link. - Fix `<8 min` → `under 8 min` (the `<` was an HTML-parse hazard).
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the documentation in docs/index.md to clarify the purpose and scope of the Agent2Agent (A2A) Protocol. Key changes include a reworded introduction, the addition of a section explaining the complementarity between A2A and the Model Context Protocol (MCP), a 'What A2A Is Not' section to set expectations, and new sections regarding project governance and licensing. I have no feedback to provide.
muscariello
left a comment
muscariello
left a comment
There was a problem hiding this comment.
Can you also add https://github.com/a2aproject/a2a-rs among the off.SDK?
… github.com:msampathkumar/A2A into sampath_refresh_homepage
…2A into sampath_refresh_homepage
Thank you! Updated it now. |
holtskinner
left a comment
holtskinner
left a comment
There was a problem hiding this comment.
I think the new structure works well!
| - **Model Context Protocol (MCP)**: Provides [agent-to-tool communication](https://cloud.google.com/discover/what-is-model-context-protocol). It's a complementary standard that standardizes how an agent connects to its tools, APIs, and resources to get information. | ||
| - **IBM ACP**: [Incorporated into the A2A Protocol](https://github.com/orgs/i-am-bee/discussions/5) | ||
| - **Cisco agntcy**: A framework that provides components to the Internet of Agents with discovery, group communication, identity and observability and leverages A2A and MCP for agent communication and tool calling. | ||
| - **A2A**: Provides agent-to-agent communication. As a universal, decentralized standard, A2A acts as the public internet that allows [ai agents](https://cloud.google.com/discover/what-are-ai-agents)—including those using MCP, or built with frameworks like agntcy—to interoperate, collaborate, and share their findings. |
There was a problem hiding this comment.
Is there a specific reason why this integration section was removed? This includes all the A2A partners and complementary protocols and removing these has community impact. Can we get this back?
5 participants
Reorder homepage to a developer-first reading path:
What → Try → Compare → Features → Not → Governance → License.
Details:
## Get started with A2Adirectly under the hero.## Why use the A2A Protocol→## Key Features; add an Extensible card linking to the extensions governance page.## How does A2A work with MCP?→## How A2A Works with MCPas a clean A2A↔MCP comparison. Keep the existing PNG. Add a "See also" link totopics/a2a-and-mcp.md.## What A2A Is Not— explicit scope-setting.## Governance & Open Source— moves the LF/TSC paragraph out of the intro; links toGOVERNANCE.mdandMAINTAINERS.md.## License— Apache 2.0 + contributions link.<8 min→under 8 min(the<was an HTML-parse hazard).Closes #1872
You can preview - https://msampathkumar.github.io/A2A/