Tried out the demo you had setup - overall I think it is good for content that doesn't change too often but I worry about content that changes on a regular basis or trying to get somebody who isn't that upskilled in things like GitHub to understand and follow the process. (e.g. The fact that after making a change you then have to click on the "Create a PR request button" and then you need to work out how to get back to where you were on the site type thing)
Now I'm not terribly tied to Confluence (even though me going on about it so much might look like it :) ) but figured I'd provide some counter-argument to your points: - Terrible comments everywhere and nobody to moderate them I'd say to solve this you'd either turn comments off completely or use something like https://marketplace.atlassian.com/plugins/com.bugsio.confluence.plugins.external-comments to use Disqus instead - No review of any documentation updates or additions, and there's value in having some well structured and reviewed docs Agreed although the counter to this is that then there's a delay in getting your content live and requires someone to actively traverse the approval queue. In Confluence there's also some options for this type of things by the looks (although never looked at them myself) : https://confluence.atlassian.com/pages/viewpage.action?pageId=179438967 - Some prefer "wiki syntax" editing and Confluence only offers WYSIWYG in newer versions I think I'd say there's also a large number of people who prefer WYSIWYG as well - this probably comes down to the audience of who we are expecting to make changes. For me, I don't deal in Markdown all day and so Markdown is a (re)learning experience everytime I come to it :) - UX disconnect when moving immediately from the site to the wiki as today Agreed by default you get this but you I think that could be fixed with some work. For instance, as I've previously posted it, some of Atlassian's site is now powered by https://marketplace.atlassian.com/plugins/com.k15t.scroll.scroll-viewport which allows to make Wiki pages look a bit more "normal" Also just one more thing to mention that comes to mind about the fact that we possibly wouldn't want to use the cloud version of Confluence due to it not integrating with our LDAP, wouldn't a Github based solution suffer from the same problem? (Yes, quite a large number of people have a Github account, but its still not linked in with our LDAP and is therefore just a separate account off to one side) Just some more food for thought! Richard. On Sat, 10 Oct 2015 at 00:41 Daniel Beck <[email protected]> wrote: > > 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. > -- 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/CAMui947EO1MH7hr-XUGZq2rct293z56%3DMkdyyDqZbQtctDOWLw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
