diff --git a/README.md b/README.md
index a1a345687376d727b03fbe7b22f9a065ad9ece70..eb169c49059195407eb5e5c4f851b2adf48bf70c 100644
--- a/README.md
+++ b/README.md
@@ -11,7 +11,7 @@ The design of bf-pd is based on the BOEUF conceptual framework which consists of
## Installing bf-pd
-- Download and install Pure Data for your operating system from https://puredata.info/downloads/pure-data
+- Download and install Pure Data (>=0.51) for your operating system from https://puredata.info/downloads/pure-data
- Install the **mrpeach** library using Deken (PD -> Help -> Find Externals)
- Install **bf-pd** using Deken
diff --git a/doc/boeuf.html b/doc/boeuf.html
new file mode 100644
index 0000000000000000000000000000000000000000..4396325c831f09d2c7c41dd56bb3ad7205cdce0f
--- /dev/null
+++ b/doc/boeuf.html
@@ -0,0 +1,33 @@
+<h1 id="the-boeuf-conceptual-framework">The BOEUF conceptual framework</h1>
+<p>BOEUF is a conceptual framework for modeling and building orchestras of digital musical instruments. It consists of a classification of <em>modes of collaboration</em>, and a set of <em>components</em> which can be used to enable these modes in digital instruments. We developed this classification after conducting interviews with digital musicians who work in ensembles, as well as literature review of work on digital ensembles and collaborative instruments. The word “boeuf” is french slang for a jam session.</p>
+<h2 id="modes-of-collaboration">Modes of Collaboration</h2>
+<p>The <em>modes of collaboration</em> are a categorization which is intended to describe all the ways that musicians collaborate and communicate during performance. This includes interactions which are <em>mediated</em> (i.e. take place through some technology) as well as <em>unmediated</em> interactions (which can occur through being in the same space together.)</p>
+<p>We propose that there are three modes of collaboration: <em>Cooperation</em>, <em>Communication</em>, and <em>Organisation</em></p>
+<h3 id="cooperation-modes">Cooperation Modes</h3>
+<p><em>Cooperation</em> describes the ways that musicians coordinate their actions with respect to their instruments. This cooperation can be:</p>
+<ul>
+<li><p><strong>Independent:</strong> Each musician controls their own instrument. For example, when two musicians begin to play their instruments at the same time this is <em>independent cooperation</em>. They are cooperating because they coordinated their musical gestures, but they act only on their own instrument.</p></li>
+<li><p><strong>Complementary:</strong> Multiple musicians can affect different aspects of the same musical process. For example, when one musician adds effects to a sound generated by another musician.</p></li>
+<li><p><strong>Concurrent:</strong> Multiple musicians can control the same aspect of the same musical musical process. For example, when two musicians can both control some parameter (e.g. filter cutoff frequency) on the same instrument.</p></li>
+</ul>
+<h3 id="communication-modes">Communication Modes</h3>
+<p><em>Communication</em> describes how musicians exchange information which may then influence their actions.</p>
+<ul>
+<li><p><strong>Awareness:</strong> Awareness describes all non-intentional communication. For example being able to see the movements of other musicians.</p></li>
+<li><p><strong>Indication:</strong> Indications are intentional communicative acts. For example, cueing an entrance. Deliberate nods and glances between musicians may be indications.</p></li>
+<li><p><strong>Exchanges:</strong> Exchange is the transfer of musical data between musicians. For example, in a digital ensemble on musician might send a sequence of notes to another’s instrument. Or in a jazz ensemble a soloist might use a motif from the previous soloist.</p></li>
+</ul>
+<h3 id="organisation-modes">Organisation Modes</h3>
+<p><em>Organisation</em> describes the relationships between musicians. Organisation does not directly affect the sound production, but it impacts how the communication and cooperation modes operate.</p>
+<ul>
+<li><p><strong>Nomination: </strong> Nomination is that act of de fining the roles of musicians within the group. For example one musician might be the conductor, another might be a soloist.</p></li>
+<li><p><strong>Grouping</strong> The act of grouping de fines a hierarchy of groups of instruments. For example a musician might be in the group “viola players” as well as in the group “string section.”</p></li>
+<li><p><strong>Selection</strong> Selection is the act of choosing a group or instrument for cooperation or communication. For example, a conductor might gesture to the wind section (thereby selecting them) before cueing their entrance (indication.)</p></li>
+</ul>
+<h2 id="the-boeuf-components">The Boeuf components</h2>
+<p>[TODO]</p>
+<h2 id="navigate">Navigate</h2>
+<ul>
+<li>The BOEUF project: <a href="https://bf-collab.net/bf/"></a></li>
+<li>The Bf-Pd library: <a href="https://gitlab.cristal.univ-lille.fr/boeuf/bf-pd/blob/master/README.md"></a></li>
+</ul>
diff --git a/doc/build.sh b/doc/build.sh
new file mode 100755
index 0000000000000000000000000000000000000000..3c23d2182f736010bdfb764f7966300bbf577712
--- /dev/null
+++ b/doc/build.sh
@@ -0,0 +1,3 @@
+pandoc ../README.md -s -o ../index.html --lua-filter=img/md_to_html.lua -c doc/img/style.css
+pandoc boeuf.md -o boeuf.html
+pandoc objects.md -o objects.html
diff --git a/doc/img/.style.css.swp b/doc/img/.style.css.swp
new file mode 100644
index 0000000000000000000000000000000000000000..200683201616607614bd5b6e55c649b89baaa2a6
Binary files /dev/null and b/doc/img/.style.css.swp differ
diff --git a/doc/img/md_to_html.lua b/doc/img/md_to_html.lua
new file mode 100644
index 0000000000000000000000000000000000000000..64a4cbd8eef1d037853ed646fce9c1fd12f14cbc
--- /dev/null
+++ b/doc/img/md_to_html.lua
@@ -0,0 +1,5 @@
+function Link(el)
+ el.target = string.gsub(el.target, "%.md", ".html")
+ return el
+end
+
diff --git a/doc/img/start.gif b/doc/img/start.gif
index e96a5db8a01ec820e188e5fa3e776c202de77ac5..b1d04927d70f78480e5192b66adb57eaed6a8db4 100644
Binary files a/doc/img/start.gif and b/doc/img/start.gif differ
diff --git a/doc/img/style.css b/doc/img/style.css
new file mode 100644
index 0000000000000000000000000000000000000000..632a48bcdbaa6bacd0b7706d88645bacd12a44d5
--- /dev/null
+++ b/doc/img/style.css
@@ -0,0 +1,4 @@
+
+h1 {
+ color:red;
+}
diff --git a/doc/index.html b/doc/index.html
new file mode 100644
index 0000000000000000000000000000000000000000..11e035906f6b5c57a5faceba8bc60bad4cdf26da
--- /dev/null
+++ b/doc/index.html
@@ -0,0 +1,78 @@
+<h1 id="bf-pd-a-puredata-external-for-building-digital-orchestras">bf-pd : a PureData external for building Digital Orchestras</h1>
+<h2 id="introduction-what-is-bf-pd-and-why-do-you-need-it">Introduction: What is bf-pd and why do you need it?</h2>
+<p>Digital instruments allow us to do things that were not possible with purely acoustic instruments. For example musicians can share data between instruments in real-time, in effect creating distributed multi-musician super-instruments. Musicians such as The Hub have been doing this since at least the 1970s. Contemporary digital musicians often write their own software instruments to re-create these functionalities.</p>
+<p>Bf-pd is a library built in PureData (Pd) which enables communication and cooperation between digital instruments. Bf-pd can be integrated into any instrument built in Pd. It provides a <em>collaboration window</em> from which musicians can view each others’ activity and share control of instrument parameters and other musical data.</p>
+<p>The design of bf-pd is based on the BOEUF conceptual framework which consists of a classification of modes of collaboration used in collective music performance, and a set of components which affords them. More details on the BOEUF conceptual framework can be found <a href="doc/boeuf.md">on this page</a>.</p>
+<h2 id="installing-bf-pd">Installing bf-pd</h2>
+<ul>
+<li>Download and install Pure Data (>=0.51) for your operating system from https://puredata.info/downloads/pure-data</li>
+<li>Install the <strong>mrpeach</strong> library using Deken (PD -> Help -> Find Externals)</li>
+<li>Install <strong>bf-pd</strong> using Deken</li>
+</ul>
+<h2 id="getting-started-building-your-instrument">Getting started: Building your instrument</h2>
+<figure>
+<img src="doc/img/start.gif" alt="" /><figcaption>doc/img/start.gif</figcaption>
+</figure>
+<p>Starting from an existing instrument made in PureData :</p>
+<ol type="1">
+<li>Create a declare object with -path bf-pd</li>
+<li>Create a bf-instrument object with your instrument name as argument</li>
+<li>Connect the sound output of your instrument to its inlet</li>
+<li>Create a bf-param object for each control you want to share with the others and insert it into your instrument</li>
+<li>Create a bf-session object with the name of the session you want to connect to</li>
+</ol>
+<h3 id="parameters-and-outputs">Parameters and outputs</h3>
+<p><strong>Parameters</strong> correspond to controls you have over your instrument and that you want to share with others.</p>
+<figure>
+<img src="doc/img/bf-param.gif" alt="" /><figcaption>doc/img/bf-param.gif</figcaption>
+</figure>
+<p><strong>Outputs</strong> have the same properties but correspond to musical content produced by your instruments (notes, onsets, envelopes …). They can be used to control others parameters. Three default outputs are automatically created by bf-pd and extracted from the audio you send to bf-instrument : pitch, onsets, loudness.</p>
+<figure>
+<img src="doc/img/bf-output.gif" alt="" /><figcaption>doc/img/bf-output.gif</figcaption>
+</figure>
+<p>Parameters and outputs have the same <strong>arguments</strong> :</p>
+<ol type="1">
+<li>instrument name</li>
+<li>parameter / output namenumberOfValues valuesType parameterIndex ]</li>
+<li>number of values</li>
+<li>type of values : cont (0 to 1), midi (0 to 127), bool (0 or 1), bang</li>
+<li>index : position in the collaboration window</li>
+</ol>
+<h2 id="performance-making-music-together-using-bf-pd">Performance: Making music together using bf-pd</h2>
+<h3 id="the-collaboration-window">The collaboration window</h3>
+<p>The collaboration window is a collaboration interface that comes with bf-pd and provides a way to connect your instrument with other instruments in the session.</p>
+<p>To open the collaboration window, simply check the <em>collab</em> toggle in the bf-instrument object.</p>
+<p>The leftmost green column shows your instrument with its outputs and parameters. The grey columns show the other instruments in the session with their respective activity, outputs and parameters.</p>
+<figure>
+<img src="doc/img/collabwin.png" alt="" /><figcaption>doc/img/collabwin.png</figcaption>
+</figure>
+<h3 id="sharing-granting-access-to-your-parameters">Sharing / granting access to your parameters</h3>
+<p>By default, all your parameters are in the <em>granted</em> mode, which means that all the other musicians can change your parameter values. You can of course change this by clicking the red <em>grant</em> toggle for each parameter, or the <em>grant all</em> toggle at the top of your column. When your parameter is not granted, values <em>asked</em> by others are only displayed on the gray widgets. You can accept their <em>ask</em> by using the <em>1x</em> bang.</p>
+<figure>
+<img src="doc/img/sharing.gif" alt="" /><figcaption>doc/img/sharing.gif</figcaption>
+</figure>
+<h3 id="using-others-parameters-and-outputs-to-change-your-parameters">Using others parameters and outputs to change your parameters</h3>
+<p>A <em>watch</em> bus selector is placed below each parameter and output of the other instruments. By choosing a bus other than 0, the values are sent to the corresponding bus and can be sent to your parameters connected to the same bus using the <em>watching</em> selector.</p>
+<figure>
+<img src="doc/img/watching.gif" alt="" /><figcaption>doc/img/watching.gif</figcaption>
+</figure>
+<h3 id="controlling-others-parameters-with-your-parameters-and-outputs">Controlling others parameters with your parameters and outputs</h3>
+<p>Symmetrically, you can control others parameters by choosing a non-zero bus on the <em>ask</em> selector and the same <em>asking</em> bus below one of your outputs or parameters. This requires however that the parameter that you want to controlled is <em>granted</em> (i.e. that the green <em>granted</em> toggle is checked).</p>
+<figure>
+<img src="doc/img/asking.gif" alt="" /><figcaption>doc/img/asking.gif</figcaption>
+</figure>
+<h3 id="directly-asking-controlling-others-parameters">Directly asking / controlling others parameters</h3>
+<p>You can also ask another instrument’s parameter to be set to a specific value by interacting with the white sliders/toggles/bangs. It the access is granted, the value will be directly set.</p>
+<figure>
+<img src="doc/img/direct_asking.gif" alt="" /><figcaption>doc/img/direct_asking.gif</figcaption>
+</figure>
+<h2 id="demo-video">Demo Video</h2>
+<p><a href="https://pod.univ-lille.fr/video/19614-bf-pd-collaboration-window/"><img src="doc/img/video.png" height="300px"/><br/>Video demoing the collab window for bf-pd</a>.</p>
+<h2 id="more-resources">More resources</h2>
+<p>Documentation for each of the user objects in bf-pd can be found in <a href="doc/objects.md">objects.md</a> and on help patches directly in PureData (right-click an object -> Help)</p>
+<p>The <em>BOEUF conceptual framework</em> describes the <em>modes of collaboration</em> used in musical collaboration and describes a set of <em>components</em> for realizing these modes in a software framework. Bf-pd is based on this framework. More info can be found in <a href="doc/boeuf.md">boeuf.md</a>.</p>
+<h2 id="authors">Authors</h2>
+<ul>
+<li>Luke Dahl, University of Virginia</li>
+<li>Florent Berthaut, University of Lille</li>
+</ul>
diff --git a/doc/objects.html b/doc/objects.html
new file mode 100644
index 0000000000000000000000000000000000000000..43880adc55794197596cd56e0f906bec8c168df6
--- /dev/null
+++ b/doc/objects.html
@@ -0,0 +1,98 @@
+<p>Bf-pd is a library of pd objects for enabling real-time collaboration. This page describes each of the objects in bf-pd, their arguments, inlets and outlets.</p>
+<h2 id="bf-session">bf-session</h2>
+<p>A bf-session represents a group of musicians (as represented by their bf-instruments) making music together. Within the bf-pd system a bf-session works “behind the scenes” to coordinate the data exchanged between bf-instruments.</p>
+<p>To participate in a bf-session there must be at least one instance of bf-session instantiated somewhere. A bf-session has a name, e.g. “technoJam1”, and this session would be instantiated as [bf-session technoJam1].</p>
+<p>There can be more than one bf-session object with the same name within the patches running in Pd. So you can add the same bf-session to each bf-instrument. (However if you instantiate two different bf-sessions within pd, the second one will not work.)</p>
+<h6 id="arguments">Arguments:</h6>
+<ol type="1">
+<li>The name of the session.</li>
+</ol>
+<h6 id="outlets">Outlets:</h6>
+<ol type="1">
+<li>Outlet 1 sends all the session messages which are used “behind the scenes” by the bf-pd objects.</li>
+</ol>
+<h2 id="bf-instrument">bf-instrument</h2>
+<p>A bf-instrument represents a musical instrument within the bf-pd system. Each instrument joins a bf-session and can contain bf-params and bf-outputs. To create an instrument you should instantiate a bf-instrument with the name of your instrument, e.g. [bf-instrument myDrumMachine].</p>
+<p>The audio output of your instrument should be connected to the first inlet of bf-instrument object. The interface has an <em>activity monitor</em> which shows a simple representation of the changing spectrum of the instrument’s sound, and the activity for each bf-instrument in the bf-session appears in the <em>collaboration window</em>. (Note: you must also send your audio to [dac~] in order to hear it!)</p>
+<p>The <em>collaboration window</em> can be opened with the toggle in the bf-instrument object. If musicians enter or leave the session you may need to close and re-open the collaboration window.</p>
+<h6 id="arguments-1">Arguments:</h6>
+<ol type="1">
+<li>The name of the instrument.</li>
+</ol>
+<h6 id="inlets">Inlets:</h6>
+<ol type="1">
+<li>The audio output of your instrument should be sent here. (It must also be sent to [dac~].)</li>
+</ol>
+<h2 id="bf-param">bf-param</h2>
+<p>A bf-param creates a user parameter within the bf-pd system. A bf-param can be controlled by the user of the bf-instrument it belongs to, and the bf-param will also be accessible to other instruments within the bf-session via the collaboration window, if the owner of the bf-instrument grants access.</p>
+<p>A bf-param object has a user interface within the instrument patch itself, and it also creates a user interface in the collaboration window of each musician in the session.</p>
+<p>A bf-param can be one of four <em>types</em>: * <em>cont</em> are numbers between 0.0 and 1.0. * <em>midi</em> are numbers between 0.0 and 127.0. * <em>bool</em> can take values of 0 or 1. * <em>bang</em> are bang messages which are used to trigger actions.</p>
+<p>A bf-param can be a single instance of its type or it can be a multiple, which creates an array of values within a single bf-param object. For example, a bf-param “8 bool” creates an interface with 8 toggles, and might be used to represent 8 on/off values in a drum machine sequencer.</p>
+<h6 id="arguments-2">Arguments:</h6>
+<ol type="1">
+<li>The name of the instrument, e.g. “myDrumMachine”.</li>
+<li>The name of the parameter, e.g. “kickOnOff”</li>
+<li>The dimensionality of the parameter, e.g. “8”</li>
+<li>The type of the parameter, e.g. “bool”</li>
+</ol>
+<p>So a bf-param with 8 drum machine note triggers would be: <code>[bf-param myDrumMachine kickOnOff 8 bool]</code> and creates this object within your patch:</p>
+<figure>
+<img src="/uploads/114e1a4d5f4c38d21eac50bbcebe5509/bf-param_example.png" alt="" /><figcaption>bf-param_example</figcaption>
+</figure>
+<h6 id="inlets-1">Inlets:</h6>
+<ol type="1">
+<li>Sets the value of the parameter. If the parameter is a multiple, then <em>Inlet 1</em> sets the parameter at the index last received on <em>Inlet 2</em>.</li>
+<li>Sets the index of the parameter which will be changed by sending values to <em>Inlet 1</em>.</li>
+<li>An integer in <em>Inlet 3</em> will send the value of the parameter at that index to <em>Outlet 3</em>.</li>
+</ol>
+<p>(The first two inlets for bf-param operate similar to the first two inlets for [array set] in Pd.)</p>
+<h6 id="outlets-1">Outlets:</h6>
+<ol type="1">
+<li>The parameter value of the most recent change to the bf-param (whether that change came from the inlets, the UI, or via the collaboration window.)</li>
+<li>A list of the parameter value of the most recent change, and the index of the parameter that was changed.</li>
+<li>The parameter value for the index that was sent to <em>Inlet 3</em>.</li>
+</ol>
+<h2 id="bf-output">bf-output</h2>
+<p>An bf-output can be used to send some musical data from your bf-instrument to another instrument in the same bf-session. A bf-output can have the same types and multiplicity as a bf-param.</p>
+<p>Each bf-output in your bf-instrument will appear [TODO continue]</p>
+<p>is a musical attribute that is produced by a module or instrument. They can have the same types as parameters. Outputs can be retrieved and watched by other instruments, and function as a means for both awareness and exchange.</p>
+<h6 id="arguments-3">Arguments:</h6>
+<ol type="1">
+<li>arg1</li>
+</ol>
+<h6 id="inlets-2">Inlets:</h6>
+<ol type="1">
+<li>blah</li>
+</ol>
+<h6 id="outlets-2">Outlets:</h6>
+<ol type="1">
+<li>blah</li>
+</ol>
+<h2 id="bf-watch">bf-watch</h2>
+<p>Bf-watch is used to get data from another bf-instrument into your bf-instrument.</p>
+<h6 id="arguments-4">Arguments:</h6>
+<ol type="1">
+<li>arg1</li>
+</ol>
+<h6 id="inlets-3">Inlets:</h6>
+<ol type="1">
+<li>blah</li>
+</ol>
+<h6 id="outlets-3">Outlets:</h6>
+<ol type="1">
+<li>blah</li>
+</ol>
+<h2 id="bf-ask">bf-ask</h2>
+<p>Description blah blah</p>
+<h6 id="arguments-5">Arguments:</h6>
+<ol type="1">
+<li>arg1</li>
+</ol>
+<h6 id="inlets-4">Inlets:</h6>
+<ol type="1">
+<li>blah</li>
+</ol>
+<h6 id="outlets-4">Outlets:</h6>
+<ol type="1">
+<li>blah</li>
+</ol>