First pass at getting new files included in the docs

philipstarkey · philipstarkey · commit 36dad35b5bf6 · 2024-01-27T12:37:53.000+11:00
diff --git a/docs/source/api/index.rst b/docs/source/api/index.rst
@@ -7,5 +7,12 @@ API Reference
 	:template: autosummary-module.rst
 	:recursive:
 
+	labscript.core
+	labscript.outputs
+	labscript.remote
+	labscript.constants
 	labscript.labscript
 	labscript.functions
+	labscript.base
+	labscript.compiler
+	labscript.utils
diff --git a/docs/source/connection_table.rst b/docs/source/connection_table.rst
@@ -5,7 +5,7 @@ The connection table maps out the way input/output devices are connected to each
 .. image:: img/connection_diagram.png
 	:alt: Example wiring diagram.
 
-Here we see two :py:class:`PseudoclockDevice <labscript.PseudoclockDevice>` instances in the top tier of the diagram. They do not have a parent device that tells them when to update their output (this is true for all :py:class:`PseudoclockDevice <labscript.PseudoclockDevice>` instances). However, all but one (the master pseudoclock device) must be triggered by an output clocked by the master pseudoclock device. 
+Here we see two :py:class:`PseudoclockDevice <labscript.core.PseudoclockDevice>` instances in the top tier of the diagram. They do not have a parent device that tells them when to update their output (this is true for all :py:class:`PseudoclockDevice <labscript.PseudoclockDevice>` instances). However, all but one (the master pseudoclock device) must be triggered by an output clocked by the master pseudoclock device. 
 
 Each :py:class:`PseudoclockDevice <labscript.PseudoclockDevice>` instance should have one or more :py:class:`Pseudoclock <labscript.Pseudoclock>` children. Some :py:class:`PseudoclockDevice <labscript.PseudoclockDevice>` instances may automatically create these children for you (check the device specific documentation). In turn, each :py:class:`Pseudoclock <labscript.Pseudoclock>` will have one of more :py:class:`ClockLine <labscript.ClockLine>` instances connected to it. These :py:class:`ClockLine <labscript.ClockLine>` instances generally refer to physical outputs of a device which will be used to clock another device. However, in some cases, one or more :py:class:`ClockLine <labscript.ClockLine>` instances may be internally created for you (check the device specific documentation).
 
