<p>Good stuff with <a class="commit-link" href="https://github.com/bisq-network/bisq-docs/commit/72cabda997873f3b6e2a428c61bb5529ec4cb23d"><tt>72cabda</tt></a>, <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>. I've just had a quick glance now, but notice that the screenshots are all taken a quite high-res, making the details hard to see. Perhaps you could shrink the screen down, ideally to the default size of the window when it's first launched. If we standardize on doing it that way, then all our documentation will have consistent window dimensions. And things should always be visible enough at those dimensions anyway. i.e. it should be a design constraint that people don't <em>have</em> to stretch the Bisq window beyond its default dimensions just to see some feature of the UI.</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/bisq-docs/pull/45#issuecomment-386827065">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtqfgZw0F7G0fsUArvQ6IIBmyPCWcks5tvfUMgaJpZM4TxXG2">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtsBC4StUbkuoW8BBpTrbsxbOkr4eks5tvfUMgaJpZM4TxXG2.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/bisq-docs/pull/45#issuecomment-386827065"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request 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/bisq-docs","title":"bisq-network/bisq-docs","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/bisq-docs"}},"updates":{"snippets":[{"icon":"PERSON","message":"@cbeams in #45: Good stuff with 72cabda, @m52go. I've just had a quick glance now, but notice that the screenshots are all taken a quite high-res, making the details hard to see. Perhaps you could shrink the screen down, ideally to the default size of the window when it's first launched. If we standardize on doing it that way, then all our documentation will have consistent window dimensions. And things should always be visible enough at those dimensions anyway. i.e. it should be a design constraint that people don't _have_ to stretch the Bisq window beyond its default dimensions just to see some feature of the UI."}],"action":{"name":"View Pull Request","url":"https://github.com/bisq-network/bisq-docs/pull/45#issuecomment-386827065"}}}</script>