Add some additional texts

Observatory-Control-System/Camera-Control-System/More-CCS-Procedures/More-CCS-Procedures-index.rst

@@ -7,7 +7,7 @@
 
 .. This is the label that can be used as for cross referencing this file.
 .. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
-.. _Camera-General-index: 
+.. _More-CCS-Procedures-index: 
 .. Each section should includes a label for cross referencing to a given area.
 .. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
 .. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.

Observatory-Control-System/EAS/All-sky-Camera/All-sky-Camera-index.rst

@@ -0,0 +1,18 @@
+.. Review the README in this directory on instructions to contribute.
+.. Static objects, such as figures, should be stored in the _static directory. Review the _static/README in this file's directory on instructions to contribute.
+.. Do not remove the comments that describe each section. They are included to provide guidance to contributors.
+.. Do not remove other content provided in the templates, such as a section. Instead, comment out the content and include comments to explain the situation. For example:
+    - If a section within the template is not needed, comment out the section title and label reference. Do not delete the expected section title, reference or related comments provided from the template.
+    - If a file cannot include a title (surrounded by ampersands (#)), comment out the title from the template and include a comment explaining why this is implemented (in addition to applying the ``title`` directive).
+
+.. This is the label that can be used as for cross referencing this file.
+.. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
+.. _All-Sky-Camera-index: 
+.. Each section should includes a label for cross referencing to a given area.
+.. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
+.. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
+.. An error will alert you of identical labels during the build process.
+
+######################
+All-sky Camera
+######################

Observatory-Control-System/EAS/DREAM/DREAM-index.rst

@@ -0,0 +1,18 @@
+.. Review the README in this directory on instructions to contribute.
+.. Static objects, such as figures, should be stored in the _static directory. Review the _static/README in this file's directory on instructions to contribute.
+.. Do not remove the comments that describe each section. They are included to provide guidance to contributors.
+.. Do not remove other content provided in the templates, such as a section. Instead, comment out the content and include comments to explain the situation. For example:
+    - If a section within the template is not needed, comment out the section title and label reference. Do not delete the expected section title, reference or related comments provided from the template.
+    - If a file cannot include a title (surrounded by ampersands (#)), comment out the title from the template and include a comment explaining why this is implemented (in addition to applying the ``title`` directive).
+
+.. This is the label that can be used as for cross referencing this file.
+.. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
+.. _DREAM-index: 
+.. Each section should includes a label for cross referencing to a given area.
+.. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
+.. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
+.. An error will alert you of identical labels during the build process.
+
+######################
+DREAM
+######################

Observatory-Control-System/EAS/EAS-index.rst

@@ -40,4 +40,26 @@ DREAM
    :glob:
    :titlesonly:
 
-   DREAM/DREAM-index.rst
+   DREAM/DREAM-index.rst
+
+.. _EAS-All-sky-Camera:
+
+All-sky Camera
+===============
+
+.. toctree::
+   :glob:
+   :titlesonly:
+
+   All-sky-Camera/All-sky-Camera-index.rst
+
+.. _EAS-ESS:
+
+ESS
+===============
+
+.. toctree::
+   :glob:
+   :titlesonly:
+
+   ESS/ESS-index.rst

Observatory-Control-System/EAS/ESS/ESS-index.rst

@@ -0,0 +1,18 @@
+.. Review the README in this directory on instructions to contribute.
+.. Static objects, such as figures, should be stored in the _static directory. Review the _static/README in this file's directory on instructions to contribute.
+.. Do not remove the comments that describe each section. They are included to provide guidance to contributors.
+.. Do not remove other content provided in the templates, such as a section. Instead, comment out the content and include comments to explain the situation. For example:
+    - If a section within the template is not needed, comment out the section title and label reference. Do not delete the expected section title, reference or related comments provided from the template.
+    - If a file cannot include a title (surrounded by ampersands (#)), comment out the title from the template and include a comment explaining why this is implemented (in addition to applying the ``title`` directive).
+
+.. This is the label that can be used as for cross referencing this file.
+.. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
+.. _ESS-index: 
+.. Each section should includes a label for cross referencing to a given area.
+.. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
+.. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
+.. An error will alert you of identical labels during the build process.
+
+######################
+ESS
+######################

Observatory-Control-System/Observing-Tools/Tools-index.rst

@@ -42,6 +42,8 @@ RubinTV
 
   RubinTv/RubinTv-index.rst
 
+.. _Observing-Tools-Sky-Almanac:
+
 Sky Almanac
 ===========
 

index.rst

@@ -74,45 +74,54 @@ Observing Constraints
 
    Constraints <Observing-Constraints/Observing-Constraints-index>
 
+.. _Obs-Ops-MainTel-Operations:
 
-.. _Obs-Ops-AuxTel-Operations:
+Simonyi Telescope Operations
+============================
 
-Auxiliary Telescope Operations
-==============================
-This section comprises information and procedures pertinent to the operation of the Auxiliary Telescope. 
-It includes the standard operations for an ordinary, scheduler-driven observation night, 
-as well as unique procedures and manual interventions that may be needed under more exceptional circumstances. 
-It also incorporates an exhaustive list of identified problems and their corresponding troubleshooting guidelines 
-to recover functionality of the Auxiliary Telescope and LATISS. 
+Herein lies comprehensive information for Simonyi Telescope operations. 
+It covers essential aspects of the standard operations and other non-routine procedures, alongside 
+troubleshooting guidance for common issues encountered during the stages of system integration, testing and commissioning.
 
 .. toctree::
     :glob:
     :maxdepth: 2 
     :titlesonly:
 
 
-    AuxTel <AuxTel/AuxTel-index>
-
+    Simonyi <MainTel/MainTel-index>
 
-.. _Obs-Ops-MainTel-Operations:
+.. _Obs-Ops-AuxTel-Operations:
 
-Simonyi Telescope Operations
-============================
+Auxiliary Telescope Operations
+==============================
 
-This section encapsulates everything to operate, regular operations and troubleshoot for Simonyi Telescope. 
+Under this section is comprised information and procedures pertinent to the operation of the Auxiliary Telescope. 
+It includes the standard operations for an ordinary, scheduler-driven observation night, 
+as well as unique procedures and manual interventions that may be needed under more exceptional circumstances. 
+It also incorporates an exhaustive list of identified problems and their corresponding troubleshooting guidelines 
+to recover functionality of the Auxiliary Telescope and LATISS. 
 
 .. toctree::
     :glob:
     :maxdepth: 2 
     :titlesonly:
 
 
-    Simonyi <MainTel/MainTel-index>
+    AuxTel <AuxTel/AuxTel-index>
+
+
 
 .. _Obs-Ops-Observatory-Control-System:
 
 Observatory Control System
 ==========================
+
+Here is offered an extensive exploration of the observatory's control system. 
+It provides comprehensive information on system components, their operations, configuration, along with troubleshooting support. 
+Additionally, it provides an inventory of valuable observing tools to facilitate data visualization and system monitoring 
+during nighttime operations. 
+
 .. toctree::
     :glob:
     :maxdepth: 2