RE: plugins.cordova.io: UX redesign
My name is Plugus Aycius Decius, commander of the plugins of the north, general of the cross-platform legions, loyal servant to the true emperor, Cordovus. And I will have my vengeance, in this version or the next. -Original Message- From: Wargo, John [mailto:john.wa...@sap.com] Sent: Saturday, 14 December 2013 12:20 AM To: dev@cordova.apache.org Subject: RE: plugins.cordova.io: UX redesign And his real given name is Plugmanus? Plugmanus Cordovus? -Original Message- From: brian.ler...@gmail.com [mailto:brian.ler...@gmail.com] On Behalf Of Brian LeRoux Sent: Thursday, December 12, 2013 7:39 PM To: dev@cordova.apache.org Cc: Yohei Shimomae Subject: Re: plugins.cordova.io: UX redesign I vote that we call him Plugman (But his friends call him Pluggy =) On Fri, Dec 13, 2013 at 10:57 AM, Shazron wrote: > Awesome, love Pluggy(?) the robot. > > Some comments if I may: > 1. Plugin Details - maintainers should be linkable, so we can go to a > list of their authored packages (like npmjs) 2. Plugin Details - not > sure if we want "previous versions" here. npmjs does this by appending > the version to the url, but this is not discoverable > easily: eg https://npmjs.org/package/ios-sim --> > https://npmjs.org/package/ios-sim/1.8.0 . Ideally we want the user to > always grab the latest, but there will be cases where they might want > to grab an older one for compatibility reasons, and they might not > know how, even through the command line 3. Plugin Details - I assume > the Readme here is just pulled from the Readme.md of the plugin > package (like npmjs) - that will be great if so > > > On Wed, Dec 11, 2013 at 7:26 PM, Joni Rustulka wrote: > > > Hi all, > > > > I'm Joni. I work at Adobe as a UX designer on the PhoneGap team, and > > I have recently thrown some time at redesigning the > > http://plugins.cordova.io site. I'm looking for feedback prior to > > implementation - your thoughts are appreciated. > > > > The main screens that have been reworked are as follows: > > > > > > 1. Home (http://cl.ly/image/2n3l1N0Z0g0w) The primary goal for > > the site is to help users find the plugins they > need. > > As such, the main focus is on search/findability. > > > > 2. Search Results (http://cl.ly/image/0c3X3T1E1L0j) Upon search > > for a plugin, the user is returned results. The user can filter to > > include only desired platforms ( > http://cl.ly/image/3W2f321I211r), > > and the results table can be sorted by number of downloads, or plugin ID. > > > > 3. Plugin Details (http://cl.ly/image/2n1p2s3E0a2t) The details > > screen intends to provide all of the necessary information on a > > plugin. > > ** From what I understand, one piece of information that may be > > missing from this screen is "Installation Instructions". This being, > > config.xml feature tags. Is this something that you guys plan to > > automate, or should we be telling plugin authors to put this information in their Read Me? > > Please advise. > > > > Further, we do intend to make this a responsive site - so it will be > > easily viewed on smaller screen sizes. > > > > Thanks for your input, > > -joni > > > > > > PS - big thanks and kudos to Yohei for putting together the pluggy robot! > > > > > > >
Re: plugins.cordova.io: UX redesign
More Feedback! I agree with Andrew for removing Analytics from top nav. Maybe it belongs in a footer? I think in terms of version, we could go NPM style and only show latest. We also could add a dropdown that selects older versions on the plugin detail page. It could be similar to how github lets you select branches. This way we could show older readmes (and docs if they end up in there). Searching should only bring up latest versions and I believe download counts should be on a per plugin basis instead of per version. Adding older versions to search results will just add extra clutter and doesn't make a lot of sense when we want people to be using the latest releases. +1 to gender neutral name for the plugbot. :) On Fri, Dec 13, 2013 at 5:19 AM, Wargo, John wrote: > And his real given name is Plugmanus? Plugmanus Cordovus? > > -Original Message- > From: brian.ler...@gmail.com [mailto:brian.ler...@gmail.com] On Behalf Of > Brian LeRoux > Sent: Thursday, December 12, 2013 7:39 PM > To: dev@cordova.apache.org > Cc: Yohei Shimomae > Subject: Re: plugins.cordova.io: UX redesign > > I vote that we call him Plugman > > (But his friends call him Pluggy =) > > > On Fri, Dec 13, 2013 at 10:57 AM, Shazron wrote: > > > Awesome, love Pluggy(?) the robot. > > > > Some comments if I may: > > 1. Plugin Details - maintainers should be linkable, so we can go to a > list > > of their authored packages (like npmjs) > > 2. Plugin Details - not sure if we want "previous versions" here. npmjs > > does this by appending the version to the url, but this is not > discoverable > > easily: eg https://npmjs.org/package/ios-sim --> > > https://npmjs.org/package/ios-sim/1.8.0 . Ideally we want the user to > > always grab the latest, but there will be cases where they might want to > > grab an older one for compatibility reasons, and they might not know how, > > even through the command line > > 3. Plugin Details - I assume the Readme here is just pulled from the > > Readme.md of the plugin package (like npmjs) - that will be great if so > > > > > > On Wed, Dec 11, 2013 at 7:26 PM, Joni Rustulka wrote: > > > > > Hi all, > > > > > > I'm Joni. I work at Adobe as a UX designer on the PhoneGap team, and I > > > have recently thrown some time at redesigning the > > > http://plugins.cordova.io site. I'm looking for feedback prior to > > > implementation - your thoughts are appreciated. > > > > > > The main screens that have been reworked are as follows: > > > > > > > > > 1. Home (http://cl.ly/image/2n3l1N0Z0g0w) > > > The primary goal for the site is to help users find the plugins they > > need. > > > As such, the main focus is on search/findability. > > > > > > 2. Search Results (http://cl.ly/image/0c3X3T1E1L0j) > > > Upon search for a plugin, the user is returned results. The user can > > > filter to include only desired platforms ( > > http://cl.ly/image/3W2f321I211r), > > > and the results table can be sorted by number of downloads, or plugin > ID. > > > > > > 3. Plugin Details (http://cl.ly/image/2n1p2s3E0a2t) > > > The details screen intends to provide all of the necessary information > on > > > a plugin. > > > ** From what I understand, one piece of information that may be missing > > > from this screen is "Installation Instructions". This being, config.xml > > > feature tags. Is this something that you guys plan to automate, or > should > > > we be telling plugin authors to put this information in their Read Me? > > > Please advise. > > > > > > Further, we do intend to make this a responsive site - so it will be > > > easily viewed on smaller screen sizes. > > > > > > Thanks for your input, > > > -joni > > > > > > > > > PS - big thanks and kudos to Yohei for putting together the pluggy > robot! > > > > > > > > > > > >
RE: plugins.cordova.io: UX redesign
And his real given name is Plugmanus? Plugmanus Cordovus? -Original Message- From: brian.ler...@gmail.com [mailto:brian.ler...@gmail.com] On Behalf Of Brian LeRoux Sent: Thursday, December 12, 2013 7:39 PM To: dev@cordova.apache.org Cc: Yohei Shimomae Subject: Re: plugins.cordova.io: UX redesign I vote that we call him Plugman (But his friends call him Pluggy =) On Fri, Dec 13, 2013 at 10:57 AM, Shazron wrote: > Awesome, love Pluggy(?) the robot. > > Some comments if I may: > 1. Plugin Details - maintainers should be linkable, so we can go to a list > of their authored packages (like npmjs) > 2. Plugin Details - not sure if we want "previous versions" here. npmjs > does this by appending the version to the url, but this is not discoverable > easily: eg https://npmjs.org/package/ios-sim --> > https://npmjs.org/package/ios-sim/1.8.0 . Ideally we want the user to > always grab the latest, but there will be cases where they might want to > grab an older one for compatibility reasons, and they might not know how, > even through the command line > 3. Plugin Details - I assume the Readme here is just pulled from the > Readme.md of the plugin package (like npmjs) - that will be great if so > > > On Wed, Dec 11, 2013 at 7:26 PM, Joni Rustulka wrote: > > > Hi all, > > > > I'm Joni. I work at Adobe as a UX designer on the PhoneGap team, and I > > have recently thrown some time at redesigning the > > http://plugins.cordova.io site. I'm looking for feedback prior to > > implementation - your thoughts are appreciated. > > > > The main screens that have been reworked are as follows: > > > > > > 1. Home (http://cl.ly/image/2n3l1N0Z0g0w) > > The primary goal for the site is to help users find the plugins they > need. > > As such, the main focus is on search/findability. > > > > 2. Search Results (http://cl.ly/image/0c3X3T1E1L0j) > > Upon search for a plugin, the user is returned results. The user can > > filter to include only desired platforms ( > http://cl.ly/image/3W2f321I211r), > > and the results table can be sorted by number of downloads, or plugin ID. > > > > 3. Plugin Details (http://cl.ly/image/2n1p2s3E0a2t) > > The details screen intends to provide all of the necessary information on > > a plugin. > > ** From what I understand, one piece of information that may be missing > > from this screen is "Installation Instructions". This being, config.xml > > feature tags. Is this something that you guys plan to automate, or should > > we be telling plugin authors to put this information in their Read Me? > > Please advise. > > > > Further, we do intend to make this a responsive site - so it will be > > easily viewed on smaller screen sizes. > > > > Thanks for your input, > > -joni > > > > > > PS - big thanks and kudos to Yohei for putting together the pluggy robot! > > > > > > >
Re: plugins.cordova.io: UX redesign
Shouldn't the little plugger have multiple prongs on it's head, so it can be universally applied, or is there a specially designed adapter-hat [1] that is not shown in that picture? Actually, thinking more about the gender thing, he is definitely male [2], on both ends even ... ? [1] http://img.alibaba.com/wsphoto/360207307/10pcs-lot-All-in-one-World-Travel-Adapter-Universal-Plug-Converter-US-UK-EU-AU-black.jpg [2] http://en.wikipedia.org/wiki/Gender_of_connectors_and_fasteners @purplecabbage risingj.com On Thu, Dec 12, 2013 at 4:41 PM, Shazron wrote: > Well of course Plugman makes sense, d'oh didn't think of that :) > (but erm... maybe we want to skip any gender specificity after that libuv > brouhaha) > > > On Thu, Dec 12, 2013 at 4:38 PM, Brian LeRoux wrote: > > > I vote that we call him Plugman > > > > (But his friends call him Pluggy =) > > > > > > On Fri, Dec 13, 2013 at 10:57 AM, Shazron wrote: > > > > > Awesome, love Pluggy(?) the robot. > > > > > > Some comments if I may: > > > 1. Plugin Details - maintainers should be linkable, so we can go to a > > list > > > of their authored packages (like npmjs) > > > 2. Plugin Details - not sure if we want "previous versions" here. npmjs > > > does this by appending the version to the url, but this is not > > discoverable > > > easily: eg https://npmjs.org/package/ios-sim --> > > > https://npmjs.org/package/ios-sim/1.8.0 . Ideally we want the user to > > > always grab the latest, but there will be cases where they might want > to > > > grab an older one for compatibility reasons, and they might not know > how, > > > even through the command line > > > 3. Plugin Details - I assume the Readme here is just pulled from the > > > Readme.md of the plugin package (like npmjs) - that will be great if so > > > > > > > > > On Wed, Dec 11, 2013 at 7:26 PM, Joni Rustulka wrote: > > > > > > > Hi all, > > > > > > > > I'm Joni. I work at Adobe as a UX designer on the PhoneGap team, and > I > > > > have recently thrown some time at redesigning the > > > > http://plugins.cordova.io site. I'm looking for feedback prior to > > > > implementation - your thoughts are appreciated. > > > > > > > > The main screens that have been reworked are as follows: > > > > > > > > > > > > 1. Home (http://cl.ly/image/2n3l1N0Z0g0w) > > > > The primary goal for the site is to help users find the plugins they > > > need. > > > > As such, the main focus is on search/findability. > > > > > > > > 2. Search Results (http://cl.ly/image/0c3X3T1E1L0j) > > > > Upon search for a plugin, the user is returned results. The user can > > > > filter to include only desired platforms ( > > > http://cl.ly/image/3W2f321I211r), > > > > and the results table can be sorted by number of downloads, or plugin > > ID. > > > > > > > > 3. Plugin Details (http://cl.ly/image/2n1p2s3E0a2t) > > > > The details screen intends to provide all of the necessary > information > > on > > > > a plugin. > > > > ** From what I understand, one piece of information that may be > missing > > > > from this screen is "Installation Instructions". This being, > config.xml > > > > feature tags. Is this something that you guys plan to automate, or > > should > > > > we be telling plugin authors to put this information in their Read > Me? > > > > Please advise. > > > > > > > > Further, we do intend to make this a responsive site - so it will be > > > > easily viewed on smaller screen sizes. > > > > > > > > Thanks for your input, > > > > -joni > > > > > > > > > > > > PS - big thanks and kudos to Yohei for putting together the pluggy > > robot! > > > > > > > > > > > > > > > > > >
Re: plugins.cordova.io: UX redesign
Well of course Plugman makes sense, d'oh didn't think of that :) (but erm... maybe we want to skip any gender specificity after that libuv brouhaha) On Thu, Dec 12, 2013 at 4:38 PM, Brian LeRoux wrote: > I vote that we call him Plugman > > (But his friends call him Pluggy =) > > > On Fri, Dec 13, 2013 at 10:57 AM, Shazron wrote: > > > Awesome, love Pluggy(?) the robot. > > > > Some comments if I may: > > 1. Plugin Details - maintainers should be linkable, so we can go to a > list > > of their authored packages (like npmjs) > > 2. Plugin Details - not sure if we want "previous versions" here. npmjs > > does this by appending the version to the url, but this is not > discoverable > > easily: eg https://npmjs.org/package/ios-sim --> > > https://npmjs.org/package/ios-sim/1.8.0 . Ideally we want the user to > > always grab the latest, but there will be cases where they might want to > > grab an older one for compatibility reasons, and they might not know how, > > even through the command line > > 3. Plugin Details - I assume the Readme here is just pulled from the > > Readme.md of the plugin package (like npmjs) - that will be great if so > > > > > > On Wed, Dec 11, 2013 at 7:26 PM, Joni Rustulka wrote: > > > > > Hi all, > > > > > > I'm Joni. I work at Adobe as a UX designer on the PhoneGap team, and I > > > have recently thrown some time at redesigning the > > > http://plugins.cordova.io site. I'm looking for feedback prior to > > > implementation - your thoughts are appreciated. > > > > > > The main screens that have been reworked are as follows: > > > > > > > > > 1. Home (http://cl.ly/image/2n3l1N0Z0g0w) > > > The primary goal for the site is to help users find the plugins they > > need. > > > As such, the main focus is on search/findability. > > > > > > 2. Search Results (http://cl.ly/image/0c3X3T1E1L0j) > > > Upon search for a plugin, the user is returned results. The user can > > > filter to include only desired platforms ( > > http://cl.ly/image/3W2f321I211r), > > > and the results table can be sorted by number of downloads, or plugin > ID. > > > > > > 3. Plugin Details (http://cl.ly/image/2n1p2s3E0a2t) > > > The details screen intends to provide all of the necessary information > on > > > a plugin. > > > ** From what I understand, one piece of information that may be missing > > > from this screen is "Installation Instructions". This being, config.xml > > > feature tags. Is this something that you guys plan to automate, or > should > > > we be telling plugin authors to put this information in their Read Me? > > > Please advise. > > > > > > Further, we do intend to make this a responsive site - so it will be > > > easily viewed on smaller screen sizes. > > > > > > Thanks for your input, > > > -joni > > > > > > > > > PS - big thanks and kudos to Yohei for putting together the pluggy > robot! > > > > > > > > > > > >
Re: plugins.cordova.io: UX redesign
I vote that we call him Plugman (But his friends call him Pluggy =) On Fri, Dec 13, 2013 at 10:57 AM, Shazron wrote: > Awesome, love Pluggy(?) the robot. > > Some comments if I may: > 1. Plugin Details - maintainers should be linkable, so we can go to a list > of their authored packages (like npmjs) > 2. Plugin Details - not sure if we want "previous versions" here. npmjs > does this by appending the version to the url, but this is not discoverable > easily: eg https://npmjs.org/package/ios-sim --> > https://npmjs.org/package/ios-sim/1.8.0 . Ideally we want the user to > always grab the latest, but there will be cases where they might want to > grab an older one for compatibility reasons, and they might not know how, > even through the command line > 3. Plugin Details - I assume the Readme here is just pulled from the > Readme.md of the plugin package (like npmjs) - that will be great if so > > > On Wed, Dec 11, 2013 at 7:26 PM, Joni Rustulka wrote: > > > Hi all, > > > > I'm Joni. I work at Adobe as a UX designer on the PhoneGap team, and I > > have recently thrown some time at redesigning the > > http://plugins.cordova.io site. I'm looking for feedback prior to > > implementation - your thoughts are appreciated. > > > > The main screens that have been reworked are as follows: > > > > > > 1. Home (http://cl.ly/image/2n3l1N0Z0g0w) > > The primary goal for the site is to help users find the plugins they > need. > > As such, the main focus is on search/findability. > > > > 2. Search Results (http://cl.ly/image/0c3X3T1E1L0j) > > Upon search for a plugin, the user is returned results. The user can > > filter to include only desired platforms ( > http://cl.ly/image/3W2f321I211r), > > and the results table can be sorted by number of downloads, or plugin ID. > > > > 3. Plugin Details (http://cl.ly/image/2n1p2s3E0a2t) > > The details screen intends to provide all of the necessary information on > > a plugin. > > ** From what I understand, one piece of information that may be missing > > from this screen is "Installation Instructions". This being, config.xml > > feature tags. Is this something that you guys plan to automate, or should > > we be telling plugin authors to put this information in their Read Me? > > Please advise. > > > > Further, we do intend to make this a responsive site - so it will be > > easily viewed on smaller screen sizes. > > > > Thanks for your input, > > -joni > > > > > > PS - big thanks and kudos to Yohei for putting together the pluggy robot! > > > > > > >
Re: plugins.cordova.io: UX redesign
Awesome, love Pluggy(?) the robot. Some comments if I may: 1. Plugin Details - maintainers should be linkable, so we can go to a list of their authored packages (like npmjs) 2. Plugin Details - not sure if we want "previous versions" here. npmjs does this by appending the version to the url, but this is not discoverable easily: eg https://npmjs.org/package/ios-sim --> https://npmjs.org/package/ios-sim/1.8.0 . Ideally we want the user to always grab the latest, but there will be cases where they might want to grab an older one for compatibility reasons, and they might not know how, even through the command line 3. Plugin Details - I assume the Readme here is just pulled from the Readme.md of the plugin package (like npmjs) - that will be great if so On Wed, Dec 11, 2013 at 7:26 PM, Joni Rustulka wrote: > Hi all, > > I'm Joni. I work at Adobe as a UX designer on the PhoneGap team, and I > have recently thrown some time at redesigning the > http://plugins.cordova.io site. I'm looking for feedback prior to > implementation - your thoughts are appreciated. > > The main screens that have been reworked are as follows: > > > 1. Home (http://cl.ly/image/2n3l1N0Z0g0w) > The primary goal for the site is to help users find the plugins they need. > As such, the main focus is on search/findability. > > 2. Search Results (http://cl.ly/image/0c3X3T1E1L0j) > Upon search for a plugin, the user is returned results. The user can > filter to include only desired platforms (http://cl.ly/image/3W2f321I211r), > and the results table can be sorted by number of downloads, or plugin ID. > > 3. Plugin Details (http://cl.ly/image/2n1p2s3E0a2t) > The details screen intends to provide all of the necessary information on > a plugin. > ** From what I understand, one piece of information that may be missing > from this screen is "Installation Instructions". This being, config.xml > feature tags. Is this something that you guys plan to automate, or should > we be telling plugin authors to put this information in their Read Me? > Please advise. > > Further, we do intend to make this a responsive site - so it will be > easily viewed on smaller screen sizes. > > Thanks for your input, > -joni > > > PS - big thanks and kudos to Yohei for putting together the pluggy robot! > > >
RE: plugins.cordova.io: UX redesign
I have some feedback about versions and the download counts. When a particular plugin (eg org.apache.cordova.XYZ) has multiple versions 0.1.0, 0.1.5, 0.2.0, 0.2.1, 0.2.3, 0.2.4 then how will the list of all those different versions displayed? And what does the download count mean in that case - is it count per id across all versions or for each version? For example, it is not so clear where clicking on a "Most Downloaded" link on the "home" page goes to - is it to the details page of the most downloaded version? E.g. maybe the plugin XYZ version v0.2.3 is most downloaded but that is only because XYZ v0.2.4 is very new and nobody is aware of it yet. Similarly, if the "search results" page is sorted by download counts maybe v0.2.3 has 10,000 downloads but the newer v0.2.4 has only 57 dowloads so falls off bottom of that results list. So the user might accidentally download what they believe is most popular and fetch v0.2.3 simply because they are unaware of a newer version of the same plugin. Or am I misreading this page, and that "Version" column actually means "*Latest* Version" (??) Users ought to be able to get any version of a plugin they want - perhaps they do not want the latest version, but it would be a pity if they accidentally didn't get the latest version simply because they didn't even know it existed. Maybe that plugin "details" page could always default to show the latest version but providing a "Version History" section on that page would help by giving links back to older versions of the same plugin id... 12 Dec 2013: v0.2.4, 57 downloads 25 Nov 2013: v0.2.3, 10,000 downloads 04 May 2013: v0.2.1, 6777 downloads 03 May 2013: v0.2.0, 16 downloads 12 Mar 2013: v0.1.5, 503 downloads 05 Jan 2013: v0.1.0, 50 downloads Cheers, Peter. -Original Message- From: Joni Rustulka [mailto:j...@adobe.com] Sent: Thursday, 12 December 2013 2:27 PM To: dev@cordova.apache.org Cc: Yohei Shimomae Subject: plugins.cordova.io: UX redesign Hi all, I'm Joni. I work at Adobe as a UX designer on the PhoneGap team, and I have recently thrown some time at redesigning the http://plugins.cordova.io site. I'm looking for feedback prior to implementation - your thoughts are appreciated. The main screens that have been reworked are as follows: 1. Home (http://cl.ly/image/2n3l1N0Z0g0w) The primary goal for the site is to help users find the plugins they need. As such, the main focus is on search/findability. 2. Search Results (http://cl.ly/image/0c3X3T1E1L0j) Upon search for a plugin, the user is returned results. The user can filter to include only desired platforms (http://cl.ly/image/3W2f321I211r), and the results table can be sorted by number of downloads, or plugin ID. 3. Plugin Details (http://cl.ly/image/2n1p2s3E0a2t) The details screen intends to provide all of the necessary information on a plugin. ** From what I understand, one piece of information that may be missing from this screen is "Installation Instructions". This being, config.xml feature tags. Is this something that you guys plan to automate, or should we be telling plugin authors to put this information in their Read Me? Please advise. Further, we do intend to make this a responsive site - so it will be easily viewed on smaller screen sizes. Thanks for your input, -joni PS - big thanks and kudos to Yohei for putting together the pluggy robot!
Re: plugins.cordova.io: UX redesign
Looks awesome, great work and sorely needed! I assume the filter is an ³and² operation? -- Ken Wallis Senior Product Manager - WebWorks BlackBerry 650-620-2404 -Original Message- From: Steven Gill Reply-To: "dev@cordova.apache.org" Date: Thursday, December 12, 2013 at 11:46 AM To: "dev@cordova.apache.org" Subject: Re: plugins.cordova.io: UX redesign >Awesome Job Joni! Love it! > >Carlos, I think the plan for 3 is to display the readme npm style. Good >suggestion ;). A template to give out would be a great idea. Maybe it gets >generated in the plugin create command (did that ever make it in?) > > >On Thu, Dec 12, 2013 at 11:36 AM, Josh Soref >wrote: > >> Jesse wrote: >> - Search prominence is great, >> >> >> but I am confused about the difference >> between what the 'Find Plugins' link at the top does, and the search >>box. >> >> I was confused too (+1) >> >> - Contribute, and Utilize seem to be given too much prominence here, and >> >> +1 >> >> I'm not crazy about the word 'Utilize'. >> >> +1 >> >> Maybe 'Get Started' with subs of 'Publish a plugin' and 'Install a >> plugin' ... ? >> >> - Plugin listing by ID seems overly geeky, can't we use the Name field? >> >> +1 >> >> can we include latest published date, >> >> +1 >> >> - It would be awesome if we could add some sort of image/logo to the >> publish process, >> >> +1 >> - >> This transmission (including any attachments) may contain confidential >> information, privileged material (including material protected by the >> solicitor-client or other applicable privileges), or constitute >>non-public >> information. Any use of this information by anyone other than the >>intended >> recipient is prohibited. If you have received this transmission in >>error, >> please immediately reply to the sender and delete this information from >> your system. Use, dissemination, distribution, or reproduction of this >> transmission by unintended recipients is not authorized and may be >>unlawful. >> >> - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Re: plugins.cordova.io: UX redesign
Awesome Job Joni! Love it! Carlos, I think the plan for 3 is to display the readme npm style. Good suggestion ;). A template to give out would be a great idea. Maybe it gets generated in the plugin create command (did that ever make it in?) On Thu, Dec 12, 2013 at 11:36 AM, Josh Soref wrote: > Jesse wrote: > - Search prominence is great, > > > but I am confused about the difference > between what the 'Find Plugins' link at the top does, and the search box. > > I was confused too (+1) > > - Contribute, and Utilize seem to be given too much prominence here, and > > +1 > > I'm not crazy about the word 'Utilize'. > > +1 > > Maybe 'Get Started' with subs of 'Publish a plugin' and 'Install a > plugin' ... ? > > - Plugin listing by ID seems overly geeky, can't we use the Name field? > > +1 > > can we include latest published date, > > +1 > > - It would be awesome if we could add some sort of image/logo to the > publish process, > > +1 > - > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute non-public > information. Any use of this information by anyone other than the intended > recipient is prohibited. If you have received this transmission in error, > please immediately reply to the sender and delete this information from > your system. Use, dissemination, distribution, or reproduction of this > transmission by unintended recipients is not authorized and may be unlawful. > >
Re: plugins.cordova.io: UX redesign
Jesse wrote: - Search prominence is great, but I am confused about the difference between what the 'Find Plugins' link at the top does, and the search box. I was confused too (+1) - Contribute, and Utilize seem to be given too much prominence here, and +1 I'm not crazy about the word 'Utilize'. +1 Maybe 'Get Started' with subs of 'Publish a plugin' and 'Install a plugin' ... ? - Plugin listing by ID seems overly geeky, can't we use the Name field? +1 can we include latest published date, +1 - It would be awesome if we could add some sort of image/logo to the publish process, +1 - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Re: plugins.cordova.io: UX redesign
Looks good Joni. Great tone, character and feel. Some of the utilitarian pieces I think need fine tuning. Re: 1. ( opinions, which may be misguided ) - Search prominence is great, but I am confused about the difference between what the 'Find Plugins' link at the top does, and the search box. - Contribute, and Utilize seem to be given too much prominence here, and I'm not crazy about the word 'Utilize'. Maybe 'Get Started' with subs of 'Publish a plugin' and 'Install a plugin' ... ? - Plugin listing by ID seems overly geeky, can't we use the Name field? Re: 2. - The Version column does not seem very useful, can we include latest published date, or is there some author information? Re: 3 - Perfect! - It would be awesome if we could add some sort of image/logo to the publish process, as we are going to be stuck with a very texty site otherwise. I think the nuget site is a very good example of a site based on doing a very similar thing. http://www.nuget.org/ Here is what knockoutjs looks like there: http://www.nuget.org/packages/knockoutjs/ @purplecabbage risingj.com On Thu, Dec 12, 2013 at 8:17 AM, Max Woghiren wrote: > Looks great indeed! > > > On Wed, Dec 11, 2013 at 10:26 PM, Joni Rustulka wrote: > > > Hi all, > > > > I'm Joni. I work at Adobe as a UX designer on the PhoneGap team, and I > > have recently thrown some time at redesigning the > > http://plugins.cordova.io site. I'm looking for feedback prior to > > implementation - your thoughts are appreciated. > > > > The main screens that have been reworked are as follows: > > > > > > 1. Home (http://cl.ly/image/2n3l1N0Z0g0w) > > The primary goal for the site is to help users find the plugins they > need. > > As such, the main focus is on search/findability. > > > > 2. Search Results (http://cl.ly/image/0c3X3T1E1L0j) > > Upon search for a plugin, the user is returned results. The user can > > filter to include only desired platforms ( > http://cl.ly/image/3W2f321I211r), > > and the results table can be sorted by number of downloads, or plugin ID. > > > > 3. Plugin Details (http://cl.ly/image/2n1p2s3E0a2t) > > The details screen intends to provide all of the necessary information on > > a plugin. > > ** From what I understand, one piece of information that may be missing > > from this screen is "Installation Instructions". This being, config.xml > > feature tags. Is this something that you guys plan to automate, or should > > we be telling plugin authors to put this information in their Read Me? > > Please advise. > > > > Further, we do intend to make this a responsive site - so it will be > > easily viewed on smaller screen sizes. > > > > Thanks for your input, > > -joni > > > > > > PS - big thanks and kudos to Yohei for putting together the pluggy robot! > > > > > > >
Re: plugins.cordova.io: UX redesign
Looks great indeed! On Wed, Dec 11, 2013 at 10:26 PM, Joni Rustulka wrote: > Hi all, > > I'm Joni. I work at Adobe as a UX designer on the PhoneGap team, and I > have recently thrown some time at redesigning the > http://plugins.cordova.io site. I'm looking for feedback prior to > implementation - your thoughts are appreciated. > > The main screens that have been reworked are as follows: > > > 1. Home (http://cl.ly/image/2n3l1N0Z0g0w) > The primary goal for the site is to help users find the plugins they need. > As such, the main focus is on search/findability. > > 2. Search Results (http://cl.ly/image/0c3X3T1E1L0j) > Upon search for a plugin, the user is returned results. The user can > filter to include only desired platforms (http://cl.ly/image/3W2f321I211r), > and the results table can be sorted by number of downloads, or plugin ID. > > 3. Plugin Details (http://cl.ly/image/2n1p2s3E0a2t) > The details screen intends to provide all of the necessary information on > a plugin. > ** From what I understand, one piece of information that may be missing > from this screen is "Installation Instructions". This being, config.xml > feature tags. Is this something that you guys plan to automate, or should > we be telling plugin authors to put this information in their Read Me? > Please advise. > > Further, we do intend to make this a responsive site - so it will be > easily viewed on smaller screen sizes. > > Thanks for your input, > -joni > > > PS - big thanks and kudos to Yohei for putting together the pluggy robot! > > >
Re: plugins.cordova.io: UX redesign
Looks awesome! We've been needing this for a while! Great job, thanks! +1 to Carlos' suggestion above of providing users a readme.md template that they can fill out that we just display on the plugin info page. If they provide nothing, we can probably auto fill this with the registry information. If they need to provide more information for more complicated setup, this will be an easy way to provide that info without cramming it in the description or something else. On Thu, Dec 12, 2013 at 8:57 AM, Dick Van den Brink < d_vandenbr...@outlook.com> wrote: > Nice Joni! > Really love the plugin robot! :) > > Also a +1 for making it responsive. > > > > > Subject: Re: plugins.cordova.io: UX redesign > > From: wjamesj...@gmail.com > > Date: Thu, 12 Dec 2013 08:38:06 -0500 > > CC: yo...@adobe.com > > To: dev@cordova.apache.org > > > > UX looks great!! Thanks for the efforts! > > > > 2. For search, perhaps the ability to add/remove filters? > > > > +1 to making it responsive > > > > -James Jong > > > > On Dec 11, 2013, at 10:26 PM, Joni Rustulka wrote: > > > >> Hi all, > >> > >> I'm Joni. I work at Adobe as a UX designer on the PhoneGap team, and I > have recently thrown some time at redesigning the > http://plugins.cordova.io site. I'm looking for feedback prior to > implementation - your thoughts are appreciated. > >> > >> The main screens that have been reworked are as follows: > >> > >> > >> 1. Home (http://cl.ly/image/2n3l1N0Z0g0w) > >> The primary goal for the site is to help users find the plugins they > need. As such, the main focus is on search/findability. > >> > >> 2. Search Results (http://cl.ly/image/0c3X3T1E1L0j) > >> Upon search for a plugin, the user is returned results. The user can > filter to include only desired platforms (http://cl.ly/image/3W2f321I211r), > and the results table can be sorted by number of downloads, or plugin ID. > >> > >> 3. Plugin Details (http://cl.ly/image/2n1p2s3E0a2t) > >> The details screen intends to provide all of the necessary information > on a plugin. > >> ** From what I understand, one piece of information that may be missing > from this screen is "Installation Instructions". This being, config.xml > feature tags. Is this something that you guys plan to automate, or should > we be telling plugin authors to put this information in their Read Me? > Please advise. > >> > >> Further, we do intend to make this a responsive site - so it will be > easily viewed on smaller screen sizes. > >> > >> Thanks for your input, > >> -joni > >> > >> > >> PS - big thanks and kudos to Yohei for putting together the pluggy > robot! > >> > >> > > >
RE: plugins.cordova.io: UX redesign
Nice Joni! Really love the plugin robot! :) Also a +1 for making it responsive. > Subject: Re: plugins.cordova.io: UX redesign > From: wjamesj...@gmail.com > Date: Thu, 12 Dec 2013 08:38:06 -0500 > CC: yo...@adobe.com > To: dev@cordova.apache.org > > UX looks great!! Thanks for the efforts! > > 2. For search, perhaps the ability to add/remove filters? > > +1 to making it responsive > > -James Jong > > On Dec 11, 2013, at 10:26 PM, Joni Rustulka wrote: > >> Hi all, >> >> I'm Joni. I work at Adobe as a UX designer on the PhoneGap team, and I have >> recently thrown some time at redesigning the http://plugins.cordova.io site. >> I'm looking for feedback prior to implementation - your thoughts are >> appreciated. >> >> The main screens that have been reworked are as follows: >> >> >> 1. Home (http://cl.ly/image/2n3l1N0Z0g0w) >> The primary goal for the site is to help users find the plugins they need. >> As such, the main focus is on search/findability. >> >> 2. Search Results (http://cl.ly/image/0c3X3T1E1L0j) >> Upon search for a plugin, the user is returned results. The user can filter >> to include only desired platforms (http://cl.ly/image/3W2f321I211r), and the >> results table can be sorted by number of downloads, or plugin ID. >> >> 3. Plugin Details (http://cl.ly/image/2n1p2s3E0a2t) >> The details screen intends to provide all of the necessary information on a >> plugin. >> ** From what I understand, one piece of information that may be missing from >> this screen is "Installation Instructions". This being, config.xml feature >> tags. Is this something that you guys plan to automate, or should we be >> telling plugin authors to put this information in their Read Me? Please >> advise. >> >> Further, we do intend to make this a responsive site - so it will be easily >> viewed on smaller screen sizes. >> >> Thanks for your input, >> -joni >> >> >> PS - big thanks and kudos to Yohei for putting together the pluggy robot! >> >> >
Re: plugins.cordova.io: UX redesign
Those comps look great Joni! Nice work! The details page needs a way to view prior versions. On Thu, Dec 12, 2013 at 8:38 AM, James Jong wrote: > UX looks great!! Thanks for the efforts! > > 2. For search, perhaps the ability to add/remove filters? > > +1 to making it responsive > > -James Jong > > On Dec 11, 2013, at 10:26 PM, Joni Rustulka wrote: > > > Hi all, > > > > I'm Joni. I work at Adobe as a UX designer on the PhoneGap team, and I > have recently thrown some time at redesigning the > http://plugins.cordova.io site. I'm looking for feedback prior to > implementation - your thoughts are appreciated. > > > > The main screens that have been reworked are as follows: > > > > > > 1. Home (http://cl.ly/image/2n3l1N0Z0g0w) > > The primary goal for the site is to help users find the plugins they > need. As such, the main focus is on search/findability. > > > > 2. Search Results (http://cl.ly/image/0c3X3T1E1L0j) > > Upon search for a plugin, the user is returned results. The user can > filter to include only desired platforms (http://cl.ly/image/3W2f321I211r), > and the results table can be sorted by number of downloads, or plugin ID. > > > > 3. Plugin Details (http://cl.ly/image/2n1p2s3E0a2t) > > The details screen intends to provide all of the necessary information > on a plugin. > > ** From what I understand, one piece of information that may be missing > from this screen is "Installation Instructions". This being, config.xml > feature tags. Is this something that you guys plan to automate, or should > we be telling plugin authors to put this information in their Read Me? > Please advise. > > > > Further, we do intend to make this a responsive site - so it will be > easily viewed on smaller screen sizes. > > > > Thanks for your input, > > -joni > > > > > > PS - big thanks and kudos to Yohei for putting together the pluggy robot! > > > > > >
Re: plugins.cordova.io: UX redesign
UX looks great!! Thanks for the efforts! 2. For search, perhaps the ability to add/remove filters? +1 to making it responsive -James Jong On Dec 11, 2013, at 10:26 PM, Joni Rustulka wrote: > Hi all, > > I'm Joni. I work at Adobe as a UX designer on the PhoneGap team, and I have > recently thrown some time at redesigning the http://plugins.cordova.io site. > I'm looking for feedback prior to implementation - your thoughts are > appreciated. > > The main screens that have been reworked are as follows: > > > 1. Home (http://cl.ly/image/2n3l1N0Z0g0w) > The primary goal for the site is to help users find the plugins they need. As > such, the main focus is on search/findability. > > 2. Search Results (http://cl.ly/image/0c3X3T1E1L0j) > Upon search for a plugin, the user is returned results. The user can filter > to include only desired platforms (http://cl.ly/image/3W2f321I211r), and the > results table can be sorted by number of downloads, or plugin ID. > > 3. Plugin Details (http://cl.ly/image/2n1p2s3E0a2t) > The details screen intends to provide all of the necessary information on a > plugin. > ** From what I understand, one piece of information that may be missing from > this screen is "Installation Instructions". This being, config.xml feature > tags. Is this something that you guys plan to automate, or should we be > telling plugin authors to put this information in their Read Me? Please > advise. > > Further, we do intend to make this a responsive site - so it will be easily > viewed on smaller screen sizes. > > Thanks for your input, > -joni > > > PS - big thanks and kudos to Yohei for putting together the pluggy robot! > >
Re: plugins.cordova.io: UX redesign
That. Is. So. Exciting! Also, PLUGIN ROBOT On 12 Dec 2013, at 2:26 pm, Joni Rustulka wrote: > Hi all, > > I'm Joni. I work at Adobe as a UX designer on the PhoneGap team, and I have > recently thrown some time at redesigning the http://plugins.cordova.io site. > I'm looking for feedback prior to implementation - your thoughts are > appreciated. > > The main screens that have been reworked are as follows: > > > 1. Home (http://cl.ly/image/2n3l1N0Z0g0w) > The primary goal for the site is to help users find the plugins they need. As > such, the main focus is on search/findability. > > 2. Search Results (http://cl.ly/image/0c3X3T1E1L0j) > Upon search for a plugin, the user is returned results. The user can filter > to include only desired platforms (http://cl.ly/image/3W2f321I211r), and the > results table can be sorted by number of downloads, or plugin ID. > > 3. Plugin Details (http://cl.ly/image/2n1p2s3E0a2t) > The details screen intends to provide all of the necessary information on a > plugin. > ** From what I understand, one piece of information that may be missing from > this screen is "Installation Instructions". This being, config.xml feature > tags. Is this something that you guys plan to automate, or should we be > telling plugin authors to put this information in their Read Me? Please > advise. > > Further, we do intend to make this a responsive site - so it will be easily > viewed on smaller screen sizes. > > Thanks for your input, > -joni > > > PS - big thanks and kudos to Yohei for putting together the pluggy robot! > >
Re: plugins.cordova.io: UX redesign
I think I may want plugins compatible with Cordova version X or license Y. (License may be "not in Z...") - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Re: plugins.cordova.io: UX redesign
Shoot. I was going to go to bed, but now I'm too excited! These look AWESOME! Put some nitpicks below, but pretty much I think it's perfect! On Wed, Dec 11, 2013 at 10:26 PM, Joni Rustulka wrote: > Hi all, > > I'm Joni. I work at Adobe as a UX designer on the PhoneGap team, and I > have recently thrown some time at redesigning the > http://plugins.cordova.io site. I'm looking for feedback prior to > implementation - your thoughts are appreciated. > > The main screens that have been reworked are as follows: > > > 1. Home (http://cl.ly/image/2n3l1N0Z0g0w) > The primary goal for the site is to help users find the plugins they need. > As such, the main focus is on search/findability. > Might consider doing away with "Find Plugins" and "Analytics" top-nav links - Don't feel strongly about it, but we might be able to get away without them. e.g. click the banner to get back to front page & have the front page have a link to analytics on it somewhere (I don't think analytics needs to be prominently linked to.) > > 2. Search Results (http://cl.ly/image/0c3X3T1E1L0j) > Upon search for a plugin, the user is returned results. The user can > filter to include only desired platforms (http://cl.ly/image/3W2f321I211r), > and the results table can be sorted by number of downloads, or plugin ID. > - Love that search results has a filter by platform - Would be neat if the search results page showed supported platforms as well > > 3. Plugin Details (http://cl.ly/image/2n1p2s3E0a2t) > The details screen intends to provide all of the necessary information on > a plugin. > ** From what I understand, one piece of information that may be missing > from this screen is "Installation Instructions". This being, config.xml > feature tags. Is this something that you guys plan to automate, or should > we be telling plugin authors to put this information in their Read Me? > Please advise. > > - Maybe get rid of the "Back to search results" link? - Users can use the browser back button for this - The link won't make sense if you went directly to the page (not through search results) - Ditch the "Copy to Clipboard" button. - AFAIK, we can't implement that Further, we do intend to make this a responsive site - so it will be easily > viewed on smaller screen sizes. > > Thanks for your input, > -joni > > > PS - big thanks and kudos to Yohei for putting together the pluggy robot! > > >
Re: plugins.cordova.io: UX redesign
This looks awesome Joni The plugin robot looks rad! for #3 details view, now I looked at your mockup it looks we are missing that info from the plugin Maybe it will make sense that we take same approach as NPM and use a readme markdown file per plugin, and render in details view we could provide a template that people should follow to allow some sort of consistency for the details view On Wed, Dec 11, 2013 at 10:26 PM, Joni Rustulka wrote: > Hi all, > > I'm Joni. I work at Adobe as a UX designer on the PhoneGap team, and I > have recently thrown some time at redesigning the > http://plugins.cordova.io site. I'm looking for feedback prior to > implementation - your thoughts are appreciated. > > The main screens that have been reworked are as follows: > > > 1. Home (http://cl.ly/image/2n3l1N0Z0g0w) > The primary goal for the site is to help users find the plugins they need. > As such, the main focus is on search/findability. > > 2. Search Results (http://cl.ly/image/0c3X3T1E1L0j) > Upon search for a plugin, the user is returned results. The user can > filter to include only desired platforms (http://cl.ly/image/3W2f321I211r), > and the results table can be sorted by number of downloads, or plugin ID. > > 3. Plugin Details (http://cl.ly/image/2n1p2s3E0a2t) > The details screen intends to provide all of the necessary information on > a plugin. > ** From what I understand, one piece of information that may be missing > from this screen is "Installation Instructions". This being, config.xml > feature tags. Is this something that you guys plan to automate, or should > we be telling plugin authors to put this information in their Read Me? > Please advise. > > Further, we do intend to make this a responsive site - so it will be > easily viewed on smaller screen sizes. > > Thanks for your input, > -joni > > > PS - big thanks and kudos to Yohei for putting together the pluggy robot! > > > -- Carlos Santana
