<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 14, 2016 at 2:12 PM, Gary Brown <span dir="ltr"><<a href="mailto:gbrown@redhat.com" target="_blank">gbrown@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Hi<br>
<br>
Currently only have one observation - under User Guide it has Hawkular Server and Hawkular Metrics - however I believe Metrics is part of Hawkular Server.<br></blockquote><div><br></div><div>is *also* part of Hawkular server, yes.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
So should the User Guide be broken down into functional areas, rather than be based on packaging, as I guess that its usage will be the same (mostly) whether standalone or packaged? And where differences occur, then the guide can highlight the differences?<br></blockquote><div><br></div><div>Yes that the dilemma. As a user I think I would prefer based on packaging as I want to have the documentation for what I am running, today there is a split per functional area (actually it's per "component"), it makes it harder to grasp what one can do and how, plus it's missing the link between the components, as how to use them together.<br></div><div><br></div><div><br></div><div>Thomas.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">If this change is appropriate, then it might be possible for some/all of the 'clients' to be described under the functionality area they are related to.<br></blockquote><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
Regards<br>
<span class=""><font color="#888888">Gary<br>
</font></span><div class=""><div class="h5"><br>
----- Original Message -----<br>
> With the recent repackaging effort + the ManageIQ UI, we need to rethink<br>
> <a href="http://hawkular.org" rel="noreferrer" target="_blank">hawkular.org</a> .<br>
><br>
> It's tricky to keep it simple, what to download, for what usecase... And at<br>
> the moment it's getting outdated.<br>
><br>
> IMO, it should be trivial for end users to figure out:<br>
> - What to download<br>
> - where to download and how to install the server<br>
> - find/browse/download the various options to feed the server with data (WF<br>
> agent, ptrans supported protocoles, ...)<br>
> - find/browse/download options to use/read the data: (ManageIQ, Grafana...)<br>
><br>
> and for the developers<br>
> - find/browse/download the client libraries (Ruby, Python...)<br>
> - Find client libraries documentation<br>
> - Find examples...<br>
><br>
> We should probably not separate/fork Hawkular Services from Hawkular<br>
> "community" too much, beside the installation procedure and few things that<br>
> we would mention as only available in the "larger" package. I use the term<br>
> "Hawkular Server" in the mind map for the 2 "flavors".<br>
><br>
> Please propose improvements to the draft attached that represents the website<br>
> structure. (A square is not necessarily a page, it may be a section of a<br>
> page)<br>
><br>
> Thomas<br>
><br>
</div></div><div class=""><div class="h5">> _______________________________________________<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>
_______________________________________________<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>
<br>
</div></div></blockquote></div><br></div></div>