chore: improve introduction and guidance for TEDI React components #534

Author: airikej

src/tedi/docs/_welcome.mdx

@@ -7,7 +7,32 @@ import { Meta, Title, Subtitle, Unstyled } from '@storybook/blocks';
 Here you can find our design guidelines, component documentation, and resources for building apps with
 `@tedi-design-system/react`
 
-## Resources
+## Component Types
+
+TEDI offers two types of components:
+
+### TEDI-Ready Components
+
+These components are fully **supervised and maintained by the TEDI team**.
+
+- Updates and contributions are reviewed by the TEDI team before merging into the `rc` branch.
+- They require unit tests.
+- They follow strict design and accessibility guidelines.
+- The TEDI team ensures stability and fixes issues in these components.
+
+### Community Components
+
+These are **community-driven components**, and the **community is responsible for maintaining them**.
+
+- Contributors own their components: they are responsible for bug fixes, updates, and stability.
+- Unit tests are optional but recommended.
+- Anyone can contribute directly without TEDI-team approval.
+- Community contributions can still improve TEDI-Ready components, but changes must go through TEDI-team review.
+- If a community component depends on a TEDI-Ready component and issues arise due to the TEDI-Ready component, the TEDI team will handle it—but **if the issue is within the community component itself, the responsibility lies with the contributor/community**.
+
+---
+
+#### **Resources:**
 
 - [Repository](https://github.com/TEDI-Design-System/react)
 - [WIKI](https://github.com/TEDI-Design-System/general)