fixed html buikd

ICRAR · Sep 5, 2021 · c95f530 · c95f530
1 parent 7689214
commit c95f530
Show file tree

Hide file tree

Showing 3 changed files with 1 addition and 2 deletions.
diff --git a/docs/development/component_binding.md → component_binding.md b/docs/development/component_binding.md → component_binding.md
diff --git a/docs/development/dev_index.rst b/docs/development/dev_index.rst
@@ -24,7 +24,6 @@ Please refer to the |daliuge| :doc:`../intro` for a top-level introduction to th
  service_components
  wrap_existing
  test_and_debug
- component_binding
  eagle_integration
  deployment_testing
 

diff --git a/docs/development/dev_intro.rst b/docs/development/dev_intro.rst
@@ -41,4 +41,4 @@ The |daliuge| system consists of three main parts:
 
 All three of them are essentially independent and can be used without the others running. The EAGLE visual graph editor is a web application, which deals with *Nodes*, i.e. with JSON descriptions of *Components*. It also allows users to define these descriptions starting from node templates, which are contained in a standard palette, called 'All Nodes', which is loaded when EAGLE is started in a browser. The nodes of one or multiple palettes are used to construct a workflow graph. Graphs and Palettes are stored as JSON files and they are essentially the same, except for the additional arrangement and visual information in a graph file. A graph can be stored as a palette and then used to create other graphs.
 
-The JSON description of the nodes in a palette can be generated from the component interface code by means of special in-line documentation tags. This procedure is described in detail in :doc:`component_binding`.
+The JSON description of the nodes in a palette can be generated from the component interface code by means of special in-line documentation tags. This procedure is described in detail in _reference_.