On Wednesday, 7 October 2015 13:51:15 UTC+2, James Nord wrote: > > One thing I just realize is that we have our documentation (javadocs) on a > separate website. > Most sites these days just have a "documentation " section which will also > have an api section within the same site (and themed in an approriate > manner) such that you have a more cohesive view (and have something that > actually makes you want to come back to the site. > > We should also have separate javadocs for the latest LTS as well as > bleeding edge (you could make the case for keeping a certain number of > javadocs for prior LTS versions - you can still get Spring 2.0 javadocs > online even if it is not supported!) > > and (ot as the design goes) ssl-everywhere will be required as Google will > start ranking secure sites higher in the future. >
Amen to that. The idea of having release notes/ changelogs/ etc per release can be taken from how Atlassian does that on Confluence. Maybe just upgrading Confluence and reorganizing the website (maybe with a custom theme) makes sense? Regards, Radek -- 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/ed2de476-7061-4729-8357-0c1c9d8eb357%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
