re-label copernicus product information as documentation, move away from user guide & tutorials

Author: j-atkins

docs/index.md

@@ -5,7 +5,7 @@
 :hidden:
 
 Home <self>
-user-guide/index
+User Guide & Documation <user-guide/index>
 api/index
 contributing/index
 VirtualShip Website <https://virtualship.oceanparcels.org/>

docs/user-guide/additional_information.md …ide/documentation/copernicus_products.mddocs/user-guide/additional_information.md renamed to docs/user-guide/documentation/copernicus_products.md docs/user-guide/additional_information.md renamed to docs/user-guide/documentation/copernicus_products.md

@@ -1,8 +1,4 @@
-# Additional information
-
-This file contains additional technical information and guidance not covered in the [Quickstart](https://virtualship.readthedocs.io/en/latest/user-guide/quickstart.html) guide or in the [Tutorials](https://virtualship.readthedocs.io/en/latest/user-guide/tutorials/index.html).
-
-### Copernicus Marine products
+# Copernicus Marine products
 
 VirtualShip supports running experiments anywhere in the global ocean from 1993 through to the present day (and approximately two weeks into the future), using the suite of products available from the [Copernicus Marine Data Store](https://data.marine.copernicus.eu/products).
 
@@ -23,7 +19,7 @@ The ethos for automated dataset selection in `virtualship fetch` is to prioritis
 ```
 
 ```{warning}
-In the rare situation where the start and end times of an expedition schedule span different products, which is possible in the case of the end time being in the **Reanalysis_interim** period and the start time in the **Reanalysis** period, the **Analysis & Forecast** product will be automatically selected, as this spans back enough in time for this niche case.
+In the rare situation where the start and end times of an expedition schedule span different products *and* there is no overlap in the respective dataset timeseries, which is possible in the case of the end time being in the **Reanalysis_interim** period and the start time in the **Reanalysis** period, the **Analysis & Forecast** product will be automatically selected, as this spans back enough in time for this niche case.
 ```
 
 ### Data availability

docs/user-guide/index.md

@@ -6,5 +6,12 @@
 quickstart
 tutorials/index
 assignments/index
-additional_information
+```
+
+# Documentation
+
+```{toctree}
+:maxdepth: 1
+
+documentation/copernicus_products.md
 ```

docs/user-guide/quickstart.md

@@ -81,7 +81,7 @@ For the underway ADCP, there is a choice of using the 38 kHz OceanObserver or th
 ### Waypoint datetimes
 
 ```{note}
-VirtualShip supports simulating experiments in the years 1993 through to the present day (and up to two weeks in the future) by leveraging the suite of products available Copernicus Marine Data Store (see [Fetch the data](#fetch-the-data)). The data download is automated based on the time period selected in the schedule. Different periods will rely on different products from the Copernicus Marine catalogue (see [Additional information](additional_information.md)).
+VirtualShip supports simulating experiments in the years 1993 through to the present day (and up to two weeks in the future) by leveraging the suite of products available Copernicus Marine Data Store (see [Fetch the data](#fetch-the-data)). The data download is automated based on the time period selected in the schedule. Different periods will rely on different products from the Copernicus Marine catalogue (see [Documentation](documentation/copernicus_products.md)).
 ```
 
 You will need to enter dates and times for each of the sampling stations/waypoints selected in the MFP route planning stage. This can be done under _Schedule Editor_ > _Waypoints & Instrument Selection_ in the planning tool.