Assuming the plugins moved into the static model and didn't remain in the Wiki side. Personally I think that perhaps we are trying to bite off too much in one chunk. Would a good starting point be taking a small part of the site (e.g. the Drupal + some basic getting started type stuff) and doing that first. From there people will have a much better idea on how its working and what will work and what won't.
In all of this I'd still like to have a discussion on how we might get Confluence up to a modern version which would, I think, allow for a lot of the "features" that we are looking for for some of the content at least. Richard. On Fri, 9 Oct 2015 at 23:18 Robert Sandell <[email protected]> wrote: > Back to the tech, > > If we go for a static site generation with a PR model I believe we need to > have the individual plugin pages distributed somehow, because if everything > is centralized to one repo with a PR model then we could risk loosing the > wonderful silo model we currently have with plugins. I think we would need > some way for plugin devs to handle their documentation pages independantly > of waiting for someone to approve and merge their PR. > Even if we give commit rights to frequent contributors of the site new > plugin maintainers wouldn't necessarily get that access and will have > problems releasing their plugin (since we nowadays require an existing wiki > page in the pom). > But if we, as an example, gather them up in the site build process from > the "jenkins-pages" branch of each plugin then there would be more autonomy > for the plugin docs and they would get their silo back. > > /B > > On Fri, Oct 9, 2015 at 11:49 AM, Robert Sandell <[email protected]> > wrote: > >> I'm saying YES to showcase the plugins, but NO to hiding the >> extensibility way down the plugin list. >> IMHO the extensibility documentation is equally important as the plugins >> themselves and the user and installation guides, i.e. it should not be more >> than one click (and no scrolling) from the main page to get to the >> "introduction to extending Jenkins" documentation with further links to >> everything else like the list of extension points, tutorials, javadoc etc. >> >> I just wanted to highlight that so it doesn't disappear behind the >> "Documentation link" while discussing site content. >> >> /B >> >> On Fri, Oct 9, 2015 at 1:22 AM, Gus Reiber <[email protected]> wrote: >> >>> Oh no.... The internet never forgets! >>> ...tonight I am going to party like it is 1999: >>> >>> https://web.archive.org/web/20000816062846/http://devex.allaire.com/developer/gallery/index.cfm >>> >>> ...I take it back. >>> App Stores are way, way, way sexier. >>> >>> On Thu, Oct 8, 2015 at 2:06 PM, Christopher Orr <[email protected]> wrote: >>> >>>> Thanks for the explanation, and video! Do you have any old screenshots >>>> of the Allaire stuff, out of curiosity? >>>> >>>> That grid does seems nice, and yeah, we do know which plugins are newest >>>> (I'm a fan of @jenkins_release) though I do prefer the version without >>>> icons.. :) >>>> >>>> Getting plugin developers to *name* their plugin in a reasonable (and >>>> consistent) way is hard enough, never mind getting them to add a wiki >>>> page, and then add a short but meaningful description there... so I'm >>>> going to be pessimistic about icons, I'm afraid. >>>> >>>> Regards, >>>> Chris >>>> >>>> >>>> On 08/10/15 22:58, Gus Reiber wrote: >>>> > I think plugins are almost exactly like apps in an app store. Way back >>>> > when I worked at Allaire, we (Mike Nimer and I) built a Developer's >>>> > exchange that featured CFML applets and code snippets. That experience >>>> > was designed very much like today's app-stores (but with older and >>>> > crappier web-tech). It wasn't as sex as an app-store, but a lot sexier >>>> > than random text articles. They also had interesting metadata that was >>>> > associated with them, that again matches our plugins almost exactly: >>>> > Their review ranking, installation share (% of Jenkins users using >>>> this >>>> > plugin), a category badge ...and though I have gotten negative >>>> pushback >>>> > about this before, I don't think it would unreasonable to ask plugin >>>> > authors to give their plugin an icon. >>>> > >>>> > ...something like this, but more of a website form factor than an >>>> in-app >>>> > form factor: >>>> > https://www.youtube.com/watch?v=kcxKvyX4Oq8 >>>> > https://www.youtube.com/watch?v=9vPUMe3lzfo >>>> > >>>> > ...the form factor isn't quite right for a website, but yeah, the >>>> > sorting, grouping, categorizing is pretty close. >>>> > >>>> > ...the fresh content is new plugins or plugins that are freshly >>>> updated. >>>> > The other fresh content is the reviews of those plugins. We can >>>> automate >>>> > which plugins we show based on user feedback. >>>> > >>>> > On Thu, Oct 8, 2015 at 1:28 PM, Christopher Orr <[email protected] >>>> > <mailto:[email protected]>> wrote: >>>> > >>>> > On 08/10/15 21:44, Baptiste Mathus wrote: >>>> > > 2015-10-08 20:36 GMT+02:00 Gus Reiber <[email protected] >>>> <mailto:[email protected]> >>>> > > <mailto:[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 a topic in >>>> > the Google Groups "Jenkins Developers" group. >>>> > To unsubscribe from this topic, visit >>>> > >>>> https://groups.google.com/d/topic/jenkinsci-dev/EMbE3a4u8nA/unsubscribe >>>> . >>>> > To unsubscribe from this group and all its topics, send an email >>>> to >>>> > [email protected] >>>> > <mailto:jenkinsci-dev%[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. >>>> > >>>> > >>>> > -- >>>> > 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] >>>> > <mailto:[email protected]>. >>>> > To view this discussion on the web visit >>>> > >>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAOcHHXyU-ExO7EJMK_LofNfhyffnV-Cp144rKLX8f9%3D-OpO2kQ%40mail.gmail.com >>>> > < >>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAOcHHXyU-ExO7EJMK_LofNfhyffnV-Cp144rKLX8f9%3D-OpO2kQ%40mail.gmail.com?utm_medium=email&utm_source=footer >>>> >. >>>> > For more options, visit https://groups.google.com/d/optout. >>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Jenkins Developers" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/jenkinsci-dev/EMbE3a4u8nA/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/5616DAF0.7080405%40orr.me.uk >>>> . >>>> 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/CAOcHHXzY%2BBujzs1h-WDf6UYrk7%3DgN9QyKhVRPqBREr2kx1dA%2BA%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAOcHHXzY%2BBujzs1h-WDf6UYrk7%3DgN9QyKhVRPqBREr2kx1dA%2BA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Robert Sandell >> *Software Engineer* >> *CloudBees Inc.* >> > > > > -- > Robert Sandell > *Software Engineer* > *CloudBees Inc.* > > -- > 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/CALzHZS14gS%3DZV3PbMRoya%2B1fSgT7q%3DPyqrjjQLJMSy7hLbksfg%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS14gS%3DZV3PbMRoya%2B1fSgT7q%3DPyqrjjQLJMSy7hLbksfg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > 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/CAMui947q8uth0bwCvJo%3D7oWSQLXt-bQY3%3D7yM0YSQoYjF_B5jA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
