Uploaded image for project: 'Jenkins Website'
  1. Jenkins Website
  2. WEBSITE-39

Define the website migration path from current to "2.0"



    • Similar Issues:


      Kohsuke Kawaguchi and I have had a bit of back and forth on how to move forward with the "new and improved" version of jenkins-ci.org

      I suggested teasing apart things into two tracks in IRC, one for the new site and one for the new domain (jenkins.io). Kohsuke's concerns are around making it such that folks like Tracy Kennedy and Patrick Wolf can help fill out "2.0" content for the new site without adversely affecting or being impeded by the 1.0 version of the site.

      One of the things we've also discussed on IRC is taking the same corpus of content and generating the 1.0 version of the site (blog, home page) and generating that plus new types of content for the 2.0 version of the site (blog, home page, events, solution pages) while maintaining the same raw materials underneath.

      What is really needed here is a migration path to be defined such that we can talk around it without operating on so many assumptions right now


          Issue Links


            rtyler R. Tyler Croy created issue -
            rtyler R. Tyler Croy made changes -
            Field Original Value New Value
            Labels community-bee
            rtyler R. Tyler Croy made changes -
            Status To Do [ 10003 ] In Progress [ 3 ]
            rtyler R. Tyler Croy made changes -
            Remote Link This issue links to "pull request #3 (Web Link)" [ 13536 ]
            rtyler R. Tyler Croy made changes -
            Flagged Impediment [ 10003 ]
            rtyler R. Tyler Croy made changes -
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Done [ 10004 ]


              rtyler R. Tyler Croy
              rtyler R. Tyler Croy
              0 Vote for this issue
              2 Start watching this issue