docs: reorganise detector metrics out of code reference section (#1617)

Author: jmartin-tech

docs/source/detector_metrics.rst

@@ -1,5 +1,5 @@
-Detector Metrics: F1 Score and Ranking
-======================================
+Detector Quality Metrics
+========================
 
 Detectors in garak attempt to identify specific failure modes in model outputs. To assess detector performance, they must be evaluated against labeled benchmark datasets where the ground truth is known. This evaluation process measures how accurately each detector identifies its target failure mode.
 
@@ -148,6 +148,8 @@ Key Fields
 
 The primary ranking metric is ``hit_f1`` under each detector's metrics.
 
+.. _Confidence Intervals:
+
 Confidence Intervals
 --------------------
 

docs/source/index.rst

@@ -38,13 +38,11 @@ Check out the :doc:`usage` section for further information, including :doc:`inst
    configurable
    cliref
    reporting
-   translation
-   ascii_smuggling
    faster
    FAQ <https://github.com/NVIDIA/garak/blob/main/FAQ.md>
 
 .. toctree::
-   :caption: Reference
+   :caption: Code Reference
    :maxdepth: 1
    :hidden:
 
@@ -54,7 +52,6 @@ Check out the :doc:`usage` section for further information, including :doc:`inst
    cli
    command
    detectors
-   detector_metrics
    evaluators
    exception
    generators
@@ -68,6 +65,15 @@ Check out the :doc:`usage` section for further information, including :doc:`inst
    _plugins
    analyze
 
+.. toctree:: 
+   :caption: Technologies
+   :maxdepth: 1
+   :hidden:
+
+   detector_metrics
+   translation
+   ascii_smuggling
+   analyze.tbsa
 
 .. toctree::
    :caption: Extending and Contributing