Merge pull request #4344 from vespa-engine/bratseth/organize-24

Bratseth/organize 24

Author: bratseth

_data/sidebar.yml

@@ -520,18 +520,6 @@ docs:
             url: /en/reference/applications/testing.html
           - page: System test (Java)
             url: /en/reference/applications/testing-java.html
-      - page: Chunking
-        url: /en/reference/chunking-reference.html
-      - page: Embedding
-        url: /en/reference/embedding-reference.html
-      - page: mTLS
-        url: /en/reference/mtls.html
-      - page: Tools
-        url: /en/reference/tools.html
-      - page: Tools (self managing)
-        url: /en/reference/tools-self-managing.html
-      - page: Health checks
-        url: /en/reference/healthchecks.html
       - title: APIs
         sub:
           - page: APIs overview
@@ -602,6 +590,24 @@ docs:
             url: /en/reference/ranking/rank-types.html
           - page: Model files
             url: /en/reference/ranking/model-files.html
+          - page: Constant tensors
+            url: /en/ranking/constant-tensor-json-format.html
+      - title: RAG and embedding
+        sub:
+          - page: Chunking
+            url: /en/reference/chunking.html
+          - page: Embedding
+            url: /en/reference/embedding.html
+      - title: Operations
+        sub:
+          - page: Health checks
+            url: /en/reference/operations/health-checks.html
+          - page: Log files
+            url: /en/reference/operations/log-files.html
+          - page: Tools
+            url: /en/reference/operations/tools.html
+          - page: Tools (self managing)
+            url: /en/reference/operations/tools-self-managing.html
       - title: Metrics
         sub:
           - page: Metrics

en/applications/bundles.html

@@ -113,10 +113,10 @@ <h2 id="building-an-osgi-bundle">Building an OSGi bundle</h2>
   Errors triggered at this stage will be the likes of
   <code>ClassNotFoundException</code> and <code>NoClassDefFoundError</code>.
   To debug these types of errors, inspect the stack traces in the
-  <a href="../reference/logs.html">error log</a>, and refer to
+  <a href="../reference/operations/log-files.html">error log</a>, and refer to
   <a href="#troubleshooting">troubleshooting</a>.
 </p><p>
-  <a href="../reference/tools-self-managing.html#vespa-logfmt">vespa-logfmt</a>
+  <a href="../reference/operations/tools-self-managing.html#vespa-logfmt">vespa-logfmt</a>
   with its <em>--nldequote</em> option is useful when reading logs.
 </p>
 <p>
@@ -674,11 +674,11 @@ <h3 id="slow-container-start">Slow Container start</h3>
   Find the container service name (here: "container"), set debug logging and restart the container:
 </p>
 <pre>
-$ <a href="../reference/tools-self-managing.html#vespa-sentinel-cmd">vespa-sentinel-cmd</a> list
+$ <a href="../reference/operations/tools-self-managing.html#vespa-sentinel-cmd">vespa-sentinel-cmd</a> list
 vespa-sentinel-cmd 'sentinel.ls' OK.
 container state=RUNNING mode=AUTO pid=246585 exitstatus=0 id="default/container.0"
 
-$ <a href="../reference/tools-self-managing.html#vespa-logctl">vespa-logctl</a> container:com.yahoo.container.di.componentgraph.core debug=on
+$ <a href="../reference/operations/tools-self-managing.html#vespa-logctl">vespa-logctl</a> container:com.yahoo.container.di.componentgraph.core debug=on
 
 $ vespa-stop-services &amp;&amp; vespa-start-services
 

en/applications/components.html

@@ -383,7 +383,7 @@ <h3 id="component-load">Component load</h3>
   Construction can fail - to debug, enable more logging (replace "container" as needed with container id):
 </p>
 <pre>
-$ <a href="../reference/tools-self-managing.html#vespa-logctl">vespa-logctl</a> container:com.yahoo.container.di.componentgraph.core.ComponentNode debug=on
+$ <a href="../reference/operations/tools-self-managing.html#vespa-logctl">vespa-logctl</a> container:com.yahoo.container.di.componentgraph.core.ComponentNode debug=on
   .com.yahoo.container.di.componentgraph.core.ComponentNode   ON  ON  ON  ON  ON  ON  ON OFF
 </pre>
 <p>

en/applications/config-system.html

@@ -334,7 +334,7 @@ <h2 id="further-reads">Further reads</h2>
         <ol>
             <li><a href="../operations/self-managed/configuration-server.html#zookeeper-recovery">
                 Delete all config server state</a> on all config servers</li>
-            <li>Run <a href="../reference/tools-self-managing.html#vespa-remove-index">
+            <li>Run <a href="../reference/operations/tools-self-managing.html#vespa-remove-index">
                 vespa-remove-index</a> to wipe content nodes</li>
         </ol>
     </li>

en/applications/configuring-components.html

@@ -144,7 +144,7 @@ <h2 id="adding-files-to-the-component-configuration">Adding files to the compone
 
 <p>
   This section describes what to do if the component needs larger configuration objects that are stored in files,
-  e.g. machine-learned models, <a href="../reference/tools.html#vespa-makefsa">automata</a> or large tables.
+  e.g. machine-learned models, <a href="../reference/operations/tools.html#vespa-makefsa">automata</a> or large tables.
   Before proceeding, take a look at how to create
   <a href="dependency-injection.html#special-components">provider components</a> &mdash;
   instead of integrating large objects into e.g. a searcher or processor, it might be better to

en/applications/containers.html

@@ -120,7 +120,7 @@ <h2 id="other-related-documents">Other related documents</h2>
     <a href="web-services.html">Designing RESTful web
       services</a> as Vespa Components
   </li><li>
-    <a href="../reference/healthchecks.html">healthchecks</a> - using the Container with a VIP
+    <a href="../reference/operations/health-checks.html">healthchecks</a> - using the Container with a VIP
   </li><li>
     <a href="../reference/applications/components.html">Vespa Component Reference</a>:
       The Container's request processing lifecycle

en/applications/deployment.html

@@ -104,7 +104,7 @@ <h2 id="deploying-remote-models">Deploying remote models</h2>
 
 <p>Most application packages are stored as source code in a code repository.
 However, some resources are generated or too large to store in a code repository,
-like models or an <a href="../reference/tools.html#vespa-makefsa">FSA</a>.</p>
+like models or an <a href="../reference/operations/tools.html#vespa-makefsa">FSA</a>.</p>
 
 <p>Machine learned models in Vespa,
 are stored in the application package under the <em>models</em> directory.

en/applications/document-processors.html

@@ -439,7 +439,7 @@ <h2 id="reconfiguring-document-processing">(Re)configuring Document Processing</
   the container must be restarted:
 </p>
 <pre>
-$ <a href="../reference/tools-self-managing.html#vespa-sentinel-cmd">vespa-sentinel-cmd</a> restart container
+$ <a href="../reference/operations/tools-self-managing.html#vespa-sentinel-cmd">vespa-sentinel-cmd</a> restart container
 </pre>
 
 

en/content/consistency.md

@@ -89,7 +89,7 @@ requested document from all divergent replicas. The client then receives the
 version with the newest timestamp.
 
 If replicas diverge during a Visit, the behavior is slightly different between
-the Document V1 API and [vespa-visit](/en/reference/tools-self-managing.html#vespa-visit):
+the Document V1 API and [vespa-visit](/en/reference/operations/tools-self-managing.html#vespa-visit):
 
   * Document V1 will prefer immediately visiting the replica that contains the
     most documents. This means it's possible for a subset of documents in a bucket

en/content/proton.html

@@ -848,7 +848,7 @@ <h2 id="state-v1-api">/state/v1 API</h2>
   This API is available at <code>http://host:stateport/state/v1/</code>.
 </p>
 <p>
-  Run <a href="../reference/tools-self-managing.html#vespa-model-inspect">vespa-model-inspect</a>
+  Run <a href="../reference/operations/tools-self-managing.html#vespa-model-inspect">vespa-model-inspect</a>
   to find the JSON HTTP stateport:
 </p>
 <pre>