<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>2. Having sections named "clients" and "client libraries" can be confusing. Perhaps "integrations" or "applications that consume hawkular" is better for "clients"?<br></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>4. Overview can link to quick start imo<br></div><div>5. What should be the difference between quick start and the download sections? <br></div><div>6. Ways to contact community? I saw only social links in the footer, but what about mailing list/irc,etc.?<br><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">https://opensource.com/business/14/8/open-source-project-front-door</a><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">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><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><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 class="HOEnZb"><font color="#888888"><div><br></div><div>Thomas</div></font></span></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>