Hi, First of all +1 for the nice design and layout in your attached screenshot. I really like having the most important actions in the header bar.
If it's OK for you, I'll add a link back to this thread from https://wiki.jenkins-ci.org/display/JENKINS/UI+Enhancements which already lists a lot of ideas how the UI can be improved. Communication-wise, the best channel would be the #jenkins channel on the Freenode IRC network. Regards, Fred On Tuesday, March 20, 2012 9:25:23 AM UTC+1, Tom Bevers wrote: > > I already have forked jenkins and done some work in branch here: > https://github.com/tombevers/jenkins > My github Id: > https://github.com/tombevers<https://github.com/tombevers/jenkins> > > What's the best communication channel to communicate over the work and > backward > compatibility? > > On Tuesday, March 20, 2012 12:57:41 AM UTC+1, Kohsuke Kawaguchi wrote: >> >> On 03/18/2012 03:55 AM, Tom Bevers wrote: >> > Hi all, >> > >> > I really like Jenkins and use it daily, but one thing annoys me and >> that's >> > the GUI. It's not that user friendly and doesn't look good. >> > I hoped that would have been changed after the logo design contest as >> > www.jenkins-ci.org has gotten a new design aswel as the bug tracker. >> > >> > I want to contribute so we can make the GUI better and faster, and I >> have >> > some proposal: >> > >> > - Use Twitter Bootstrap< >> http://twitter.github.com/bootstrap/index.html> and >> > change the colors a bit to match the Jenkins colors >> > - Clean up current HTML >> > - Remove all inline styling (Include CSS in the head) >> > - Remove all inline javascript (Include at the bottom) >> > - Create sprite images wich results in less http calls >> > >> > I already tried to use the twitter bootstrap wich results directly in a >> > better looking Jenkins GUI (see the attachment). >> >> Thanks. Would you be interested in creating a branch and doing the work >> there? It's great that you are interested in working on it, and I think >> there are things I can help in ensuring backward compatibility, etc. >> >> I'm also trying to decompose monolithic style.css and >> hudson-behaviour.js and co-locate them via tag files so that we can see >> related code more quickly, which I think is relevant to this effort as >> well. >> >> On top of that, there are other committors like Ohtake-san and Domi, who >> I suspect have some opinions about these things! >> >> Let me know your GitHub ID so that we can set things up. >> >> -- >> Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ >> Try Nectar, our professional version of Jenkins >> >>
