<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Responding to my own email...<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 11, 2015, at 6:40 AM, Dirk Hohndel <<a href="mailto:dirk@hohndel.org" class="">dirk@hohndel.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Ahh,<div class=""><br class=""></div><div class="">Clearly it's much easier to get feedback on the website than to get people to test :-)</div><div class=""><br class=""></div><div class="">Is this an example of the bike shedding phenomenon? :-)</div></div></div></blockquote><div><br class=""></div>First things first. Me and my big mouth.</div><div>What I should have said was "Thank you to all of you who provided feedback. Much appreciated. I need as many people as possible to look at this and help me iron out the kinks before the site goes live".</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">I'll try to answer to all of the comments here...</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Oct 10, 2015, at 11:20 PM, Rick Walsh <<a href="mailto:rickmwalsh@gmail.com" class="">rickmwalsh@gmail.com</a>> wrote:</div><div class="">I've had a quick look on my phone. Using Chrome on my Galaxy S6. I like the new layout, including that it draws attention to cool features at the top. A few points.<br class=""><p dir="ltr" class="">
-Main headings on each page are inconsistent size. Landing page is small. Downloads is large. FAQ is small, etc.<br class=""></p></div></blockquote><div class=""><br class=""></div><div class="">Yes, I noticed that, too. The pages are two different ways - Landing and FAQ use an additional toolset that the other pages don't use. I'll take a look at how to make this consistent.</div></div></div></div></div></blockquote><div><br class=""></div><div>I think I have now fixed most of them - I know there are a couple left that are a different size and black (see next item). If you stumble across them please point them out here so I don't end up missing any.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class=""><p dir="ltr" class="">
-I think the heading colour would look better as "Subsurface blue", rather than black.<br class=""></p></div></blockquote><div class=""><br class=""></div><div class="">Good point</div></div></div></div></div></blockquote><div><br class=""></div><div>This should be fixed for most, see previous point.</div><blockquote type="cite" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class=""><p dir="ltr" class="">-On the landing page is it better to elaborate on the features in case the reader doesn't wait to scroll through them at the top? Cloud storage, platforms and the planner aren't mentioned except in the bit that flashes through at the top.</p></div></blockquote><div class=""><br class=""></div>I tried both ways and it felt really redundant. So I'm not sure what to do here. I'll ask a friend of mine who has helped me with rewording this page (and as working on writing a better announcement). She tends to know what works with audiences :-)<br class=""></div><div class=""><br class=""></div></div></div></blockquote><div><br class=""></div>What do people here think. I just added a German translation for the landing page and did that slightly differently - I'm not sure it's better, though.</div><div><br class=""><blockquote type="cite" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class=""><div class="">On Oct 10, 2015, at 11:22 PM, Salvador Cuñat <<a href="mailto:salvador.cunat@gmail.com" class="">salvador.cunat@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Good morning.<br class=""><div class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">2015-10-11 8:01 GMT+02:00 Dirk Hohndel <span dir="ltr" class=""><<a href="mailto:dirk@hohndel.org" target="_blank" class="">dirk@hohndel.org</a>></span>:<br class=""><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div class="" style="word-wrap: break-word;">After about 20 hours of editing and copying and modifying I have a mockup of the new website ready.<div class=""><br class=""></div><div class="">Please go to <a href="http://ssrftest.subsurface-divelog.org/" target="_blank" class="">http://ssrftest.subsurface-divelog.org</a> and let me know what you think.</div><div class=""><br class=""></div><br class=""></div></blockquote></div>It looks rather bizarre in my browser };-)<br class=""></div></div></div></div></div></div></blockquote><br class=""></div><div class=""><br class=""></div><div class="">Yes, I kinda mentioned that but should have said it more strongly...</div><div class="">a) the site automatically follows the language settings of your browser - so if you usually browse the web in Spanish (or German) it will show you that translation (which hopefully means less need for the language switching)</div><div class="">b) while I spent a ton of time migrating a good chunk of the translations, the landing page and the dive ramblings page and most of the posts are broken with respect to translations</div><div class="">But many other pages should do the right thing, e.g. the FAQ or the Downloads page (except that I believe I have some changed to the non-existend 4.5 and some are the old text). Which reminds me, I noticed that the translations are WAY out of sync for some of the pages. As everything else we do, this is all a matter of the right people having enough time. Where the "right people" way to often ends up being "me".</div></div></blockquote><div><br class=""></div>So I think with the exception of the landing page and many of the older news items all the translations should now be cleaned up.</div><div>I'll send a separate email about web site translations in a moment.</div><div><br class=""><blockquote type="cite" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><blockquote type="cite" class=""><div class="WordSection1" style="page: WordSection1;"><div class=""><div class="">On Oct 10, 2015, at 11:34 PM, Steve <<a href="mailto:stevewilliams@internode.on.net" class="">stevewilliams@internode.on.net</a>> wrote:</div><div class=""><div class="WordSection1" style="page: WordSection1;"><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 12pt;" class=""> </span></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span class="" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Looks good on my laptop.<o:p class=""></o:p></span></div><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span class="" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">I would change the different languages bar to the top rather than at the bottom which you need to scroll down before you see it from the homepage.<o:p class=""></o:p></span></div></div></div></div></div></div></blockquote><br class=""></div><div class=""><br class=""></div><div class="">Well, it's at the bottom on purpose because as I mentioned above, most people should never need it and having it on the top means it steals important vertical space when you first open the page. So I think I'll leave it on the bottom.</div></div></blockquote><div><br class=""></div>I left it at the bottom but moved it up above the footer with the social media icons. It now gets correctly resized / wrapped if the window is too narrow.</div><div><br class=""></div><div><blockquote type="cite" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><blockquote type="cite" class=""><div class="">On Oct 11, 2015, at 1:02 AM, Gaetan Bisson <<a href="mailto:bisson@archlinux.org" class="">bisson@archlinux.org</a>> wrote:</div><div class=""><br class="">The only thing I noted is that we have two redundant social media<br class="">banners (one in "top-header" and the other in "footer-bottom"); perhaps<br class="">the top one could be removed so page contents get bumped up?<br class=""></div></blockquote></div><div class=""><div class="WordSection1" style="page: WordSection1;"><div class=""><div class=""><div class="WordSection1" style="page: WordSection1;"><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span class="" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><br class=""></span></div><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span class="" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Oh, good catch - I thought I had disabled the top one (see comments above about not wasting vertical space at the top). Yes, I just want the ones in the footer.</span></div></div></div></div></div></div></div></div></blockquote><div><br class=""></div>Fixed.</div><div><br class=""><blockquote type="cite" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class="WordSection1" style="page: WordSection1;"><div class=""><div class=""><div class="WordSection1" style="page: WordSection1;"><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span class="" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><blockquote type="cite" style="font-family: Helvetica; font-size: 12px;" class=""><div class="">On Oct 11, 2015, at 2:18 AM, Joakim Bygdell <<a href="mailto:j.bygdell@gmail.com" class="">j.bygdell@gmail.com</a>> wrote:</div><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class=""><blockquote type="cite" class=""><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class=""><br class=""></div></div></div></blockquote>Adding a few thing to what the others have said.</div><div class=""><br class=""></div><div class="">The lefthand navigation frame goes all the way to the bottom of the page and thus covers the language row with the result that only “sh” from English is visible.</div><div class="">It is really apparent on the bugtracker page.</div></div></div></blockquote><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span class="" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><br class=""></span></div>Oh, oops - that one is supposed to "flow", i.e. to wrap around and become multiple lines. I need to figure out why it doesn't do that</span></div></div></div></div></div></div></div></div></blockquote><div><br class=""></div>Fixed.</div><div><br class=""><blockquote type="cite" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class="WordSection1" style="page: WordSection1;"><div class=""><div class=""><div class="WordSection1" style="page: WordSection1;"><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span class="" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><blockquote type="cite" style="font-family: Helvetica; font-size: 12px;" class=""><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="">I suggest that the command snippets get placed in a scrollable frame, </div><div class="">otherwise the page gets disproportionally wide when viewed on a phone</div></div></div></blockquote><br class=""></span></div><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span class="" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Also a very good idea. I need to figure out how to do that - can't be that hard since I see it on many pages.</span></div></div></div></div></div></div></div></div></blockquote><div><br class=""></div>Still on my todo list.</div><div><br class=""><blockquote type="cite" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class="WordSection1" style="page: WordSection1;"><div class=""><div class=""><div class="WordSection1" style="page: WordSection1;"><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span class="" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">OK, I think that responds to all of your comments.</span></div><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span class="" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><br class=""></span></div><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span class="" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Thanks everyone for trying things - I realize it's still a little rough but I'll admit that I'm quite excited about it. Needless to say I think this is a massive improvement compared to what we had before - which looked terrible on mobile browsers and was way too cluttered. We had a couple people look at the site while in Bonaire and the responses were generally quite negative. The reality is that a lot of people consume the web on iPads and not on desktops and that changes some of the underlying ideas of what you can show and how you should show it. Less visual clutter is the main goal here...</span></div></div></div></div></div></div></div></div></blockquote><br class=""></div><div>Now that most issues are addressed, please play with the new site some more. I'm sure there are more inconsistencies that need to be addressed.</div><div><br class=""></div><div>Separate email about translations coming up :-)</div><div><br class=""></div><div>/D</div><div><br class=""></div><br class=""></div></body></html>