Create CONTRIBUTING.md (#39)

* Create CONTRIBUTING.md

* update table

---------

Co-authored-by: Markus Ecker <[email protected]>

Author: NathanTarbert

CONTRIBUTING.md

@@ -0,0 +1,56 @@
+# Contributing to AG-UI
+
+Thanks for your interest in improving **AG-UI**!
+
+This short guide shows the fastest way to get your idea merged.
+
+---
+
+## 1. Start a Discussion
+
+Before writing code, open a new **Discussion** and briefly cover:
+
+1. **Problem** – what you’re trying to solve.
+2. **Proposal** – how you plan to solve it (code, docs, design, etc.).
+3. **Alternatives** – other options you considered.
+
+Early feedback keeps everyone aligned and saves re-work.
+
+---
+
+## 2. Join a Bi-Weekly Working Group
+
+Meet the team and potential collaborators in our [bi-weekly community call](https://lu.ma/calendar/manage/cal-DBw2gK428IQbiSO).
+
+---
+
+## 3. Connect with the Maintainers
+
+Need a quick sync?
+
+- **Markus:** [@mme_xyz](https://twitter.com/mme_xyz) on X (Twitter)
+- **Book a chat:** <https://calendly.com/markus-copilotkit/ag-ui>
+
+---
+
+## 4. Useful Resources & Docs
+
+| Resource                                  | Link                                                     |
+| ----------------------------------------- | -------------------------------------------------------- |
+| Learn how to connect to AG-UI with JS     | <https://docs.ag-ui.com/quickstart/connect>              |
+| Learn how to connect to AG-UI with Python | <https://docs.ag-ui.com/quickstart/build>                |
+| Dojo reference implementation             | <https://github.com/ag-ui-protocol/ag-ui/tree/main/dojo> |
+
+---
+
+## 5. Open Your Pull Request
+
+1. **Fork** the repo and create a feature branch.
+2. Keep changes focused—one PR per feature or fix.
+3. Link back to your Discussion in the PR description.
+
+We review PRs weekly. Feel free to nudge us in your Discussion if you haven’t heard back in a few days.
+
+---
+
+**Thank you for making AG-UI better!**