On 09.10.2015, at 12:24, Richard Bywater <[email protected]> wrote: > 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.
Updating to a more modern Confluence version would be great. But I wonder what that would mean for the future site plans. What I mean by that is that it still would not address any of the following, all of which have been mentioned in the course of this discussion (and not just by me ;-) ): - Terrible comments everywhere and nobody to moderate them - No review of any documentation updates or additions, and there's value in having some well structured and reviewed docs - Some prefer "wiki syntax" editing and Confluence only offers WYSIWYG in newer versions I think - UX disconnect when moving immediately from the site to the wiki as today OTOH the advantage is easier editing in the browser. But I think we can make this relatively easy on the new site as well. For that I've set up a VERY minimal demo of what we could do: http://daniel-beck.github.io/jenkins-site-demo/ (The repo for this is https://github.com/daniel-beck/jenkins-site-demo ) It's basically the default generated Jekyll site, with a minor addition: If you visit "About" or "Welcome to Jekyll!", both pages offer to "Improve this page", linking to the GitHub editing interface. If you don't have commit access, GitHub will fork, branch, and create a PR. Feel free to play around with this a bit. Ping me on IRC if you want me to merge a PR. -- 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/DEB7C637-C3AB-417A-9651-B76CBB2A3F4C%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
