On 14 Jun 2016, at 22:32, Stefan Negrea wrote:

> I do not see the idea proposed yet, but why not structure the website
> around major projects? We have Hawkular community, Hawkular Services,
> Hawkular Metrics, and APM. Projects like Inventory or the clients
> would
> fall under Hawkular Services umbrella. So rather than designing a
> generic
> structure with everything make individual sub-sites and then apply the
> structure you proposed.

I think even if/when Hawkular-metrics gets its own section (which is
well
warranted as we create a metrics distribution), we need to make sure
that
it blends well into the Hawkular-services documentation. We can for sure
use some include tags to accomplish this. I think Hawkular-services
should now be the main/default focus area of hawkular.org (at least
from the non-APM side)

Likewise we should also be careful with external documentation like
gitbook. I have seen some pretty good and comprehensive documentation
there, so the idea behind is good. An issue is certainly that it is yet
another
place for stuff and dilutes the content on hawkular.org.
Perhaps there is a way to include/iframe it, the experience could
potentially
be good, as some of the current (long) pages have issues with the
navigation
via the page-tree in the left part.
On the other hand (and I think this was mentioned already) there may be
a way to include content from hawkular.org into the gitbook, so that it
exists in both forms, but from one source (-> consistency)

_______________________________________________
hawkular-dev mailing list
hawkular-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev