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 <b...@brian.io> wrote: > I vote that we call him Plugman > > (But his friends call him Pluggy =) > > > On Fri, Dec 13, 2013 at 10:57 AM, Shazron <shaz...@gmail.com> 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 <j...@adobe.com> 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! > > > > > > > > > > > >
