deploy: e08643c

head/tutorials/custom_contracts/index.html

@@ -309,7 +309,7 @@ <h2 id="key-concepts">
   <li><strong>Contract Interface</strong>: FireFly defines a common, blockchain agnostic way to describe smart contracts. This is referred to as a Contract Interface. A contract interface is written in the FireFly Interface (FFI) format. It is a simple JSON document that has a name, a namespace, a version, a list of methods, and a list of events.</li>
 </ul>
 
-<p>For more details, you can also have a look at the <a href="../../reference/firefly_interface_format">Reference page for the FireFly Interface Format</a>.</p>
+<p>For more details, you can also have a look at the <a href="/firefly/head/reference/firefly_interface_format.html">Reference page for the FireFly Interface Format</a>.</p>
 
 <p>For blockchains that offer a DSL describing the smart contract interface, such as Ethereum’s ABI (Application Binary Interface), FireFly offers a convenience tool to convert the DSL into the FFI format.</p>
 

head/tutorials/custom_contracts/pinning.html

@@ -296,7 +296,7 @@ <h1 id="pin-off-chain-data-to-a-custom-blockchain-transaction">
 
 <blockquote>
   <p><strong>NOTE:</strong> This is an advanced FireFly feature. Before following any of the steps in this guide, you should be very familiar
-and comfortable with the basic features of how <a href="../broadcast_data.html">broadcast messages</a> and <a href="../private_send.html">private messages</a>
+and comfortable with the basic features of how <a href="/firefly/head/tutorials/broadcast_data.html">broadcast messages</a> and <a href="/firefly/head/tutorials/private_send.html">private messages</a>
 work, be proficient at custom contract development on your blockchain of choice, and understand the
 fundamentals of how FireFly interacts with <a href="../">custom contracts</a>.</p>
 </blockquote>
@@ -437,7 +437,7 @@ <h2 id="initializing-firefly">
       </h2>
 
 
-<p>Once you have a contract designed, you can <a href="../../gettingstarted/setup_env.html">initialize your environment</a>
+<p>Once you have a contract designed, you can <a href="/firefly/head/gettingstarted/setup_env.html">initialize your environment</a>
 using the blockchain of your choice.</p>
 
 <p>No special initialization arguments are needed for Ethereum.</p>
@@ -455,7 +455,7 @@ <h2 id="invoking-the-contract">
 
 
 <p>You can follow the normal steps for <a href="/firefly/head/tutorials/custom_contracts/ethereum.html">Ethereum</a> or <a href="/firefly/head/tutorials/custom_contracts/fabric.html">Fabric</a> to define your contract
-interface and API in FireFly. When invoking the contract, you can include a <a href="../../reference/types/message.html">message payload</a>
+interface and API in FireFly. When invoking the contract, you can include a <a href="/firefly/head/reference/types/message.html">message payload</a>
 alongside the other parameters.</p>
 
 <p><code class="language-plaintext highlighter-rouge">POST</code> <code class="language-plaintext highlighter-rouge">http://localhost:5000/api/v1/namespaces/default/apis/custom-pin/invoke/sayHello</code></p>
@@ -480,12 +480,12 @@ <h2 id="listening-for-events">
       </h2>
 
 
-<p>All parties that receive the message will receive a <code class="language-plaintext highlighter-rouge">message_confirmed</code> on their <a href="../events.html">event listeners</a>.
+<p>All parties that receive the message will receive a <code class="language-plaintext highlighter-rouge">message_confirmed</code> on their <a href="/firefly/head/tutorials/events.html">event listeners</a>.
 This event confirms that the off-chain payload has been received (via data exchange or shared storage) <em>and</em>
 that the blockchain transaction has been received and sequenced. It is guaranteed that these <code class="language-plaintext highlighter-rouge">message_confirmed</code>
 events will be ordered based on the sequence of the on-chain transactions, regardless of when the off-chain
 payload becomes available. This means that all parties will order messages on a given topic in exactly the
-same order, allowing for deterministic but decentralized <a href="../../reference/events.html">event-driven architecture</a>.</p>
+same order, allowing for deterministic but decentralized <a href="/firefly/head/reference/events.html">event-driven architecture</a>.</p>