<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><div style="font-family: Helvetica; font-size: medium; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); -webkit-text-size-adjust: auto; ">--<br>sent via mobile</div></div><div><br>On 15 Mar 2013, at 05:54, Daniel Bünzli <<a href="mailto:daniel.buenzli@erratique.ch">daniel.buenzli@erratique.ch</a>> wrote:<br><br></div><blockquote type="cite"><div><span>Hello,</span><br><span></span><br><blockquote type="cite"><span>On wider monitors, we'd likely add more whitespace either side so as to avoid stretching the content too far.</span><br></blockquote><span></span><br><span>W.r.t. page layout stretchability but on the narrower side, a good test to have in mind is to check if on a laptop you can have an 80-columns text editor and the documentation side by side without needing horizontal scrolling.</span><br></div></blockquote><div><br></div><div>Hadn't thought of that so I'll bear it in mind. However, it may still depend on the resolution of the laptop in question (eg I have a 'retina' MacBook which has more horizontal space than my old laptop). </div><div><br></div><br><blockquote type="cite"><div><span></span><span>Regarding the Modules tab I'm not sure I understood you well so it may already be the idea. But if the package has a single module it would be nice if it shows directly the documentation of that module to save one useless click. </span><br></div></blockquote><div><br></div><div>Yes, that's the plan. I did mention it but probably wasn't clear enough.</div><div><br></div><br><blockquote type="cite"><div><span></span><span>Also, it's more a comment for opam, but it would be nice if the documentation system could do the same locally with the same experience but showing you only the documentation of your installed packages (with a landing page that lists the packages and their respective modules for direct access).</span><br></div></blockquote><div><br></div><div>Yes, this is also something we want :) It's not just an opam thing as it involves Leo's upcoming work on documentation, as well as using packages like cow, opam2web, weberizer etc. Doing this locally, would enable the creation of properly cross-referenced docs for a particular user's environment. </div><div><br></div><div>Best wishes,</div><div>Amir</div><br><blockquote type="cite"><div><span></span></div></blockquote></body></html>