Skip to content

Commit d23a713

Browse files
committed
Updating Console info.
1 parent 606b234 commit d23a713

File tree

2 files changed

+31
-27
lines changed

2 files changed

+31
-27
lines changed

distribution/how-to-submit-to-plugin-manager.md

+30-27
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,6 @@ The XD Plugin Manager is accessed through:
77
- the _Plugins_ menu in the app's menu bar: go to _Plugins > Discover Plugins..._
88
- the plus button (+) in the plugins panel on the left-hand side of the app
99

10-
![XD Plugin Manager](/images/plugin-manager.png)
11-
1210
In order to make your plugin available in the XD Plugin Manager, you'll need to go through our [submission checklist and review process](/distribution/submission-checklist.md).
1311

1412
## Prerequisites
@@ -22,9 +20,7 @@ In order to make your plugin available in the XD Plugin Manager, you'll need to
2220

2321
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).
2422

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-
27-
If everything looks good, you can then submit your plugin and our CC Integrations Review team will review it.
23+
Once you've entered information about your plugin, you can then submit your it. Our CC Integrations Review team will review it and communicate any next steps back to you.
2824

2925
We'll walk you through the workflow below.
3026

@@ -36,50 +32,57 @@ All plugins are reviewed by our CC Integrations Review team. Make sure to thorou
3632

3733
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.
3834

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.
35+
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.
4036

41-
In the left-hand navbar, you'll see a "Distribute" page.
37+
In the left-hand navbar, you'll see a "Distribute" link. You can begin creating your listing by clicking this link.
4238

43-
![Distribute your plugin](/images/submit.png)
39+
### 3. Submit plugin for review - Listing Information
4440

45-
You can begin creating your listing from this page.
41+
The "Submit plugin for review" page has three tabs:
4642

47-
### 3. Submit plugin for review - Listing Information
48-
The "Submit plugin for review" page has two tabs: "Listing information" and "Plugin file". As the first step, you are asked to provide some facts about you, the publisher, and your plugin. Make sure that the plugin name in your [manifest file](/reference/structure/manifest.md) and the plugin name you provide here match.
43+
1. Publisher information
44+
2. Listing information
45+
3. Plugin file
4946

50-
![Publisher and plugin info](/images/plugin-and-publisher-info.png)
47+
**In the Publisher information tab**, you are asked to provide some facts about you, the publisher. This information applies to any plugin you create and any updates to this information will affect all versions of every plugin you've published.
5148

52-
Next, indicate whether your plugin requires installations of another application or use of a third party service. Also, include release notes for this version. This information will be displayed in the plugin manager to help users onboard your plugin.
49+
**In the Listing information tab**, you'll enter information about your plugin.
5350

54-
![Connection and version info](/images/connect-and-version-details.png)
51+
A few important notes:
5552

56-
Next, you are asked to provide three plugin icons (48 x 48 px, 96 x 96 px, and 192 x 192 px). These icons will be used for display in the Plugin Manager listing.
53+
- For plugin names:
5754

58-
> **Info**
59-
> Note that, separately, you are required to include additional icons in your plugin package and include them in [the manifest](/reference/structure/manifest.md). These icons can be different from the ones that you use in Console and they will be used to show icons in the plugins panel within the application.
55+
- Make sure that the plugin name in your [manifest file](/reference/structure/manifest.md) and the plugin name you provide in the Console match.
56+
- Note that plugin names are globally unique. If your plugin name is already taken, you'll need to find another name.
57+
- Your plugin name is reserved for 90 days once you have saved it as part of your submission information. If you do not publish a plugin within that timeframe, the name will once again become available to other developers to use.
6058

61-
You must also provide at least one screenshot of your plugin, which will be included in your Plugin Manager listing when published.
59+
- For icons:
6260

63-
![Icon and screenshot info](/images/plugin-icons-and-screenshots.png)
61+
- The Console will ask you to supply some icons for display in your XD Plugin Manager listing.
62+
- Separately, you are required to include additional icons in your plugin package and include them in [the manifest](/reference/structure/manifest.md). These icons can be different from the ones that you use in Console and they will used for display within the application.
6463

65-
Finally, if you have a message for our reviewers, write it here.
64+
In the **Plugin file** tab, you can upload your Plugin File.
6665

67-
> **Info**
68-
> Note that if your plugin requires a paid account, license number, or other such credentials to use all features of the plugin, you must provide test credentials in the "Note to Adobe reviewers" field so Adobe can review the plugin. If we need credentials from you and they have not been shared in this field, your plugin submission will be rejected.
66+
### 4. Preview and submit plugin version for review
67+
68+
Once you have provided all required information about your plugin, you can click "Preview and submit".
6969

70-
![Note to reviewer](/images/note-to-reviewers.png)
70+
This final screen will allow you to:
7171

72-
### 4. Submit plugin for review - Plugin File
72+
1. Preview your listing in Adobe XD before submitting
73+
2. Add a note to the CC Integrations Review team
74+
3. Choose whether to publish immediately after approval or manually publish later
7375

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.
76+
> **Info**
77+
> Note that if your plugin requires a paid account, license number, or other such credentials to use all features of the plugin, you must provide test credentials in the "Note to Adobe reviewers" field so Adobe can review the plugin. If we need credentials from you and they have not been shared in this field, your plugin submission will be rejected.
7578
76-
When your plugin passes all validation checks by the Adobe Developer Console, the "Submit" button will be activated for you to click.
79+
When you're ready to submit your plugin to Adobe for review, click "Submit".
7780

7881
Congratulations on your submission! We can't wait to have a look at what you've created!
7982

8083
## CC Integrations Review
8184

82-
After you submit, the CC Integrations Review team will review your plugin. Depending on current submission volume, it can take up to 10 business days before you hear a response. Thank you for being patient with us.
85+
After you submit, the CC Integrations Review team will review your plugin. Depending on current submission volume, it can take up to 10 business days before you hear a response. Thank you for being patient with us.
8386

8487
> **Info**
8588
> Many of the items our reviewers check for when reviewing a plugin are noted in the [submission checklist](/distribution/submission-checklist.md).

scripts/404-test.sh

+1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
#! /bin/bash
2+
# npm i -g broken-link-checker-local
23

34
mkdir .logs 2> /dev/null
45
blcl ./_book -ro > ./.logs/log.txt

0 commit comments

Comments
 (0)