Convert docs from ipynb to qmd (#2376)

Needed for #2078, since that doesn't work on notebooks directly. Taking
this as an intermediate step to avoid getting to many conflicts.

Even if we don't make the switch, I think it is better to have all of
our docs in the same format. QMD support seems a bit more first class
and transparent when working in a repository.

I ran this locally and verified that the converted pages still look the
same.

Author: visr

docs/_quarto.yml

@@ -11,9 +11,9 @@ website:
       - text: "Overview"
         file: index.qmd
       - text: "Tutorials"
-        file: tutorial/natural-flow.ipynb
+        file: tutorial/natural-flow.qmd
       - text: "How-to guides"
-        file: guide/examples.ipynb
+        file: guide/examples.qmd
       - text: "Concepts"
         file: concept/concept.qmd
       - text: "Reference"
@@ -34,17 +34,17 @@ website:
         - contact.qmd
     - title: "Tutorials"
       contents:
-        - tutorial/natural-flow.ipynb
-        - tutorial/irrigation-demand.ipynb
-        - tutorial/reservoir.ipynb
+        - tutorial/natural-flow.qmd
+        - tutorial/irrigation-demand.qmd
+        - tutorial/reservoir.qmd
     - title: "How-to guides"
       contents:
-        - guide/examples.ipynb
+        - guide/examples.qmd
         - guide/qgis.qmd
         - guide/coupling.qmd
         - section: "Coupling guides"
           contents:
-            - guide/delwaq.ipynb
+            - guide/delwaq.qmd
         - guide/debug.qmd
     - title: "Concepts"
       contents:

docs/concept/allocation.qmd

@@ -233,7 +233,7 @@ $$
 
 ## Example
 
-The following is an example of an optimization problem for the example shown [here](/guide/examples.ipynb#model-with-allocation-user-demand):
+The following is an example of an optimization problem for the example shown [here](/guide/examples.qmd#model-with-allocation-user-demand):
 
 
 ```{julia}

docs/dev/addnode.qmd

@@ -212,7 +212,7 @@ There are several parts of the documentation which should be updated with the ne
 - If the node has a rol in the physical layer, `docs/core/equations` should contain a short explanation and if possible an analytical expression for the behavior of the new node;
 - If the node has a role in allocation, `docs/core/allocation` should make this role clear;
 - `docs/reference/node/new-node-type.qmd` should contain a short explanation of the node and the possible schemas associated with it;
-- The example models constructed in `docs/guide/examples.ipynb` should be extended with the new node type or a new example model with the new node type should be made.
+- The example models constructed in `docs/guide/examples.qmd` should be extended with the new node type or a new example model with the new node type should be made.
 - In `_quarto.yml` add `NewNodeType` to the "Node types" contents for the Python API reference.
 
 

docs/guide/coupling.qmd

@@ -19,4 +19,4 @@ flowchart LR
 
 Delwaq can calculate the concentration of substances in [Basin](/reference/node/basin.qmd) nodes over time, based on initial concentrations, and of [FlowBoundary](/reference/node/flow-boundary.qmd) nodes. Ribasim exposes the `Basin / concentration`, `Basin / concentration_state`, `FlowBoundary / concentration`, and `LevelBoundary / concentration` tables to setup these substances and concentrations.
 
-When a Ribasim model ran with the above tables, one can use the utilities in the `delwaq` namespace of the Ribasim Python API to generate the input required for Delwaq to run, as well as to parse the output from Delwaq into a Ribasim compatible format. For more information see the [guide](/guide/delwaq.ipynb).
+When a Ribasim model ran with the above tables, one can use the utilities in the `delwaq` namespace of the Ribasim Python API to generate the input required for Delwaq to run, as well as to parse the output from Delwaq into a Ribasim compatible format. For more information see the [guide](/guide/delwaq.qmd).