<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; " class=""><div><div class="">On 22 Feb 2018, at 11:32, Umesh Singla <<a href="mailto:umeshksingla@macports.org">umeshksingla@macports.org</a>> wrote:</div><blockquote type="cite"><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote">On Thu, Feb 22, 2018 at 12:26 AM, db <span dir="ltr" class=""><<a href="mailto:iamsudo@gmail.com" target="_blank" class="">iamsudo@gmail.com</a>></span> wrote:<br class=""><blockquote style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; " class="gmail_quote">On 21 Feb 2018, at 17:33, Mojca Miklavec <<a href="mailto:mojca@macports.org" target="_blank" class="">mojca@macports.org</a>> wrote:<br class="">
> - New website!!!!!<br class="">Homebrew/Linuxbrew's are good examples to get up and running quickly, and still have updated technical documentation.</blockquote><div class="">or ReadTheDocs (rst files, easy to manage the directory structure, can use templates)? Website is more-or-less documentation only in our case.</div></div></div></div>
</blockquote><br class=""></div><div>I meant, there's no overview. And some topics discussed in the list never make it to the guide.</div>
</body></html>