<div dir="ltr"><div>Hi Olivier,</div><div><br></div><div>I was about creating a Javadoc landing page when I was working on the component Javadoc support.</div><div>But I have never got to it unfortunately.</div><div><br></div><div>So yes, currently the "official" way to get to Javadoc lists is to use GitHub.</div><div>Should be trivial to fix by updating <a href="https://jenkins.io/doc/developer/javadoc/">https://jenkins.io/doc/developer/javadoc/</a> or maybe by adding a custom header to all Javadoc outputs (like Jenkins Javadoc plugin does).</div><div><br></div><div>BR, Oleg</div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 16, 2018 at 2:55 PM, Olblak <span dir="ltr"><<a href="mailto:me@olblak.com" target="_blank">me@olblak.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hello,<br>
I recently updated <a href="https://javadoc.jenkins.io" rel="noreferrer" target="_blank">https://javadoc.jenkins.io</a> in order to<br>
<br>
1. Update it more frequently [INFRA-1600]<br>
2. Enable HTTPS support  [INFRA-1387]<br>
3. Move it to Azure [INFRA-1426]<br>
<br>
But I also found the UX quite inconvenient with hidden information depending how you arrive on that service.<br>
<br>
Scenario 1, you get there via <a href="https://jenkins.io/doc/developer/javadoc/" rel="noreferrer" target="_blank">https://jenkins.io/doc/<wbr>developer/javadoc/</a> and then it's kind of OK.<br>
Scenario 2, you get there via <a href="https://javadoc.jenkins.io" rel="noreferrer" target="_blank">https://javadoc.jenkins.io</a> and you have no way to know about <a href="https://javadoc.jenkins.io/component" rel="noreferrer" target="_blank">https://javadoc.jenkins.io/<wbr>component</a> or <a href="https://javadoc.jenkins.io/plugin" rel="noreferrer" target="_blank">https://javadoc.jenkins.io/<wbr>plugin</a>.<br>
<br>
Is there any other way to access the javadoc?<br>
<br>
Maybe I am the only one but instinctively I would follow scenario 2 and expect '<a href="http://jenkins.io/doc/developer/javadoc" rel="noreferrer" target="_blank">jenkins.io/doc/developer/<wbr>javadoc</a>' to be the same than '<a href="http://javadoc.jenkins.io" rel="noreferrer" target="_blank">javadoc.jenkins.io</a>'.<br>
I would also expect javadoc to be a standalone service, where everything is defined from <a href="https://github.com/jenkins-infra/javadoc" rel="noreferrer" target="_blank">https://github.com/jenkins-<wbr>infra/javadoc</a> without having to go on <a href="http://github.com/jenkins-infra/jenkins.io" rel="noreferrer" target="_blank">github.com/jenkins-infra/<wbr>jenkins.io</a>.<br>
<br>
What's your thought about this?<br>
______________________________<wbr>_________________<br>
Jenkins-infra mailing list<br>
<a href="mailto:Jenkins-infra@lists.jenkins-ci.org">Jenkins-infra@lists.jenkins-<wbr>ci.org</a><br>
<a href="http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra" rel="noreferrer" target="_blank">http://lists.jenkins-ci.org/<wbr>mailman/listinfo/jenkins-infra</a><br>
</blockquote></div><br></div>