James, what is the URL to the javadoc?
Yes, that should definitely be in jenkins-ci.org and it should be pretty 
front-n-center, I would think....




On Wednesday, October 7, 2015 at 4:51:15 AM UTC-7, James Nord wrote:
>
> One thing I just realize is that we have our documentation (javadocs) on a 
> separate website.
> Most sites these days just have a "documentation " section which will also 
> have an api section within the same site (and themed in an approriate 
> manner) such that you have a more cohesive view (and have something that 
> actually makes you want to come back to the site.
>
> We should also have separate javadocs for the latest LTS as well as 
> bleeding edge (you could make the case for keeping a certain number of 
> javadocs for prior LTS versions - you can still get Spring 2.0 javadocs 
> online even if it is not supported!)
>
> and (ot as the design goes) ssl-everywhere will be required as Google will 
> start ranking secure sites higher in the future.
>
> /James
>
> On Wednesday, October 7, 2015 at 12:02:02 AM UTC+1, Gus Reiber wrote:
>>
>> Hey all,
>>    So a related thread exists here 
>> <https://groups.google.com/forum/#!topic/jenkinsci-dev/EMbE3a4u8nA>, but 
>> I have a couple of bits I didn't want lost in a thread. They are:
>>
>>    - *We are hiring! *I am looking for a contract based web designer 
>>    with a nice portfolio to show to help author new site templates and do 
>> some 
>>    information architecture for Jenkins-ci.org. If you know someone, you can 
>>    reach me on Twitter @gusreiber, or email me 
>>    gusreiber(at-symb)cloudbees(dot-com) or find me on IRC, 
>>    freenode/#jenkins/gusreiber. You would be part of a fairly tight 3 person 
>>    team that would include myself, R Tyler Croy (whom you might know from 
>> such 
>>    places as this list) and yourself. Daniel Beck, and KK and the will of 
>> the 
>>    community will also be dropping their input along the way.
>>    
>>    - *We are discussing!* Even if you don't feel you have the time or 
>>    qualifications to join the team in exchange for money, we still want to 
>>    hear from you.
>>
>> With those two little action items out of the way, here is the gist of 
>> the discussion so far....
>>
>> Jenkins.org has a website (http://jenkins-ci.org/), but it isn't very 
>> good, (made evident in part by the fact that I am posting this message to 
>> you through this site instead of that one). It contains some documentation, 
>> a few blog articles, the Jenkins bits (most importantly), and the plugins 
>> directory (next most importantly). It is my belief that this site needs to 
>> have more of a social, 2-way communication aspect to it such that it can 
>> truly be the mecca to which Jenkins developers turn when they want their 
>> soules to be filled with the light of CI/CD knowledge. 
>>
>> To that ends, I have posted a proposal for what that might look here:
>>
>> https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+2.0+Website+vision+from+Gus+Reiber
>>
>> https://wiki.jenkins-ci.org/download/attachments/82673948/knowledge-site.pdf?version=1&modificationDate=1443574130000
>>
>> ...also, the plugin browsing experience really should be a lot better.
>> To that ends, here is a related video:
>> http://youtu.be/pMwsZRo5He8
>>
>> If you've got $.02....
>> ...drop-em.
>>
>>
>>

-- 
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/68949e0c-b142-4cfb-991c-871ae3bb403a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to