Hi, I like it a lot! Thanks to everyone for the great work!
my 2 cents: * optional dependencies are not labeled as such, but should be. It's an important info that shows which additional plugins will be installed or not * the search for maintainers should be improved. I only maintain the Job DSL plugin, but the page shows 7 plugins and the most relevant (Job DSL) is shown last. http://cloudbees-plugin-site-staging.s3-website-us-east-1.amazonaws.com/?maintainers=Daniel%20Spilker * what is the workflow for editing the page? is the data pulled from Confluence frequently? Daniel On Wed, Aug 31, 2016 at 1:07 PM, Daniel Beck <[email protected]> wrote: > Hi everyone, > > As previously discussed[1], Jenkins users would benefit from a better > plugins index. Right now, all they have is the 'Plugins' wiki page[2] and > there's so much wrong with it, one wonders whether it gets anything right. > Which leaves users to basically use Google to find things -- clearly not a > great situation for a tool like Jenkins, whose major appeal is in the large > and growing number of plugins and what they enable users to do. > > So Gus and Michael McCaskill have recently worked on building a better > plugins index -- the plugins site, to be integrated with jenkins.io -- > which itself was only recently overhauled to be actually useful for more > than just the changelog. Initial designs were presented a few months ago[3]. > > A lot of progress has been made over the last few weeks, and we finally > managed to deploy the work in progress to a public site: > http://cloudbees-plugin-site-staging.s3-website-us-east-1.amazonaws.com/ > > This pretty much looks like the finished site could. A few things worth > mentioning: > > * Index page shows most installed, recently updated, and trending (i.e. > rapidly growing adoption) plugins. > * Shiny URL for plugins (which will be something like > plugins.jenkins.io/git once productive) > * Three different list visualizations: Grid, List, and Table. > * Filter by maintainer (which as metadata is a bit of a mess due to > inconsistencies in POMs, but we try) > * It includes the Jenkins wiki page contents of the plugin (for now, could > do something like allow opt-in to GitHub based docs in the future) > > There's a few glitches left, but we wanted to get this work in progress > out to get your feedback. Things like which plugin categories show up, and > how they're labeled, is really easy to change at any time, so don't let > that distract you. Love it? Hate it? Please let me know! > > Daniel > > > 1: Roughly starting at https://groups.google.com/d/ > msg/jenkinsci-dev/EMbE3a4u8nA/WiNpTSM4CgAJ > 2: https://wiki.jenkins-ci.org/display/JENKINS/Plugins > 3: https://groups.google.com/d/msg/jenkinsci-dev/2nqWoE1FfOo/2EX2-l9dBQAJ > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-dev/679434B9-A494-4775-9153-3A816D46FB5E%40beckweb.net. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAKqW32ADOH6Tup69UT-bqb2XE7Eope6q59mCZ55djZma1Na%2BtA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
