2.0 website: tech track

[Kohsuke Kawaguchi]

I'm dividing up the website conversation into several tracks. See this Wiki page for the overall structure.

My summary of the tech track discussion so far is that:

• There's a proposal on the table best summarized in this post and then in this Wiki page. This proposal seems to have a good support
• Some others are pushing back on the plan
• Content contributions would be too hard in this scheme (post)
• Running static site generator can be harder than you think

I think Tyler is suggesting that he wants to create a prototype.

Please continue the discussion in this thread...

--

Kohsuke Kawaguchi

[Jesse Glick]

On Fri, Oct 9, 2015 at 6:54 PM, Kohsuke Kawaguchi <k...@kohsuke.org> wrote:
> There's a proposal on the table best summarized in this post and then in
> this Wiki page. This proposal seems to have a good support

LGTM but is unclear on what content would *remain* in the wiki, at
least in the “advanced intermediate state”.

[Daniel Beck]

On 12.10.2015, at 14:55, Jesse Glick <jgl...@cloudbees.com> wrote:

> LGTM but is unclear on what content would *remain* in the wiki, at
> least in the “advanced intermediate state”.

Look at https://wiki.jenkins-ci.org/pages/listpages-dirview.action?key=JENKINS to get an overview of what's there. My proposal mentions what would be moved. Basically "the rest" would remain. Note that this can be implemented in stages if need be, so there's a rather fluid divider line. If my proposal were implemented as described, the following would remain in the wiki:

- Parts of "Use Jenkins" (depending on how much we end up moving, not every wiki page needs to be on the site; some will require restructuring etc.).
- All of the developer documentation (probably except general "How to contribute" guidelines), for now at least. At least introductory articles would be great on the site, but scope is an issue.
- All the individual plugin pages.
- Some governance-related pages (e.g. the meeting agenda, approved trademark usage) as needed.
- All pages that are linked from the software (and that's quite a list!) will at least remain as stubs, pointing somewhere real.

There's a bunch of other content, but much of that can probably be binned. We'll need to do some gardening (the thing you do with an axe) to remove all that stuff. The move away from the wiki for most of this is probably a good time. For that we'll need to convince Tyler that e.g. stub wiki pages about events years ago that may not even have occurred should be removed. I doubt anyone still cares about who had booth duty at JavaOne 2009, and if they do, it's time they create a copy of that wiki page.