<h1 id="updating-content">Updating Content<a aria-hidden="true" class="anchor-heading icon-link" href="#updating-content"></a></h1>
<p>When updating content in the dendron workspace, policy is different if you are updating a public or private vault</p>
<h2 id="updating-a-private-vault">Updating a private vault<a aria-hidden="true" class="anchor-heading icon-link" href="#updating-a-private-vault"></a></h2>
<p>The policy of updating a private vault is straightforward - make any edits and then run <a href="/notes/k3vz9kfqfhbr9gn23958vaz#workspace-sync">Workspace Sync</a>. </p>
<p>If you are creating or updating a SOP, run a sync before and after you change the sop and post the change as an update in <a href="/notes/5Jgi3mnbKHzTBNW4nVzJb">Daily Asyncs</a></p>
<h2 id="updating-dendron-site">Updating dendron-site<a aria-hidden="true" class="anchor-heading icon-link" href="#updating-dendron-site"></a></h2>
<p>When you are updating content from dendron-site, make a pull request against the <code>dev</code> branch for any changes.
Changes from <code>dev</code> are synced every tuesday and friday back with the <code>main</code> branch.</p>
<h2 id="updating-any-other-public-vault">Updating any other public vault<a aria-hidden="true" class="anchor-heading icon-link" href="#updating-any-other-public-vault"></a></h2>
<p>When updating any other public vault that is not <code>dendron-site</code>, changes can be submitted as a pull request directly against the <code>master</code> branch</p>
<h2 id="reference">Reference<a aria-hidden="true" class="anchor-heading icon-link" href="#reference"></a></h2>
<ul>
<li><a href="/notes/0asp7bgmz4vy0hfs1s3yo6o">All Vaults</a></li>
</ul>
<p><sup id="fnref-public"><a href="#fn-public" class="footnote-ref">public</a></sup> <a href="/notes/0asp7bgmz4vy0hfs1s3yo6o#public-vaults">Public Vaults</a></p>
<hr>
<strong>Backlinks</strong>
<ul>
<li><a href="/notes/mylqjwysyy8jwqiaicp89r9">Team Basics</a></li>
</ul>

Updating Content

dendron.handbook


Welcome to the Dendron handbook. This handbook is heavily inspired by the [gitlab handbook](https://about.gitlab.com/handbook). 

It documents everything we stand for and everything we are working towards. It is a living document, a work in progress that will change and grow as we do.
