<h2>2018.04 report</h2>
<p>Big changes to docs this month!</p>
<ul>
<li><a class="user-mention" data-hovercard-user-id="301810" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/cbeams">@cbeams</a> created new <a href="https://docs.bisq.network" rel="nofollow">docs.bisq.network</a> site and published existing documentation there
<ul>
<li><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="313867000" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq-docs/issues/36" href="https://github.com/bisq-network/bisq-docs/pull/36">bisq-network/bisq-docs#36</a></li>
</ul>
</li>
<li><a class="user-mention" data-hovercard-user-id="301810" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/cbeams">@cbeams</a> produced <a href="https://docs.bisq.network/intro.html" rel="nofollow">Intro to Bisq</a> doc</li>
<li><a class="user-mention" data-hovercard-user-id="301810" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/cbeams">@cbeams</a> produced <a href="https://docs.bisq.network/contributor-checklist.html" rel="nofollow">New Contributor Checklist</a> doc
<ul>
<li><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="315196698" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq-docs/issues/39" href="https://github.com/bisq-network/bisq-docs/pull/39">bisq-network/bisq-docs#39</a></li>
</ul>
</li>
<li><a class="user-mention" data-hovercard-user-id="301810" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/cbeams">@cbeams</a> produced <a href="https://docs.bisq.network/proposals.html" rel="nofollow">Proposals</a> doc
<ul>
<li><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="316789845" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq-docs/issues/40" href="https://github.com/bisq-network/bisq-docs/pull/40">bisq-network/bisq-docs#40</a></li>
</ul>
</li>
</ul>
<p>These changes were promoted via Twitter to good effect.</p>
<p>Also, <a class="user-mention" data-hovercard-user-id="735155" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/m52go">@m52go</a> has gotten involved, and is in progress producting a Getting Started with Bisq document at <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="314795018" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq-docs/issues/37" href="https://github.com/bisq-network/bisq-docs/issues/37">bisq-network/bisq-docs#37</a>.</p>
<p>In general, all <a class="team-mention js-team-mention" data-error-text="Failed to load team members" data-id="2562320" data-permission-text="Team members are private" data-url="/orgs/bisq-network/teams/contributors/members" href="https://github.com/orgs/bisq-network/teams/contributors">@bisq-network/contributors</a> are encouraged to get familiar with the new docs site, and to begin thinking about it as <em>the</em> place to document all the most important things about Bisq.</p>
<p>When we talk about what it means to <a href="https://github.com/bisq-network/proposals/issues/19">deliver</a> a contribution, we should always be asking ourselves the question, what needs to change or get added to the documentation such that users can discover and understand my contribution?</p>
<p>The docs site is primitive today. You can think of it as something like "a wiki that wants to become a full-fledged manual". For right now, everything is flat. If there is something you want or need to document, come chat about it in <code>#bisq-docs</code>, and then put together a pull request for it, just like any other under.</p>
<p>From a visual design perspective, the new docs site will be one of the things we want to get aligned with the new design vision coming together with <a class="user-mention" data-hovercard-user-id="807505" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/pedromvpg">@pedromvpg</a>, <a class="user-mention" data-hovercard-user-id="5376199" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/diogorsergio">@diogorsergio</a> and others. This should be relatively low-hanging fruit, is its' mostly about adapting the existing default Asciidoctor CSS and fonts to align with the new design. This is something I've helped do in previous teams and I can point to that work for a reference point on how to do it.</p>
<p>Questions and ideas welcome about this new infrastructure. Let's chat in <code>#bisq-docs</code> in slack.</p>
<p>/cc <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="319495705" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/compensation/issues/68" href="https://github.com/bisq-network/compensation/issues/68">bisq-network/compensation#68</a></p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/roles/issues/29#issuecomment-386269299">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtpFEWyetwQx_fX4k5YbLyCPot0lcks5tuu7ogaJpZM4PL2jz">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtuw8CWB3NDsI2ozCBjHT0RWBa0oeks5tuu7ogaJpZM4PL2jz.gif" height="1" width="1" alt="" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/bisq-network/roles/issues/29#issuecomment-386269299"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bisq-network/roles","title":"bisq-network/roles","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/bisq-network/roles"}},"updates":{"snippets":[{"icon":"PERSON","message":"@cbeams in #29: ## 2018.04 report\r\n\r\nBig changes to docs this month!\r\n\r\n - @cbeams created new [docs.bisq.network](https://docs.bisq.network) site and published existing documentation there\r\n   - https://github.com/bisq-network/bisq-docs/pull/36\r\n - @cbeams produced [Intro to Bisq](https://docs.bisq.network/intro.html) doc\r\n - @cbeams produced [New Contributor Checklist](https://docs.bisq.network/contributor-checklist.html) doc\r\n   - https://github.com/bisq-network/bisq-docs/pull/39\r\n - @cbeams produced [Proposals](https://docs.bisq.network/proposals.html) doc\r\n   - https://github.com/bisq-network/bisq-docs/pull/40\r\n\r\nThese changes were promoted via Twitter to good effect.\r\n\r\nAlso, @m52go has gotten involved, and is in progress producting a Getting Started with Bisq document at https://github.com/bisq-network/bisq-docs/issues/37.\r\n\r\nIn general, all @bisq-network/contributors are encouraged to get familiar with the new docs site, and to begin thinking about it as *the* place to document all the most important things about Bisq.\r\n\r\nWhen we talk about what it means to [deliver](https://github.com/bisq-network/proposals/issues/19) a contribution, we should always be asking ourselves the question, what needs to change or get added to the documentation such that users can discover and understand my contribution?\r\n\r\nThe docs site is primitive today. You can think of it as something like \"a wiki that wants to become a full-fledged manual\". For right now, everything is flat. If there is something you want or need to document, come chat about it in `#bisq-docs`, and then put together a pull request for it, just like any other under.\r\n\r\nFrom a visual design perspective, the new docs site will be one of the things we want to get aligned with the new design vision coming together with @pedromvpg, @diogorsergio and others. This should be relatively low-hanging fruit, is its' mostly about adapting the existing default Asciidoctor CSS and fonts to align with the new design. This is something I've helped do in previous teams and I can point to that work for a reference point on how to do it.\r\n\r\nQuestions and ideas welcome about this new infrastructure. Let's chat in `#bisq-docs` in slack.\r\n\r\n/cc bisq-network/compensation#68"}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/roles/issues/29#issuecomment-386269299"}}}</script>