Signal Providers apperaring again at Crypto Ecosystem.

Projects/Superalgos/Schemas/AppSchema.json

@@ -3242,8 +3242,7 @@
             "compatibleTypes": "->Prediction->"
         },
         "propertyNameAtParent": "predictionValue",
-        "childrenNodesProperties": [
-        ],
+        "childrenNodesProperties": [],
         "icon": "bitcoin"
     },
     {
@@ -3415,8 +3414,7 @@
             "compatibleTypes": "->Feature->"
         },
         "propertyNameAtParent": "featureValue",
-        "childrenNodesProperties": [
-        ],
+        "childrenNodesProperties": [],
         "icon": "bitcoin"
     },
     {
@@ -3588,8 +3586,7 @@
             "compatibleTypes": "->Label->"
         },
         "propertyNameAtParent": "labelValue",
-        "childrenNodesProperties": [
-        ],
+        "childrenNodesProperties": [],
         "icon": "bitcoin"
     },
     {
@@ -15083,7 +15080,8 @@
                 "childType": "Signals Provider",
                 "autoAdd": true
             }
-        ]
+        ],
+        "icon": "bitcoin"
     },
     {
         "type": "Signals Provider",
@@ -15127,7 +15125,8 @@
             "config": "{ \n\"webhookURL\": \"Webhook/New-Message/Trading-View/Binance/BTC-USDT\",\n\"testMessage\": \"\" \n}"
         },
         "propertyNameAtParent": "signalsProviders",
-        "childrenNodesProperties": []
+        "childrenNodesProperties": [],
+        "icon": "bitcoin"
     },
     {
         "type": "Crypto Exchanges",

Projects/Superalgos/Schemas/Docs-Topics/app-commands-001-app-contribute-command.json

@@ -7,10 +7,31 @@
         "updated": 1610909304702
     },
     "paragraphs": [
+        {
+            "style": "Text",
+            "text": "This command will send all the changes you have made both at Docs pages but also at any file within the Superalgos Repository to your fork at Github.com and from there to the main Superalgos Repository. It will do it specifically from the Current Branch to the Contributions Branch mentioned at the footer of this page. ",
+            "updated": 1615288848213
+        },
+        {
+            "style": "Important",
+            "text": "Contributions in most cases needs to come from the develop branch to the develop branch unless you have previously agreed with team members that you will send a contribution from master to master."
+        },
+        {
+            "style": "Text",
+            "text": "Master is our stable branch and it is very unlikely that we are going to merge contributions there. Instead all contributions are expected to go to the develop branch, where there are many users testing that branch every day, and the contribution will reach the master branch at the next relrease.",
+            "updated": 1615288915134
+        },
+        {
+            "style": "Note",
+            "text": "It is also very unlikely that contributions coming from the master branch will be merged into the develop branch, since that can usually lead to merging conflicts. "
+        },
+        {
+            "style": "Text",
+            "text": "So be sure that your Current Branch is develop and the Contribution Branch is develop before submitting your contribution. "
+        },
         {
             "style": "Title",
-            "text": "Syntax",
-            "updated": 1609943337280
+            "text": "Syntax"
         },
         {
             "style": "Javascript",