On 08.10.2015, at 01:45, Daniel Beck <[email protected]> wrote: > So from aggregating existing comments it looks to me like the following seems > to be at least a reasonable basis for further discussion: > > * Use a static site generator with a Git repo on GitHub as the source for the > site. Goal: Allow community to contribute content. > [Updated Confluence could also work, but would retain the problems of > unreviewed content, comments, and non-plain text editing.] > * Have actual content, like good documentation, especially for getting > started. This includes moving some of the wiki's content into the site. > * Feature the blog [and possibly the event calendar] more prominently. > * Do not have "comments everywhere", limit to specific sections like the blog. > * Make it easy to contribute, possibly through having an "Edit" ("Improve > this page"?) link on every page, if possible. > > Comments?
Based on the discussion in this and related threads, and some existing sites used as "inspiration" I published my own "vision" for the new site. Just like Gus's, this is mostly a means to move the discussion along, so if you think some (or all) of my ideas are terrible, tell everyone in this thread. https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+2.0+Website+vision+from+Daniel+Beck -- 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/C28C9820-4EFC-4EFE-BAD6-2DEF342940AF%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
