<div dir="ltr">I mostly have concerns about having docs spread over multiple solutions. But if the plan is to move all to gitbook, it should be ok.<div><br></div><div>Also we should still use AsciiDoc (I see that gitbook supports AscissDoc and Markdown) </div><div><br><div>Thomas</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 6, 2016 at 9:27 AM, 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>
Wondering if gitbooks was ever considered for the documentation? Seems ideal as we can version each book with the component(s) it relates to, and users can download a pdf version for use offline.<br>
<br>
Was thinking about experimenting with it for the updated APM docs?<br>
<br>
Any objections?<br>
<br>
Regards<br>
Gary<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>
</blockquote></div><br></div>