diff --git a/dev/dev-notes/images/clipboard-674159866.png b/dev/dev-notes/images/clipboard-674159866.png
new file mode 100644
index 00000000..27572596
Binary files /dev/null and b/dev/dev-notes/images/clipboard-674159866.png differ
diff --git a/dev/dev-notes/index.html b/dev/dev-notes/index.html
index d57111d3..5ddfcfe0 100644
--- a/dev/dev-notes/index.html
+++ b/dev/dev-notes/index.html
@@ -202,12 +202,13 @@ <h1 class="title">BMM Developer Notes</h1>
 <section id="overview" class="level1 unnumbered">
 <h1 class="unnumbered">Overview</h1>
 <p>This article aims to help developers contribute new models to bmm. It is a work in progress and will be updated as the package evolves. It explains how to set-up your system for package development, the structure of the package, and the workflow for contributing new models to the package.</p>
-<p>We follow a github flow workflow. The repository contains two main branches:</p>
+<p>We follow a <a href="https://jeffkreeftmeijer.com/git-flow/">github flow workflow</a>. The repository contains two main branches:</p>
 <ul>
 <li><p>Master (contains the latest released stable version of the <code>bmm</code> package</p></li>
 <li><p>Develop (contains the latest stable development branch</p></li>
 </ul>
 <p>All new feature development should occur on an independent branch from Develop. If you want to contribute a new model to the <code>bmm</code> package, you need to fork the repository, create a new branch for your model, extensively test the model, and eventually submit a pull request for your changes to be merged into the Develop branch of the main repository. Your changes will be reviewed by someone from the core team. Once your changes are merged into the Develop branch, they will be included in the next release of the package.</p>
+<p><img src="images/clipboard-674159866.png" class="img-fluid"></p>
 
 
 </section>