[Hawkular-dev] Hawkular.org

[Alissa Bonas]

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.
2. Having sections named "clients" and "client libraries" can be confusing.
Perhaps "integrations" or "applications that consume hawkular" is better
for "clients"?
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.
4. Overview can link to quick start imo
5. What should be the difference between quick start and the download
sections?
6. Ways to contact community? I saw only social links in the footer, but
what about mailing list/irc,etc.?

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
https://opensource.com/business/14/8/open-source-project-front-door

thanks,
Alissa

On Tue, Jun 14, 2016 at 1:25 PM, Thomas Heute <theute at redhat.com> wrote:

> With the recent repackaging effort + the ManageIQ UI, we need to rethink
> hawkular.org.
>
> It's tricky to keep it simple, what to download, for what usecase... And
> at the moment it's getting outdated.
>
> IMO, it should be trivial for end users to figure out:
>   - What to download
>   - where to download and how to install the server
>   - find/browse/download the various options to feed the server with data
> (WF agent, ptrans supported protocoles, ...)
>   - find/browse/download options to use/read the data: (ManageIQ,
> Grafana...)
>
> and for the developers
>   - find/browse/download the client libraries (Ruby, Python...)
>   - Find client libraries documentation
>   - Find examples...
>
> 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".
>
> 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)
>
> Thomas
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/ae4602e3/attachment-0001.html