<div dir="ltr">I like the re-org a lot. <div><br></div><div>Splitting the content up: unless the demo servers grow a lot I don't know if we gain much by splitting those off. We've had times when we had a lot of demo servers but inevitably they've faded into the background. If we can reliably keep just a few up I'd rather keep their information with the downloads rather than have people click around more. </div>
<div><br></div><div>Splitting the server and staff client downloads off ... it's more attractive and something tells me folks will like that. If we could make each portals for those communities I'll probably gravitate in that direction as well and it seems like that's the road you're going down here. Was that your thought Grace?</div>
<div><br></div><div>Personally, I'm also a fan of linking staff clients in a series with the current one, I often hear from folks who have trouble finding the slightly older staff clients (e.g. 2.4.2 is the current release but they need the 2.4.1) and maybe some instructions for identifying which staff client they need. I know that sounds silly to some but by the time you're supporting part time IT contractors in rural regions of your consortium... Whether or not we did those particular things they are the kind of thing I can see us fleshing out with more space.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 15, 2013 at 8:58 AM, Grace Dunbar <span dir="ltr"><<a href="mailto:gdunbar@esilibrary.com" target="_blank">gdunbar@esilibrary.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div>I used the mockup software that we have here at Equinox for the mockups I did for the download page (attached). The first mockup is a re-org of what we have now. I spent a lot of time adding notes and trying to figure out how to make the page less busy. I also had a hard time figuring out who our audience was on that page. Is it librarians or developers/admins? It was really both and I think that leads to page confusion. The next 3 mockups are my proposal for reorganizing the downloads page by splitting things up.</div>
<div><br></div><div>Feedback is appreciated.</div><div>Cheers!</div><span class="HOEnZb"><font color="#888888"><div>Grace <br clear="all"><div><br></div>-- <br><div dir="ltr"><font size="1">Grace Dunbar, Vice President<br>
Equinox Software, Inc. - The Open Source Experts<br><a href="mailto:gdunbar@esilibrary.com" target="_blank">gdunbar@esilibrary.com</a></font>
<font size="1"> <br>
1-877-OPEN-ILS <a href="http://www.esilibrary.com" target="_blank">www.esilibrary.com</a></font>
<font size="1"> </font><br></div>
</div></font></span></div>
<br>_______________________________________________<br>
Evergreen-web-team mailing list<br>
<a href="mailto:Evergreen-web-team@list.evergreen-ils.org">Evergreen-web-team@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><br><div>Rogan Hamby, MLS, CCNP, MIA</div><div>Managers Headquarters Library and Reference Services, </div><div>York County Library System</div>
<div><br></div><div><span style="color:rgb(24,24,24);font-family:georgia,serif;font-size:14px;line-height:18px;background-color:rgb(255,255,255)">“You can never get a cup of tea large enough or a book long enough to suit me.” </span><br style="color:rgb(24,24,24);font-family:georgia,serif;font-size:14px;line-height:18px;background-color:rgb(255,255,255)">
<span style="color:rgb(24,24,24);font-family:georgia,serif;font-size:14px;line-height:18px;background-color:rgb(255,255,255)">― </span><a href="http://www.goodreads.com/author/show/1069006.C_S_Lewis" style="color:rgb(102,102,0);text-decoration:initial;font-family:georgia,serif;font-size:14px;line-height:18px;background-color:rgb(255,255,255)" target="_blank">C.S. Lewis</a></div>
</div>
</div>