On 08/10/15 21:44, Baptiste Mathus wrote: > 2015-10-08 20:36 GMT+02:00 Gus Reiber <[email protected] > <mailto:[email protected]>>: > ....Personally, I think the demonstration of Jenkins extensibility > is more impressive than the saying of it. And, that demonstration is > the plugins. Thus rather than an article that say 'hey look, we are > extensible', I would think we would just want to go straight into > showing off the plugins, just as http://getbootstrap.com/ goes > straight into showing you Bootstrap or the Play store goes straight > into showing you the Andoid apps or http://www.deviantart.com/ goes > straight into showing you the art. To me, showing off the plugins > screams extensibility and the content stays fresh by virtue of the > fact that people are interacting with the plugins themselves. > > You convinced me Gus. > > IMO, we can indeed show off the plugins, showing the enormous numbers of > themes where Jenkins can actually change its behaviour by being > extensible and having been extended by plugins.
My question is: how do you "show off a plugin"? Jenkins plugins aren't Bootstrap themes, nor are they Android apps — the most you could show off for the vast majority of plugins would be a screenshot of an ugly configuration form. I'm not sure what "the content stays fresh" means in this context, and who (and how) people are "interacting with the plugins" on the website? Is the idea to have specially-written content (i.e. separate from the wiki page that every plugin has), which highlights key plugins on the main website? Regards, Chris -- 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/5616D1D0.4050609%40orr.me.uk. For more options, visit https://groups.google.com/d/optout.
