<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 14, 2016 at 2:46 PM, Thomas Heute <span dir="ltr"><<a href="mailto:theute@redhat.com" target="_blank">theute@redhat.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"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Tue, Jun 14, 2016 at 1:24 PM, Alissa Bonas <span dir="ltr"><<a href="mailto:abonas@redhat.com" target="_blank">abonas@redhat.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"><div>1. I would put REST api as a separate section, and also not in the same hierarchy/section as client libraries, because REST is part of the project, and clients consume it. <br></div></div></blockquote><div><br></div></span><div>I'm not sure, from a developer perspective it doesn't really matter if REST is part of the project (except that you have nothing else to download/use), but it should be clear what options, as a developer, you have.</div><div>One has the choice between Ruby, Python, Go or plain REST.</div><div><br></div><div>At least that was my way of thinking.</div><span class=""><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><div>2. Having sections named "clients" and "client libraries" can be confusing. </div></div></blockquote><div><br></div></span><div>Agreed.</div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Perhaps "integrations" or "applications that consume hawkular" is better for "clients"?<br></div></div></blockquote><div><br></div></span><div>I thought of "consumers" for a short name. As we have "feeds" that feed data and "consumers" that consumed and display or do something with the data. Still not convinced about that name though....</div></div></div></div></blockquote><div><br></div><div>consumers sounds good.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><div>3. Is there a section dedicated to community events (meetups/conferences/hackaton/summit, etc.) where there are talks about the project? Didn't see it in the diagram.<br></div></div></blockquote><div><br></div></span><div>Good point.</div><div>We should probably splash them on the front page + blog.</div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><div>4. Overview can link to quick start imo<br></div></div></blockquote><div><br></div></span><div>Not sure what you mean, after one read the overview he should definitely be invited to get started.</div></div></div></div></blockquote><div><br></div><div>my point was that the navigation should be as simple and efficient as possible. so if a user reads the overview page, there's no need to go<br></div><div>to the homepage again in order to go to "get started", but rather navigate directly/have an inviting link from overview to get started.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><div>5. What should be the difference between quick start and the download sections? <br></div></div></blockquote><div><br></div></span><div>Quick start explains how to install the quickest way and get something out of the product.</div><div><br>The download section allows to find links of latest and previous releases.</div></div></div></div></blockquote><div><br></div><div>like above, I would also link between quick start and download pages so the user will get a convenient flow of "here's how to" and "here's where you can download from"<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><div>6. Ways to contact community? I saw only social links in the footer, but what about mailing list/irc,etc.?</div></div></blockquote><div><br></div></span><div>That would be in Community>Connect</div><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div> </div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div>p.s. I wrote an article couple of years ago on usability of community websites, maybe some ideas from there would be helpful as well<br><a href="https://opensource.com/business/14/8/open-source-project-front-door" target="_blank">https://opensource.com/business/14/8/open-source-project-front-door</a></div></blockquote><div><br></div><div><br></div></span><div>I'll have a look, thanks !</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Thomas</div></font></span><div><div class="h5"><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br></div><div class="gmail_extra">thanks,<br></div><div class="gmail_extra">Alissa<br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Tue, Jun 14, 2016 at 1:25 PM, Thomas Heute <span dir="ltr"><<a href="mailto:theute@redhat.com" target="_blank">theute@redhat.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">With the recent repackaging effort + the ManageIQ UI, we need to rethink <a href="http://hawkular.org" target="_blank">hawkular.org</a>.<div><br></div><div>It's tricky to keep it simple, what to download, for what usecase... And at the moment it's getting outdated.</div><div><br></div><div>IMO, it should be trivial for end users to figure out:</div><div> - What to download</div><div> - where to download and how to install the server</div><div> - find/browse/download the various options to feed the server with data (WF agent, ptrans supported protocoles, ...)</div><div> - find/browse/download options to use/read the data: (ManageIQ, Grafana...)</div><div><br></div><div>and for the developers</div><div> - find/browse/download the client libraries (Ruby, Python...)</div><div> - Find client libraries documentation</div><div> - Find examples...</div><div><br></div><div>We should probably not separate/fork Hawkular Services from Hawkular "community" too much, beside the installation procedure and few things that we would mention as only available in the "larger" package. I use the term "Hawkular Server" in the mind map for the 2 "flavors".</div><div><br></div><div>Please propose improvements to the draft attached that represents the website structure. (A square is not necessarily a page, it may be a section of a page)</div><span><font color="#888888"><div><br></div><div>Thomas</div></font></span></div>
<br></div></div>_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org" target="_blank">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
<br></blockquote></div><br></div></div>
<br>_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org" target="_blank">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
<br></blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
<br></blockquote></div><br></div></div>