2.0 website: content track

[Kohsuke Kawaguchi]

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

And in particular, in this thread let's focus on identifying pillars.

In the original proposal that I made, which is captured very well in Daniel's wiki page, the key pillars of the website are:

• Channels for us devs to engage the user community. Most notably blog.
  
• Documentation for new users till they get up & running; feature highlights and curated getting started guide
• Plugins, though I classified this under "things to do in the future" category

Gus made a pitch that interaction among users should be the main pillar, which got a lot of push back. In the same pitch, he said downloads, plugins, and events are the other key pillars.

Bobby made a comment that he sees the extensibility part of the website a key pillar because it speaks to the principle & DNA of this community.

Hopefully I captured it correctly. Let's keep the discussion going here.

--

Kohsuke Kawaguchi

[Christopher Orr]

Wasn't sure which of the many email threads to hang this off of, but
here's something that may be of interest...

I noticed last week that the Kotlin documentation is pretty nicely
structured, and is also a static website backed by a Git repository
(with GitHub "edit" links on each page).

From whatever static site builder they use, they also build a
downloadable PDF version of the documentation (though I guess this is
more applicable to a programming language than it is to Jenkins).

https://kotlinlang.org/docs/reference/comparison-to-java.html
https://github.com/JetBrains/kotlin-web-site/blob/master/docs/reference/comparison-to-java.md

Regards,
Chris

On 10/10/15 01:01, Kohsuke Kawaguchi wrote:
> I'm dividing up the website conversation into several tracks. See this

> Wiki page <https://wiki.jenkins-ci.org/display/JENKINS/2.0+Website> for

> the overall structure.
>
> And in particular, in this thread let's focus on identifying pillars.
>
> In the original proposal that I made, which is captured very well in
> Daniel's wiki page

> <https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+2.0+Website+vision+from+Daniel+Beck>,

> the key pillars of the website are:
>

> * Channels for us devs to engage the user community. Most notably blog.
> * Documentation for new users till they get up & running; feature

> highlights and curated getting started guide

> * Plugins, though I classified this under "things to do in the future"

> category
>
> Gus made a pitch

> <https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+2.0+Website+vision+from+Gus+Reiber>

> that interaction among users should be the main pillar, which got a lot
> of push back. In the same pitch, he said downloads, plugins, and events
> are the other key pillars.
>
> Bobby made a comment that he sees the extensibility part of the website
> a key pillar because it speaks to the principle & DNA of this community.
>
>
> Hopefully I captured it correctly. Let's keep the discussion going here.
>
> --
> Kohsuke Kawaguchi
>

> --
> 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 jenkinsci-de...@googlegroups.com
> <mailto:jenkinsci-de...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4xNDWM9bM1PGpDAzp_oeoRB8BY5gYHX4A2yvwJXt05%3Dqg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4xNDWM9bM1PGpDAzp_oeoRB8BY5gYHX4A2yvwJXt05%3Dqg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

[R. Tyler Croy]

(replies inline)

On Mon, 02 Nov 2015, Christopher Orr wrote:

> Wasn't sure which of the many email threads to hang this off of, but
> here's something that may be of interest...
>
> I noticed last week that the Kotlin documentation is pretty nicely
> structured, and is also a static website backed by a Git repository
> (with GitHub "edit" links on each page).
>
> From whatever static site builder they use, they also build a
> downloadable PDF version of the documentation (though I guess this is
> more applicable to a programming language than it is to Jenkins).
>
> https://kotlinlang.org/docs/reference/comparison-to-java.html
> https://github.com/JetBrains/kotlin-web-site/blob/master/docs/reference/comparison-to-java.md

This is all totally viable and mostly done in my current awestruct-based
prototype under http://jenkins.lasagna.io (see "Improve this page")

Sourced via: https://github.com/rtyler/jenkins.io

- R. Tyler Croy

------------------------------------------------------
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>

% gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
------------------------------------------------------

[Kanstantsin Shautsou]

http://asciidoctor.org/news/2013/01/30/asciidoc-returns-to-github/