@commercetools/nimbus-mcp 3.5.1 → 3.6.0

package/data/docs/routes/home-contribute.json

@@ -1,8 +1,8 @@
 {
   "meta": {
-    "id": "Home-Contribute-1746704391512",
+    "id": "Home-Contribute",
     "title": "Contributing",
-    "description": "Contribute to the nimbus development",
+    "description": "How to contribute to the nimbus design system, open pull requests, and communicate with the team.",
     "order": 999,
     "repoPath": "packages/nimbus/src/docs/home-contribute.mdx",
     "menu": [
@@ -12,10 +12,20 @@
     "route": "home/contribute",
     "tags": [
       "guide",
-      "contributing",
-      "development"
+      "contributing"
+    ],
+    "toc": [
+      {
+        "value": "Communication channels",
+        "href": "#communication-channels",
+        "depth": 2,
+        "numbering": [
+          1,
+          1
+        ],
+        "parent": "root"
+      }
     ],
-    "toc": [],
     "icon": "Computer",
     "layout": "app-frame",
     "tabs": [
@@ -26,11 +36,22 @@
       }
     ]
   },
-  "mdx": "\n# Contributing\n\nContribute to the nimbus development.\n",
+  "mdx": "\n# Contributing to nimbus\n\nProduct teams can propose pull requests directly to the nimbus repository.\nPlease read the [collaboration guidelines](/home/getting-started/collaboration)\nbefore contributing.\n\nBefore opening a PR:\n\n1. **Discuss the change first.** Start in Slack or a GitHub Issue. The nimbus\n   team can help scope the work, flag potential conflicts with in-progress work,\n   and confirm the approach aligns with system conventions.\n2. **Align on whether the change belongs in nimbus.** Not every useful component\n   is a good fit for the core system. The nimbus team is the final\n   decision-maker on what goes into nimbus, and an early conversation avoids\n   wasted effort.\n3. **Follow nimbus conventions.** Contributions should meet the same standards\n   as nimbus-authored code: accessibility, testing, documentation, Figma parity,\n   and API consistency. The nimbus team can help contributors understand these\n   expectations.\n\nThe nimbus team reviews and shepherds contributed PRs. Some contributions may be\naccepted as-is; others may be adapted or reimplemented to fit system\nconventions. In all cases, the contributing team gets credit and the outcome is\ncollaborative.\n\n## Communication channels\n\n| Channel                                                                          | When to use                                                                                                 |\n| :------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------- |\n| [**nimbus Slack channel**](https://commercetools.slack.com/archives/C0ACFBKAHTM) | Quick questions, exploring whether something exists, early-stage feature discussions, architecture guidance |\n| [**GitHub Issues**](https://github.com/commercetools/nimbus/issues)              | Formal bug reports, feature proposals (using the template), design discrepancy reports                      |\n| [**Jira**](https://jira.commercetools.com)                                      | Tracking work in progress once a decision has been made                                                     |\n",
   "views": {
     "overview": {
-      "mdx": "\n# Contributing\n\nContribute to the nimbus development.\n",
-      "toc": []
+      "mdx": "\n# Contributing to nimbus\n\nProduct teams can propose pull requests directly to the nimbus repository.\nPlease read the [collaboration guidelines](/home/getting-started/collaboration)\nbefore contributing.\n\nBefore opening a PR:\n\n1. **Discuss the change first.** Start in Slack or a GitHub Issue. The nimbus\n   team can help scope the work, flag potential conflicts with in-progress work,\n   and confirm the approach aligns with system conventions.\n2. **Align on whether the change belongs in nimbus.** Not every useful component\n   is a good fit for the core system. The nimbus team is the final\n   decision-maker on what goes into nimbus, and an early conversation avoids\n   wasted effort.\n3. **Follow nimbus conventions.** Contributions should meet the same standards\n   as nimbus-authored code: accessibility, testing, documentation, Figma parity,\n   and API consistency. The nimbus team can help contributors understand these\n   expectations.\n\nThe nimbus team reviews and shepherds contributed PRs. Some contributions may be\naccepted as-is; others may be adapted or reimplemented to fit system\nconventions. In all cases, the contributing team gets credit and the outcome is\ncollaborative.\n\n## Communication channels\n\n| Channel                                                                          | When to use                                                                                                 |\n| :------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------- |\n| [**nimbus Slack channel**](https://commercetools.slack.com/archives/C0ACFBKAHTM) | Quick questions, exploring whether something exists, early-stage feature discussions, architecture guidance |\n| [**GitHub Issues**](https://github.com/commercetools/nimbus/issues)              | Formal bug reports, feature proposals (using the template), design discrepancy reports                      |\n| [**Jira**](https://jira.commercetools.com)                                      | Tracking work in progress once a decision has been made                                                     |\n",
+      "toc": [
+        {
+          "value": "Communication channels",
+          "href": "#communication-channels",
+          "depth": 2,
+          "numbering": [
+            1,
+            1
+          ],
+          "parent": "root"
+        }
+      ]
     }
   }
 }