diff --git a/_snippets/integrations/submit-community-node.md b/_snippets/integrations/submit-community-node.md index 41e421719..51c5ba3ae 100644 --- a/_snippets/integrations/submit-community-node.md +++ b/_snippets/integrations/submit-community-node.md @@ -5,7 +5,7 @@ Community nodes are npm packages, hosted in the npm registry. When building a node to submit to the community node repository, use the following resources to make sure your node setup is correct: -* View the [starter node](https://github.com/n8n-io/n8n-nodes-starter). +* View the [starter node](https://github.com/n8n-io/n8n-nodes-starter){:target=_blank .external-link}. * Refer to the documentation on [building your own nodes](/integrations/creating-nodes/). * Make sure your node follows the [standards](#standards) for community nodes. @@ -14,6 +14,6 @@ When building a node to submit to the community node repository, use the followi To make your node available to the n8n community node repository, you must: * Make sure the package name starts with `n8n-nodes-` or `@/n8n-nodes-`. For example, `n8n-nodes-weather` or `@weatherPlugins/n8n-nodes-weather`. -* Tag your package with `n8n-community-node-package`. +* Include `n8n-community-node-package` in your package keywords. * Submit the package to the npm registry. Refer to npm's documentation on [Contributing packages to the registry](https://docs.npmjs.com/packages-and-modules/contributing-packages-to-the-registry){:target=_blank .external-link} for more information. -* Make sure that you add your nodes and credentials to the `package.json` file inside the `n8n` attribute. Refer to the [package.json in the starter node](https://github.com/n8n-io/n8n-nodes-starter/blob/master/package.json) for an example. +* Make sure that you add your nodes and credentials to the `package.json` file inside the `n8n` attribute. Refer to the [package.json in the starter node](https://github.com/n8n-io/n8n-nodes-starter/blob/master/package.json){:target=_blank .external-link} for an example. diff --git a/docs/_images/common-icons/package.png b/docs/_images/common-icons/package.png new file mode 100644 index 000000000..54756d06a Binary files /dev/null and b/docs/_images/common-icons/package.png differ diff --git a/docs/_images/common-icons/three-dot-options-menu.png b/docs/_images/common-icons/three-dot-options-menu.png new file mode 100644 index 000000000..f19a4d097 Binary files /dev/null and b/docs/_images/common-icons/three-dot-options-menu.png differ diff --git a/docs/integrations/community-nodes/installation.md b/docs/integrations/community-nodes/installation.md index 6a244a6d1..957ebcee4 100644 --- a/docs/integrations/community-nodes/installation.md +++ b/docs/integrations/community-nodes/installation.md @@ -30,7 +30,7 @@ To install a community node: To uninstall a community node: 1. Go to **Settings** > **Community nodes**. -2. On the node you want to install, select **Options** . +2. On the node you want to install, select **Options** ![Three dots options menu](/_images/common-icons/three-dot-options-menu.png). 3. Select **Uninstall package**. 4. Select **Uninstall Package** in the confirmation modal. diff --git a/docs/integrations/community-nodes/usage.md b/docs/integrations/community-nodes/usage.md index 40c78adfe..fbe45168b 100644 --- a/docs/integrations/community-nodes/usage.md +++ b/docs/integrations/community-nodes/usage.md @@ -4,7 +4,7 @@ To use community nodes, you first need to [install](/integrations/community-node ## Adding community nodes to your workflow -After installing a community node, you can use it like any other node. n8n displays the node in search results in the **Nodes** panel. To show which nodes are community nodes and which are built-in, n8n marks community nodes with a **Package** icon [TODO: add icon]. +After installing a community node, you can use it like any other node. n8n displays the node in search results in the **Nodes** panel. To show which nodes are community nodes and which are built-in, n8n marks community nodes with a **Package** ![Package icon](/_images/common-icons/package.png) icon. ## Community nodes with duplicate names