moving "Understanding Tasks" into docs

README.md

@@ -179,44 +179,6 @@ For more information, see [here][RESTful API].
 
 <!--getting-started-end-->
 
-## Understanding Tasks in pydase
-
-In `pydase`, a task is defined as an asynchronous function without arguments contained in a class that inherits from `DataService`. These tasks usually contain a while loop and are designed to carry out periodic functions.
-
-For example, a task might be used to periodically read sensor data, update a database, or perform any other recurring job. One core feature of `pydase` is its ability to automatically generate start and stop functions for these tasks. This allows you to control task execution via both the frontend and python clients, giving you flexible and powerful control over your service's operation.
-
-Another powerful feature of `pydase` is its ability to automatically start tasks upon initialization of the service. By specifying the tasks and their arguments in the `_autostart_tasks` dictionary in your service class's `__init__` method, `pydase` will automatically start these tasks when the server is started. Here's an example:
-
-```python
-from pydase import DataService, Server
-
-class SensorService(DataService):
-    def __init__(self):
-        super().__init__()
-        self.readout_frequency = 1.0
-        self._autostart_tasks["read_sensor_data"] = ()
-
-    def _process_data(self, data: ...) -> None:
-        ...
-
-    def _read_from_sensor(self) -> Any:
-        ...
-
-    async def read_sensor_data(self):
-        while True:
-            data = self._read_from_sensor()
-            self._process_data(data)  # Process the data as needed
-            await asyncio.sleep(self.readout_frequency)
-
-
-if __name__ == "__main__":
-    service = SensorService()
-    Server(service).run()
-```
-
-In this example, `read_sensor_data` is a task that continuously reads data from a sensor. By adding it to the `_autostart_tasks` dictionary, it will automatically start running when `Server(service).run()` is executed.
-As with all tasks, `pydase` will generate `start_read_sensor_data` and `stop_read_sensor_data` methods, which can be called to manually start and stop the data reading task. The readout frequency can be updated using the `readout_frequency` attribute.
-
 ## Understanding Units in pydase
 
 `pydase` integrates with the [`pint`](https://pint.readthedocs.io/en/stable/) package to allow you to work with physical quantities within your service. This enables you to define attributes with units, making your service more expressive and ensuring consistency in the handling of physical quantities.
@@ -425,7 +387,7 @@ We welcome contributions! Please see [contributing.md](https://pydase.readthedoc
 [Web Interface Access]: #accessing-the-web-interface
 [Short RPC Client]: #connecting-to-the-service-via-python-rpc-client
 [Customizing Web Interface]: #customizing-the-web-interface
-[Task Management]: #understanding-tasks-in-pydase
+[Task Management]: https://pydase.readthedocs.io/en/stable/user-guide/Tasks/
 [Units]: #understanding-units-in-pydase
 [Property Validation]: #using-validate_set-to-validate-property-setters
 [Custom Components]: https://pydase.readthedocs.io/en/latest/user-guide/Components/#custom-components-pydasecomponents

docs/index.md

@@ -10,6 +10,6 @@
 [Web Interface Access]: ./getting-started.md#accessing-the-web-interface
 [Short RPC Client]: ./getting-started.md#connecting-to-the-service-via-python-rpc-client
 [Customizing Web Interface]: ./user-guide/interaction/main.md#customization-options
-[Task Management]: ./getting-started.md#understanding-tasks-in-pydase
+[Task Management]: ./user-guide/Tasks.md
 [Units]: ./getting-started.md#understanding-units-in-pydase
 [Property Validation]: ./getting-started.md#using-validate_set-to-validate-property-setters

docs/user-guide/Tasks.md

@@ -0,0 +1,39 @@
+# Understanding Tasks
+
+In `pydase`, a task is defined as an asynchronous function without arguments contained in a class that inherits from `pydase.DataService`. These tasks usually contain a while loop and are designed to carry out periodic functions.
+
+For example, a task might be used to periodically read sensor data, update a database, or perform any other recurring job. One core feature of `pydase` is its ability to automatically generate start and stop functions for these tasks. This allows you to control task execution via both the frontend and python clients, giving you flexible and powerful control over your service's operation.
+
+Another powerful feature of `pydase` is its ability to automatically start tasks upon initialization of the service. By specifying the tasks and their arguments in the `_autostart_tasks` dictionary in your service class's `__init__` method, `pydase` will automatically start these tasks when the server is started. Here's an example:
+
+```python
+import pydase
+
+
+class SensorService(pydase.DataService):
+    def __init__(self):
+        super().__init__()
+        self.readout_frequency = 1.0
+        self._autostart_tasks["read_sensor_data"] = ()
+
+    def _process_data(self, data: ...) -> None:
+        ...
+
+    def _read_from_sensor(self) -> Any:
+        ...
+
+    async def read_sensor_data(self):
+        while True:
+            data = self._read_from_sensor()
+            self._process_data(data)  # Process the data as needed
+            await asyncio.sleep(self.readout_frequency)
+
+
+if __name__ == "__main__":
+    service = SensorService()
+    pydase.Server(service=service).run()
+```
+
+In this example, `read_sensor_data` is a task that continuously reads data from a sensor. By adding it to the `_autostart_tasks` dictionary, it will automatically start running when `pydase.Server(service).run()` is executed.
+As with all tasks, `pydase` will generate `start_read_sensor_data` and `stop_read_sensor_data` methods, which can be called to manually start and stop the data reading task. The readout frequency can be updated using the `readout_frequency` attribute.
+

mkdocs.yml

@@ -8,6 +8,7 @@ nav:
     - Components Guide: user-guide/Components.md
     - Interacting with pydase Services: user-guide/interaction/main.md
     - Service Persistence: user-guide/Service_Persistence.md
+    - Understanding Tasks: user-guide/Tasks.md
   - Developer Guide: 
     - Developer Guide: dev-guide/README.md
     - API Reference: dev-guide/api.md