2015-10-08 20:36 GMT+02:00 Gus Reiber <[email protected]>: > Yeah, so if I am understanding you correctly, Robert, you are saying that > you would like to be able to highlight some bits of content over others? I > would think that would just be a matter of marking particular content > pieces with a tag that pushes them to the top of the homepage. It also > sounds like you are suggesting these so marked articles should have some > marketing-ish goop associated with them. > > ....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. And in that list of things, I would imagine some list of themes/examples of customizations (i.e. plugins), and in the end some kind of sentence like "You didn't find the thing you're looking for? You can write write one plugin for your precise needs => link to 'how to extend by creating a plugin'". > Sure we need to be able to get to blogs and events and doc, but so do > these sites, and they do. Compare that with http://arquillian.org/, which > is a prefectly fine site, but page 1 packs no punch in part becuase it > lacks a particular angle to the story it wants to tell. Yawn, yawn, they > have a blog.... and events and stuff... > > What concerns me about the technology discussion, is that if you buy my > pitch that the second most important thing Jenkins-ci.org does today > (behind allowing the download of Jenkins) is hosting the plugins, there is > a whole set of things we need to start doing in order to do that right. The > essence of that effort will be blending metadata from the plugin author, > community users, and a site curator and then serving that up to the user in > a flexible fashion. > +1. Showing off a list of plugins is a work per-se. Thinking out loud here, but I suppose the categorization's work going on for the wizard could somehow be reused/factorized here. > There are some real technical challenges there and if anything, it seems > like moving to a more static site model is a move away from providing that > value. Maybe not. I just am not seeing the glue that would hold the > anonymous markdown files together. I am sure it can be done. > That would btw be another subject (flamewar?): would we stick to markdown, or asciidoc? (I'm for the latter... Markdown does not actually really exist, there are markdownS... Flavours etc.) -- 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/CANWgJS7gXeUymiVck983Dy093DWswm1VqD-cBLDgMkRbeq12Qg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
