You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,9 +36,9 @@ XD plugins are used by designers around the world who expect great experiences.
36
36
37
37
**Manage your plugin project**
38
38
39
-
Whether you’re getting your unique plugin ID, submitting your finished plugin for review, or updating your XD Plugin Manager listing, the I/O Developer Console is the place to manage your plugin project.
39
+
Whether you’re getting your unique plugin ID, submitting your finished plugin for review, or updating your XD Plugin Manager listing, the Adobe Developer Console is the place to manage your plugin project.
40
40
41
-
**[Visit the I/O console](https://console.adobe.io)**
41
+
**[Visit the Adobe Developer Console](https://console.adobe.io)**
Copy file name to clipboardExpand all lines: distribution/how-to-submit-to-plugin-manager.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,9 +20,9 @@ In order to make your plugin available in the XD Plugin Manager, you'll need to
20
20
21
21
## Submit your plugin
22
22
23
-
You can submit your plugin for review through the I/O Developer Console, the same place you got your [unique plugin ID for your manifest](/reference/structure/manifest.md).
23
+
You can submit your plugin for review through the Adobe Developer Console, the same place you got your [unique plugin ID for your manifest](/reference/structure/manifest.md).
24
24
25
-
On the I/O Console, you can provide your packaged plugin. The I/O Console will automatically validate your package and its [manifest file](/reference/structure/manifest.md). Then, you will be asked to provide more information about your plugin on the Console.
25
+
On the Adobe Developer Console, you can provide your packaged plugin. The Adobe Developer Console will automatically validate your package and its [manifest file](/reference/structure/manifest.md). Then, you will be asked to provide more information about your plugin on the Console.
26
26
27
27
If everything looks good, you can then submit your plugin and our CC Integrations Review team will review it.
28
28
@@ -34,7 +34,7 @@ All plugins are reviewed by our CC Integrations Review team. Make sure to thorou
34
34
35
35
### 2. Begin your submission
36
36
37
-
To begin the submission for your plugin, visit the [Developer Console](https://console.adobe.io/plugins) and select your plugin from your list of plugin projects.
37
+
To begin the submission for your plugin, visit the [Developer Console](https://console.adobe.io/projects) and select your plugin from your list of plugin projects.
38
38
39
39
This will take you to your plugin's "Project Overview" page, which shows your plugin ID, a download link for your starter project, and more.
40
40
@@ -73,7 +73,7 @@ Finally, if you have a message for our reviewers, write it here.
73
73
74
74
Once you have provided all required information about your plugin, including icons and screenshots, you will be asked to attach your plugin package. Make sure to properly [package your plugin](/distribution/packaging.md) into an `.xdx` file.
75
75
76
-
When your plugin passes all validation checks by the I/O Console, the "Submit" button will be activated for you to click.
76
+
When your plugin passes all validation checks by the Adobe Developer Console, the "Submit" button will be activated for you to click.
77
77
78
78
Congratulations on your submission! We can't wait to have a look at what you've created!
Copy file name to clipboardExpand all lines: distribution/packaging.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ If you plan to distribute via the XD plugin manager, your .ZIP file **must be le
24
24
25
25
> **Danger**
26
26
>
27
-
> You should not compress the plugin's _parent_ folder. Instead, compress the _contents_ of the parent folder. Failure to do so will likely cause a rejection when submitting to the [I/O Console](https://console.adobe.io/plugins).
27
+
> You should not compress the plugin's _parent_ folder. Instead, compress the _contents_ of the parent folder. Failure to do so will likely cause a rejection when submitting to the [Adobe Developer Console](https://console.adobe.io/projects).
Copy file name to clipboardExpand all lines: distribution/submission-checklist.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ This document will give you an idea of what we’re checking for during the revi
9
9
10
10
## Plugin listing information
11
11
12
-
Plugin listing information is the content that users will see in the XD Plugin Manager when browsing your listing. Unless otherwise noted, this is information that you will input and maintain on the [Adobe I/O Console](https://console.adobe.io/plugins).
12
+
Plugin listing information is the content that users will see in the XD Plugin Manager when browsing your listing. Unless otherwise noted, this is information that you will input and maintain on the [Adobe Developer Console](https://console.adobe.io/projects).
13
13
14
14
In this section, we’ll go over what we’re checking for to ensure that your plugin listing is complete, correct, and in line with Adobe’s standards.
15
15
@@ -35,7 +35,7 @@ In this section, we’ll go over what we’re checking for to ensure that your p
35
35
* Placeholder icons will not be accepted. Icons must be unique and must be property of the plugin author. Submissions that contain icons from sample projects (or variations thereof) will be rejected.
36
36
* Plugin icons may not contain Adobe product assets or icons.
37
37
* Plugin icons must be clear and free of distortion.
38
-
* All required plugin icons must be provided at the appropriate dimensions and file sizes. See the [manifest documentation](https://adobexdplatform.com/plugin-docs/reference/structure/manifest.html) and ["Publishing your plugin" guide](https://adobexdplatform.com/plugin-docs/distribution/how-to-submit-to-plugin-manager.html) to learn more about which icons to include in your plugin package versus which to upload via the Adobe I/O Console.
38
+
* All required plugin icons must be provided at the appropriate dimensions and file sizes. See the [manifest documentation](https://adobexdplatform.com/plugin-docs/reference/structure/manifest.html) and ["Publishing your plugin" guide](https://adobexdplatform.com/plugin-docs/distribution/how-to-submit-to-plugin-manager.html) to learn more about which icons to include in your plugin package versus which to upload via the Adobe Developer Console.
Copy file name to clipboardExpand all lines: reference/structure/manifest.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,14 +42,14 @@ The top level of the manifest JSON object contains high-level information about
42
42
> **Info**
43
43
> Here are the definitions of the keywords in the "Required" column:
44
44
> - Develop - required field for XD to run the plugin. If excluded, XD won't load the plugin
45
-
> - Publish - required field for plugins to be submitted in the I/O Console and published in the Plugin Manager
45
+
> - Publish - required field for plugins to be submitted in the Adobe Developer Console and published in the Plugin Manager
46
46
47
47
Key path | Type | Description | Required
48
48
---------|------|-------------|---------
49
-
`id` | `string` | Unique identifier for your plugin. You can get your unique ID on the [Adobe I/O Console](https://console.adobe.io/plugins).| Develop / Publish
50
-
`name` | `string` | The name should be 3 - 45 characters. <br> **Note:** We recommend your plugin name matches the _project name_ you created when getting your plugin ID from the I/O Console. | Develop / Publish
49
+
`id` | `string` | Unique identifier for your plugin. You can get your unique ID on the [Adobe Developer Console](https://console.adobe.io/projects).| Develop / Publish
50
+
`name` | `string` | The name should be 3 - 45 characters. <br> **Note:** We recommend your plugin name matches the _project name_ you created when getting your plugin ID from the Adobe Developer Console. | Develop / Publish
51
51
`version`| `string` | Version number of your plugin in `x.y.z` format. <br>Version must be three segments and each version component must be between `0` and `99`. | Develop / Publish
52
-
`icons` | `array<object>` | Icons displayed in XD's plugins panel. <br> PNG, JPG/JPEG formats are supported and the max file size for each icon is 1MB. <br> Two sizes are required - `[24, 48]`. <br> **Note:** Icons for XD's Plugin Manager are uploaded directly via the I/O Console, not included within your plugin itself. See our ["Publishing your plugin" guide](../../distribution/how-to-submit-to-plugin-manager.md) to learn more. | Publish
52
+
`icons` | `array<object>` | Icons displayed in XD's plugins panel. <br> PNG, JPG/JPEG formats are supported and the max file size for each icon is 1MB. <br> Two sizes are required - `[24, 48]`. <br> **Note:** Icons for XD's Plugin Manager are uploaded directly via the Adobe Developer Console, not included within your plugin itself. See our ["Publishing your plugin" guide](../../distribution/how-to-submit-to-plugin-manager.md) to learn more. | Publish
53
53
`host.app` | `string` | Indicates that this is a plugin for Adobe XD (currently, the only valid value here is `"XD"`). | Develop / Publish
54
54
`host.minVersion` | `string` | Minimum required version of the host app (in `x.y` format) that can run this plugin. The lowest valid version for headless and modal plugins is `13.0`. The lowest valid version for panel plugins is `21.0`. <br> **Note:** The version number must be two segments. Typically, you'll leave the minor segment set to `0`, e.g. `16.0`. | Develop / Publish
55
55
`host.maxVersion` | `string` | Maximum version of host app that can run this plugin. Same formatting as `host.minVersion`. | Optional
Copy file name to clipboardExpand all lines: tutorials/quick-start-panel/index.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,13 +16,14 @@ At the end of the tutorial, we'll suggest some next steps for going deeper with
16
16
> **Info**
17
17
> Complete code for this plugin can be found [on GitHub](https://github.com/AdobeXD/Plugin-Samples/tree/master/quick-start-panel).
18
18
19
-
### 0. Get a plugin ID from the I/O Developer Console
19
+
### 0. Get a plugin ID from the Adobe Developer Console
20
20
21
-
Before you start, you'll want to create a plugin project on the Adobe I/O Developer Console.
21
+
Before you start, you'll want to create a plugin project on the Adobe Developer Console.
22
22
23
-
1.[Go to the I/O Console and sign in or sign up](https://console.adobe.io/plugins)
24
-
1. Click "Create Plugin"
25
-
1. Create a plugin project by giving it a project name and clicking "Create Plugin". Note that this project name is not public; it is only visible to you and can be changed directly on the Console later.
23
+
1.[Go to the Adobe Developer Console and sign in or sign up](https://console.adobe.io/projects)
24
+
1. Click "Create Empty Project"
25
+
1. Create a plugin project by clicking "Add XD Plugin"
26
+
1. Give it a project name. Note that this project name is not public; it is only visible to you and can be changed directly on the Console later.
26
27
1. On the following page, get the 8-character unique plugin ID in the "Plugin Details" section.
27
28
1. Optionally on the same page, download the starter project, which contains a functioning Hello, World sample plugin.
28
29
@@ -90,7 +91,7 @@ In the previous step, you created a file named `manifest.json`. Open that file a
90
91
}
91
92
```
92
93
93
-
Be sure to replace the `id` value with the unique plugin ID you got from the I/O Console in the first step:
94
+
Be sure to replace the `id` value with the unique plugin ID you got from the Adobe Developer Console in the first step:
Copy file name to clipboardExpand all lines: tutorials/quick-start-react/index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -158,14 +158,14 @@ In the previous step, you created a file named `manifest.json`. Open that file a
158
158
}
159
159
```
160
160
161
-
Be sure to replace the `id` value with the unique plugin ID you get from the I/O Console.
161
+
Be sure to replace the `id` value with the unique plugin ID you get from the Adobe Developer Console.
162
162
163
163
```json
164
164
"id": "1234ABCD",
165
165
```
166
166
167
167
> **Info**
168
-
> Make sure to read [Quick Start tutorial](/tutorials/quick-start/index.md) to learn how to get your unique plugin ID from the I/O Console.
168
+
> Make sure to read [Quick Start tutorial](/tutorials/quick-start/index.md) to learn how to get your unique plugin ID from the Adobe Developer Console.
169
169
170
170
If you're curious about what each entry in the manifest means, [see the manifest documentation](/reference/structure/manifest.md), where you can also learn about all manifest requirements for a plugin to be published in the XD Plugin Manager.
0 commit comments