Merge pull request #4337 from vespa-engine/bratseth/organize-22-rebased

Move to 'reference/application'

Author: bratseth

_data/sidebar.yml

@@ -310,6 +310,8 @@ docs:
         url: /en/operations/zones.html
       - page: Production deployment
         url: /en/operations/production-deployment.html
+      - page: Deployment variants
+        url: /en/operations/deployment-variants.html
       - page: Automated deployments
         url: /en/operations/automated-deployments.html
       - page: Autoscaling
@@ -480,36 +482,36 @@ docs:
             url: /en/reference/vespa-cli/vespa_version.html
           - page: vespa visit
             url: /en/reference/vespa-cli/vespa_visit.html
-      - page: Application packages
-        url: /en/reference/application-packages-reference.html
-      - page: Schemas
-        url: /en/reference/schema-reference.html
-      - title: services.xml
+      - title: Applications and components
         sub:
-          - page: services.xml
-            url: /en/reference/services/services.html
-          - page: services.xml - admin
-            url: /en/reference/services/admin.html
-          - page: services.xml - container
-            url: /en/reference/services/container.html
-          - page: services.xml - content
-            url: /en/reference/services/content.html
-          - page: services.xml - docproc
-            url: /en/reference/services/docproc.html
-          - page: services.xml - http
-            url: /en/reference/services/http.html
-          - page: services.xml - processing
-            url: /en/reference/services/processing.html
-          - page: services.xml - search
-            url: /en/reference/services/search.html
-      - page: deployment.xml
-        url: /en/reference/deployment.html
-      - page: Deployment variants
-        url: /en/reference/deployment-variants.html
-      - page: hosts.xml
-        url: /en/reference/hosts.html
-      - page: validation-overrides.xml
-        url: /en/reference/validation-overrides.html
+          - page: Application packages
+            url: /en/reference/applications/application-packages.html
+          - title: services.xml
+            sub:
+              - page: services.xml
+                url: /en/reference/applications/services/services.html
+              - page: services.xml - admin
+                url: /en/reference/applications/services/admin.html
+              - page: services.xml - container
+                url: /en/reference/applications/services/container.html
+              - page: services.xml - content
+                url: /en/reference/applications/services/content.html
+              - page: services.xml - docproc
+                url: /en/reference/applications/services/docproc.html
+              - page: services.xml - http
+                url: /en/reference/applications/services/http.html
+              - page: services.xml - processing
+                url: /en/reference/applications/services/processing.html
+              - page: services.xml - search
+                url: /en/reference/applications/services/search.html
+          - page: deployment.xml
+            url: /en/reference/applications/deployment.html
+          - page: hosts.xml
+            url: /en/reference/applications/hosts.html
+          - page: validation-overrides.xml
+            url: /en/reference/applications/validation-overrides.html
+          - page: Schemas
+            url: /en/reference/applications/schemas.html
       - page: System test
         url: /en/reference/testing.html
       - page: System test (Java)
@@ -566,7 +568,7 @@ docs:
             url: /en/reference/writing/document-field-path.html
           - page: Document selector language
             url: /en/reference/writing/document-selector-language.html
-      - title: Queries and results
+      - title: Querying
         sub:
           - page: The YQL query language
             url: /en/reference/querying/yql.html

_includes/sidebar.html

@@ -35,14 +35,14 @@
             <li>
               {% if child.sub %}
                 <!-- submenu start-->
-                <details data-id="{{ child.title }}">
+                <details data-id="{{ item.title }}.{{ child.title }}">
                   <summary>{{child.title}}</summary>
                   <ul class="child">
                     {% for subchild in child.sub %}
                       <li>
                         {% if subchild.sub %}
                         <!-- sub-submenu start-->
-                        <details data-id="{{ subchild.title }}">
+                        <details data-id="{{ item.title }}.{{ child.title }}.{{ subchild.title }}">
                           <summary>{{subchild.title}}</summary>
                           <ul class="child">
                             {% for subsubchild in subchild.sub %}

en/applications/components.html

@@ -268,7 +268,7 @@ <h4 id="monitoring-the-active-application">Monitoring the active Application</h4
 <p>
   All containers also provide a built-in handler that outputs JSON formatted information about the active application,
   including its components and chains (it can also be configured to show
-  <a href="../reference/application-packages-reference.html#versioning-application-packages">a user-defined version</a>).
+  <a href="../reference/applications/application-packages.html#versioning-application-packages">a user-defined version</a>).
   The handler answers to requests with the path <code>/ApplicationStatus</code>.
   For example, if 'localhost' runs a container with HTTP configured on port 8080:
 </p>

en/applications/deployment.html

@@ -14,7 +14,7 @@ <h2 id="convergence">Convergence</h2>
 <p>After the deployment command has succeeded, the application package will take effect, but this does
 not complete immediately in the distributed system that is your running application;
 it happens through a distributed <i>convergence</i> process that you can track from the command line
-or console.  Refer to the <a href="../reference/application-packages-reference.html#deploy">deploy reference</a>
+or console.  Refer to the <a href="../reference/applications/application-packages.html#deploy">deploy reference</a>
 for detailed steps run when deploying an application.</p>
 
 <p>You can get the status of the last deployment by using the status command:</p>
@@ -90,7 +90,7 @@ <h2 id="file-distribution">File distribution</h2>
         <a href="configuring-components.html#adding-files-to-the-component-configuration">
             Adding files to the component configuration</a></li>
     <li>Machine learned models</li>
-    <li><a href="../reference/schema-reference.html#constant">Constant tensors</a></li>
+    <li><a href="../reference/applications/schemas.html#constant">Constant tensors</a></li>
 </ul>
 
 <p>When new components or files specified in config are distributed, the container gets a new file reference,

en/applications/developer-guide.html

@@ -62,7 +62,7 @@ <h2 id="performance-testing">Performance testing</h2>
 {% endhighlight %}</pre>
 <p>
   Read more in <a href="../performance/benchmarking-cloud.html">benchmarking</a> and
-  <a href="../reference/deployment-variants.html">variants in services.xml</a>.
+  <a href="../operations/deployment-variants.html">variants in services.xml</a>.
 </p>
 
 

en/applications/testing.html

@@ -131,7 +131,7 @@ <h2 id="staging-tests">Staging tests</h2>
   from what the system test would expect.
 </p>
 <p>Many such changes, which require additional action post-deployment, are also guarded by
-  <a href="../reference/validation-overrides.html">validation overrides</a>,
+  <a href="../reference/applications/validation-overrides.html">validation overrides</a>,
   but the staging test is then a great way of figuring out what the exact consequences of the change are,
   and how to deal with it.
 </p>
@@ -217,14 +217,14 @@ <h2 id="feature-switches-and-bucket-tests">Feature switches and bucket tests</h2
 <p>
   To test new behavior in Vespa, use a combination of
   <a href="chaining.html">search chains</a> and
-  <a href="../reference/schema-reference.html#rank-profile">rank profiles</a>,
+  <a href="../reference/applications/schemas.html#rank-profile">rank profiles</a>,
   controlled by <a href="../querying/query-profiles.html">query profiles</a>,
   where one query profile corresponds to one bucket.
   These features support inheritance to make it easy to express variation without repetition.
 </p>
 <p>
   Sometimes a new feature requires
-  <a href="../reference/schema-reference.html#modifying-schemas">incompatible changes to a data field</a>.
+  <a href="../reference/applications/schemas.html#modifying-schemas">incompatible changes to a data field</a>.
   To be able to CD such changes, it is necessary to create a new field containing the new version of the data.
   This costs extra resources but less than the alternative: standing up a new system copy with the new data.
   New fields can be added and populated while the system is live.

en/basics/applications.html

@@ -106,7 +106,7 @@ <h2 id="a-minimal-application-package">A minimal application package</h2>
 
 <p>To read more on schemas, see the <a href="schemas.html">schemas</a> guide.
 To see everything an application package can contain, see the
-<a href="../reference/application-packages-reference.html">application package reference</a>.</p>
+<a href="../reference/applications/application-packages.html">application package reference</a>.</p>
 
 
 <h2 id="deploying-applications">Deploying applications</h2>

en/basics/operations.html

@@ -50,7 +50,7 @@
 <ul>
   <li>Application package changes are managed by Vespa's built-in control plane to be carried out
   without impacting queries or writes. If a change can not be made without impacting queries or writes,
-  it is rejected on deployment (and will require a <a href="../reference/validation-overrides.html">validation</a>
+  it is rejected on deployment (and will require a <a href="../reference/applications/validation-overrides.html">validation</a>
     override to be allowed).
   <li>The operations supported by Vespa are those that can be scaled to hundreds of nodes, billions of
   documents and hundreds of thousands of queries per second. If you can run it on a single machine,

en/basics/querying.html

@@ -18,7 +18,7 @@ <h2 id="queries">Queries</h2>
 </pre>
 
 <p>You can also search multiple fields with one query item (like "contains"), by defining
-<a href="../reference/schema-reference.html#fieldset">fieldset</a> in the schema.</p>
+<a href="../reference/applications/schemas.html#fieldset">fieldset</a> in the schema.</p>
 
 <p>Any nested combination of and/or and so on is supported, see the full syntax in the
 <a href="../reference/querying/yql.html">query language reference</a>.</p>

en/basics/ranking.html

@@ -69,7 +69,7 @@ <h2 id="rank-profiles">Rank profiles</h2>
 <p>To avoid very long schema files, rank profiles can also be specified in their own files in the
 application package, named
 <code>schemas/[schema-name]/[profile-name].profile</code>.
-See the <a href="../reference/schema-reference.html#rank-profile">schema reference</a> for documentation
+See the <a href="../reference/applications/schemas.html#rank-profile">schema reference</a> for documentation
 of all the content of rank profiles.
 
 <p>Rank profiles can inherit other profiles to avoid duplication, as in