Console changes are coming, March 5th


#9

@cpryland, try to submit a plugin and you will see that now all info come from your manifest.
My compliments to the XD Team, great work! Definitely love this new update!


#10

Update #4: Here’s our Tech Blog article on the changes: https://medium.com/adobetech/weve-updated-the-adobe-xd-plugin-workflow-on-the-i-o-developer-console-79cb5f11149c

Thanks for the compliments, @PaoloBiagini! Perhaps you can make a new setting for your icon export plugin… :grin:


#11

Update #5: We’re planning to have specific migration instructions for you tomorrow, so if you want to wait, we’ll be able to make next steps very clear for you.


#12

In addition to @PaoloBiagini’s comment, for a non-published plugin, the only changes you might notice are all on the plugin details page:

  1. You can now rename your project name (reference name for your use only) in the Console.
  2. Your downloadable starter project contains an updated manifest.
  3. You can check plugin name (public name, which must be universally unique) availability before submitting for review.

#13

Just submitted, hope it will pass the test.


#14

Does it work from Safari now? :slight_smile:


#15

Do you remember what was broken for you in Safari? I only use Safari and haven’t run into any blocking issues.


#16

When you submit a plugin the last step doesn’t show any confirmation, but a blank screen (I think it was blank screen, however it is, it fails to submit and doesn’t display any feedback). Last time I submitted a plugin was few weeks ago and after it failed I remembered I had to do it in Chrome, so didn’t bother much, because it was the same the first try I tried it and reported it.

Edit: maybe it’s fixed now with these changes.


#17

I’ll share this with the team, just in case.


#18

I can confirm, never had issues with Safari.


#19

Yesterday we posted this follow-up article with some of the more frequently asked questions: https://medium.com/adobetech/new-xd-plugin-manifest-q-a-a1f365d6dbbb


#20

Is “main”: “main.js”, no longer required? It’s not listed in the docs.


#21

A question about keywords:
do we have to add a word as keyword even if it’s already in the description text or would it be redundant?


#22

I’ve written a JSON schema making it easier to edit the manifest.json files in general and updating plugins to fit the new requirements in particular. You can read more about it in my forum post or directly in the GitHub repository


#23

@Velara that hasn’t been required for some time (although its presence doesn’t invalidate your manifest). Since all plugins must have a main.js file, it was probably seen as redundant to require stating that in the manifest.

I just checked against the Console’s starter project, and my findings:

  1. The presence of that field won’t stop your plugin from loading
  2. The field’s value is not “configurable” (changing the value to point to another file doesn’t do anything)
  3. The starter project includes this field, but it can (and probably should) be omitted

Let me know if you’ve seen anything to the contrary.

I’ll take this back to the team. Currently, I’m thinking we just need to remove the field from the starter project.


#24

Do you have a #XDplugin developer tool or sample plugin that you’ve updated to support or reflect the new manifest changes?

This includes XD-Awesome contributors.

Feel free to share in a reply to this tweet:


#25

@ashryan, my plugins are all up-to-date but unfortunately I haven’t any social account. Anyway, they are all available through XD-Awesome.


#26

@ashryan, any recommendation regarding keywords?


#27

Not yet. We realize that details and best practices are scarce at the moment. We’re looking into what further guidance we can provide. Thanks for bringing this up!


#28

I would certainly hope it’s redundant – I’m pretty sure searching on words that are in the description field should continue to work just fine.

But I believe one of the issues here is that the Plugin Manager implementation work to actually use the new keywords field is not complete yet. We’re hoping to have clearer info soon on when Plugin Manager will begin using this field for search results and how exactly it will work (CC @ashryan, @stevekwak).