Minor cleanup and link fixes

Author: emmuhamm

docs/explanation.md

@@ -2,7 +2,7 @@
 
 This page explains the underlying concepts behind Python logging and how daqpytools builds on them. Reading this will help you understand *why* the how-to guides are structured the way they are.
 
-For hands-on instructions, see the how-to guides. For the API reference, see the [reference](https://dune-daq.github.io/daqpytools/APIref).
+For hands-on instructions, see the how-to guides. For the API reference, see the [reference](../../APIref).
 
 ---
 
@@ -128,6 +128,6 @@ For a hands on explanation of these, please read the [how-to guide on how to use
 
 ## Further reading
 
-- For how this routing model is implemented under the hood, see the [developer explanation](https://dune-daq.github.io/daqpytools/dev).
-  - The architecture reference includes diagrams which explain exactly how the routing works. See [here](https://dune-daq.github.io/daqpytools/dev/reference/architecture/).
+- For how this routing model is implemented under the hood, see the [developer explanation](../../dev/).
+  - The architecture reference includes diagrams which explain exactly how the routing works. See [here](../../dev/reference/architecture/).
 - For how to configure ERS and advanced routing in practice, see [Configuring ERS](./how-to/configure-ers.md) and [Routing messages to specific handlers](./how-to/route-messages.md).

docs/how-to/add-handlers-at-runtime.md

@@ -32,7 +32,7 @@ log.info("Now routes to rich + stdout by default")
 
 ## Suppress by default with `fallback_handler={HandlerType.Unknown}`
 
-This feature takes heavy advantage of the `extra` feature of Python logging. Please read the documentation on how `extra` is used, [found here](https://dune-daq.github.io/daqpytools/dev/explanation/).
+This feature takes heavy advantage of the `extra` feature of Python logging. Please read the documentation on how `extra` is used, [found here](../../../dev/explanation/).
 
 You can make newly-added handlers opt-in only by setting fallback handlers to `HandlerType.Unknown`. This means records without explicit `extra["handlers"]` will not be emitted by those handlers.
 

docs/how-to/configure-ers.md

@@ -2,13 +2,13 @@
 
 This page covers how to attach and use ERS (error reporting system) handlers on a logger.
 
-For background on ERS streams and routing, see [Concepts](../explanation.md). For the `LogHandlerConf` routing API, see [Routing messages to specific handlers](./route-messages.md). For the definition of the handler itself as well as how it can be used, see [How to use handlers and filters](https://dune-daq.github.io/daqpytools/dev/explanation/).
+For background on ERS streams and routing, see [Concepts](../explanation.md). For the `LogHandlerConf` routing API, see [Routing messages to specific handlers](./route-messages.md). For the definition of the handler itself as well as how it can be used, see [How to use handlers and filters](../../../dev/explanation/).
 
 ---
 
 ## Configuring ERS handlers onto a new logger (by construction)
 
-Use the `ers_kafka_session` variable to put in the relevant session name in `get_daq_logger`. There are several attributes that you can use to customise the ERS handler as well, such as changing the ERS application name as displayed on the ERS dashboards, exampled below. Please see the [API reference](https://dune-daq.github.io/daqpytools/APIref/handlers/protobufstream/) for full details on what can be passed in.  
+Use the `ers_kafka_session` variable to put in the relevant session name in `get_daq_logger`. There are several attributes that you can use to customise the ERS handler as well, such as changing the ERS application name as displayed on the ERS dashboards, exampled below. Please see the [API reference](../../../APIref/handlers/protobufstream/) for full details on what can be passed in.  
 
 ```python
     from daqpytools.logging import get_daq_logger, 

docs/how-to/use-handlers.md

@@ -4,11 +4,7 @@ This page walks through each available handler and filter in daqpytools with sho
 
 Remember that by default, any messages received by the logger will be transmitted to _all_ available handlers that are attached to the logger.
 
-**For now, please view both `get_daq_logger` and the relevant builders in `handlers.py` and `filters.py` to see what options exist on how to initialise them.**
-
-**In the future, this will be automatically generated from the docstrings.**
-
-For the full API reference (kwargs, types, defaults), see the [auto-generated reference](https://dune-daq.github.io/daqpytools/APIref).
+For the full API reference (kwargs, types, defaults), see the [auto-generated reference](../../../APIref/).
 
 ---
 

docs/index.md

@@ -22,5 +22,5 @@ This documentation is split into two sections depending on your role:
 | [How to upgrade an existing package](./how-to/upgrade-package.md) | Migration checklist for adopting daqpytools logging in existing codebases |
 | [Best practices](./how-to/best-practices.md) | Recommended patterns for structuring logging in your application |
 | [Troubleshooting](./reference/troubleshooting.md) | Common symptoms, causes, and fixes |
-| [API reference](https://dune-daq.github.io/daqpytools/APIref) | Auto-generated kwargs, types, and defaults for all public APIs (redirects to MKDocs website) |
+| [API reference](../APIref/) | Auto-generated kwargs, types, and defaults for all public APIs (redirects to MKDocs website) |
 

docs/reference/troubleshooting.md

@@ -2,7 +2,7 @@
 
 This page lists common symptoms, their likely causes, and fixes.
 
-For a systematic debugging workflow when extending the system, see the [developer debugging checklist](https://dune-daq.github.io/daqpytools/dev/how-to/debug-routing/).
+For a systematic debugging workflow when extending the system, see the [developer debugging checklist](../../../dev/how-to/debug-routing/).
 ---
 
 | Symptom | Likely cause | What to check | Fix |

docs/tutorial.md

@@ -26,7 +26,7 @@ test_logger = get_daq_logger(
 )
 ```
 
-Please see the API reference of `get_daq_logger` [here](https://dune-daq.github.io/daqpytools/APIref/get_daq_logger/), or alternatively the code itself [here](https://github.com/DUNE-DAQ/daqpytools/blob/develop/src/daqpytools/logging/logger.py), to see what options exist in initialising `get_daq_logger`. 
+Please see the API reference of `get_daq_logger` [here](../../APIref/get_daq_logger/), or alternatively the code itself [here](https://github.com/DUNE-DAQ/daqpytools/blob/develop/src/daqpytools/logging/logger.py), to see what options exist in initialising `get_daq_logger`. 
 
 This gives you a named logger with a single Rich handler attached, emitting at `INFO` level and above. Loggers in daqpytools are singletons — calling `get_daq_logger` with the same name twice will return the same instance, so it's safe to call this once at module level and reuse it throughout your code.
 
@@ -61,5 +61,5 @@ The Rich handler supports the full [Rich markup syntax](https://rich.readthedocs
   View the help string to learn more, and the script itself in the repository to see how it is implemented.
 - To understand *why* logging works the way it does, read the [Concepts & explanation](./explanation.md).
 - To learn how to use specific handlers and filters, see the [How-to guides](./how-to/use-handlers.md).
-- For a full API reference, see the [API Ref](https://dune-daq.github.io/daqpytools/APIref).
+- For a full API reference, see the [API Reference](../../APIref/).
 - If you are introducing logging to your Python repo, or upgrading an existing implementation, **please** read the [Logging best practices](./how-to/best-practices.md).

docs_dev/explanation.md

@@ -2,7 +2,7 @@
 
 This page is for developers who want to understand the internals of daqpytools logging — for example, to add a new handler or debug a routing issue.
 
-For user-facing concepts (Python logging fundamentals, streams), see the [user explanation](https://dune-daq.github.io/daqpytools/user/explanation/).
+For user-facing concepts (Python logging fundamentals, streams), see the [user explanation](../../user/explanation/).
 For implementation recipes, see the how-to guides.
 
 ---