<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 15, 2016 at 12:01 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi<br>
<br>
<a href="http://pasteboard.co/1HmIxzsJ.png" rel="noreferrer" target="_blank">http://pasteboard.co/1HmIxzsJ.png</a><br>
<br>
Tried using an iframe - problems are:<br>
<br>
1) Border around iframe - not sure if this can be reduced/removed<br>
<br>
2) When left hand menu showing, it is not possible to add comments (i.e. no + sign appears)<br>
<br>
3) When menu hidden, plus sign shows, but asks to sign in to comment - when link selected the iframe content goes blank<br>
<br>
So not sure iframe is a workable solution.<br>
<br>
Will see what customisations can be made to the gitbook itself to look more integrated - however wondering whether we should do much customisation, as I think users know they are navigating from a website to documentation, so would not be concerned with a different look and feel - as long as a consistent approach was used for all documentation.<br></blockquote><div><br></div><div>Unless they arrive on the documentation from a Google search ;)</div><div><br></div><div>Thomas</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="im HOEnZb"><br>
Regards<br>
Gary<br>
<br>
----- Original Message -----<br>
><br>
><br>
</span><div class="HOEnZb"><div class="h5">> On Wed, Jun 15, 2016 at 10:17 AM, Heiko W.Rupp < <a href="mailto:hrupp@redhat.com">hrupp@redhat.com</a> > wrote:<br>
><br>
><br>
> On 14 Jun 2016, at 22:32, Stefan Negrea wrote:<br>
><br>
> > I do not see the idea proposed yet, but why not structure the website<br>
> > around major projects? We have Hawkular community, Hawkular Services,<br>
> > Hawkular Metrics, and APM. Projects like Inventory or the clients<br>
> > would<br>
> > fall under Hawkular Services umbrella. So rather than designing a<br>
> > generic<br>
> > structure with everything make individual sub-sites and then apply the<br>
> > structure you proposed.<br>
><br>
> I think even if/when Hawkular-metrics gets its own section (which is<br>
> well<br>
> warranted as we create a metrics distribution), we need to make sure<br>
> that<br>
> it blends well into the Hawkular-services documentation. We can for sure<br>
> use some include tags to accomplish this. I think Hawkular-services<br>
> should now be the main/default focus area of <a href="http://hawkular.org" rel="noreferrer" target="_blank">hawkular.org</a> (at least<br>
> from the non-APM side)<br>
><br>
> +1<br>
><br>
><br>
><br>
> Likewise we should also be careful with external documentation like<br>
> gitbook. I have seen some pretty good and comprehensive documentation<br>
> there, so the idea behind is good. An issue is certainly that it is yet<br>
> another<br>
> place for stuff and dilutes the content on <a href="http://hawkular.org" rel="noreferrer" target="_blank">hawkular.org</a> .<br>
> Perhaps there is a way to include/iframe it, the experience could<br>
> potentially<br>
> be good, as some of the current (long) pages have issues with the<br>
> navigation<br>
> via the page-tree in the left part.<br>
> On the other hand (and I think this was mentioned already) there may be<br>
> a way to include content from <a href="http://hawkular.org" rel="noreferrer" target="_blank">hawkular.org</a> into the gitbook, so that it<br>
> exists in both forms, but from one source (-> consistency)<br>
><br>
> Agreed.<br>
> Gary could you look into the options to "blend" <a href="http://gitbook.io" rel="noreferrer" target="_blank">gitbook.io</a> content better<br>
> into <a href="http://hawkular.org" rel="noreferrer" target="_blank">hawkular.org</a> ?<br>
><br>
> Here is the reference point:<br>
> <a href="http://www.hawkular.org/docs/components/btm/index.html" rel="noreferrer" target="_blank">http://www.hawkular.org/docs/components/btm/index.html</a><br>
> Maybe iFraming <a href="https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/" rel="noreferrer" target="_blank">https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/</a><br>
> would work...<br>
> Maybe using a custom theme that adds our <a href="http://hawkular.org" rel="noreferrer" target="_blank">hawkular.org</a> header/footer in<br>
> <a href="http://gitbook.io" rel="noreferrer" target="_blank">gitbook.io</a> would work (I didn't see how to apply a theme to all books<br>
> though)...<br>
><br>
> I gave you admin rights if you need to poke around, but I didn't see anything<br>
> there that would help us...<br>
><br>
> Thomas<br>
><br>
><br>
><br>
><br>
><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>
><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>
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>