Test run of new docs

api-extractor.json

@@ -0,0 +1,39 @@
+{
+  "$schema": "https://developer.microsoft.com/json-schemas/api-extractor/v7/api-extractor.schema.json",
+  "mainEntryPointFilePath": "<projectFolder>/lib/client.d.ts",
+  "bundledPackages": [
+    "@elastic/*"
+  ],
+  "apiReport": {
+    "enabled": false
+  },
+  "docModel": {
+    "enabled": true,
+    "apiJsonFilePath": "<projectFolder>/api-extractor/<unscopedPackageName>.api.json",
+    "includeForgottenExports": true
+  },
+  "dtsRollup": {
+    "enabled": false
+  },
+  "tsdocMetadata": {
+    "enabled": true,
+    "tsdocMetadataFilePath": "<projectFolder>/api-extractor/tsdoc-metadata.json"
+  },
+  "messages": {
+    "compilerMessageReporting": {
+      "default": {
+        "logLevel": "warning"
+      }
+    },
+    "extractorMessageReporting": {
+      "default": {
+        "logLevel": "warning"
+      }
+    },
+    "tsdocMessageReporting": {
+      "default": {
+        "logLevel": "warning"
+      }
+    }
+  }
+}

docs/basic-config.asciidoc

@@ -85,7 +85,7 @@ _Default:_ `3`
 _Default:_ `30000`
 
 |`pingTimeout`
-|`number` - Max ping request timeout in milliseconds for each request. +
+|`number` - Max number of milliseconds a `ClusterConnectionPool` will wait when pinging nodes before marking them dead. +
 _Default:_ `3000`
 
 |`sniffInterval`
@@ -105,17 +105,13 @@ _Default:_ `'_nodes/_all/http'`
 _Default:_ `false`
 
 |`resurrectStrategy`
-|`string` - Configure the node resurrection strategy. +
+|`string` - Strategy for resurrecting dead nodes when using `ClusterConnectionPool`. 'ping' will issue a test request to a node and resurrect it if it responds. 'optimistic' marks a node as alive without testing it. 'none' will never attempt to revive a dead connection. +
 _Options:_ `'ping'`, `'optimistic'`, `'none'` +
 _Default:_ `'ping'`
 
-|`suggestCompression`
-|`boolean` - Adds `accept-encoding` header to every request. +
-_Default:_ `false`
-
 |`compression`
 |`string, boolean` - Enables gzip request body compression. +
-_Options:_ `'gzip'`, `false` +
+_Options:_ `true`, `false` +
 _Default:_ `false`
 
 |`tls`

docs/changelog.asciidoc

@@ -118,8 +118,7 @@ https://www.elastic.co/guide/en/elasticsearch/reference/8.15/release-notes-8.15.
 ===== OpenTelemetry zero-code instrumentation support
 
 For those that use an observability service that supports OpenTelemetry spans, the client will now automatically generate traces for each Elasticsearch request it makes.
-See {jsclient}/observability.html#_opentelemetry[the docs]
-for more information.
+See <<o11y-otel,the docs>> for more information.
 
 [discrete]
 === 8.14.1
@@ -329,7 +328,7 @@ https://www.elastic.co/guide/en/elasticsearch/reference/8.9/release-notes-8.9.0.
 [discrete]
 ===== Allow document to be overwritten in `onDocument` iteratee of bulk helper https://github.com/elastic/elasticsearch-js/pull/1732[#1732]
 
-In the {jsclient}/client-helpers.html#bulk-helper[bulk helper], documents could not be modified before being sent to Elasticsearch. It is now possible to {jsclient}/client-helpers.html#_modifying_a_document_before_operation[modify a document] before sending it.
+In the <<bulk-helper,bulk helper>>, documents could not be modified before being sent to Elasticsearch. It is now possible to <<bulk-modify-doc,modify a document>> before sending it.
 
 [discrete]
 ==== Fixes

docs/examples/bulk.asciidoc

@@ -1,10 +1,10 @@
 [[bulk_examples]]
 === Bulk
 
-With the {jsclient}/api-reference.html#_bulk[`bulk` API], you can perform multiple index/delete operations in a 
+With the <<client.bulk,`bulk` API>>, you can perform multiple index/delete operations in a
 single API call. The `bulk` API significantly increases indexing speed.
 
-NOTE: You can also use the {jsclient}/client-helpers.html[bulk helper].
+NOTE: You can also use the <<bulk-helper,bulk helper>>.
 
 [source,js]
 ----

docs/examples/scroll.asciidoc

@@ -1,25 +1,25 @@
 [[scroll_examples]]
 === Scroll
 
-While a search request returns a single “page” of results, the scroll API can be 
-used to retrieve large numbers of results (or even all results) from a single 
-search request, in much the same way as you would use a cursor on a traditional 
+While a search request returns a single “page” of results, the scroll API can be
+used to retrieve large numbers of results (or even all results) from a single
+search request, in much the same way as you would use a cursor on a traditional
 database.
 
-Scrolling is not intended for real time user requests, but rather for processing 
-large amounts of data, for example in order to reindex the contents of one index 
+Scrolling is not intended for real time user requests, but rather for processing
+large amounts of data, for example in order to reindex the contents of one index
 into a new index with a different configuration.
 
-NOTE: The results that are returned from a scroll request reflect the state of 
-the index at the time that the initial search request was made, like a snapshot 
-in time. Subsequent changes to documents (index, update or delete) will only 
+NOTE: The results that are returned from a scroll request reflect the state of
+the index at the time that the initial search request was made, like a snapshot
+in time. Subsequent changes to documents (index, update or delete) will only
 affect later search requests.
 
-In order to use scrolling, the initial search request should specify the scroll 
-parameter in the query string, which tells {es} how long it should keep the 
+In order to use scrolling, the initial search request should specify the scroll
+parameter in the query string, which tells {es} how long it should keep the
 “search context” alive.
 
-NOTE: Did you know that we provide an helper for sending scroll requests? You can find it {jsclient}/client-helpers.html[here].
+NOTE: Did you know that we provide an helper for sending scroll requests? You can find it <<scroll-search-helper,here>>.
 
 [source,js]
 ----
@@ -113,7 +113,7 @@ async function run () {
 run().catch(console.log)
 ----
 
-Another cool usage of the `scroll` API can be done with Node.js ≥ 10, by using 
+Another cool usage of the `scroll` API can be done with Node.js ≥ 10, by using
 async iteration!
 
 [source,js]

docs/helpers.asciidoc

@@ -338,6 +338,7 @@ console.log(result)
 ----
 
 [discrete]
+[[bulk-modify-doc]]
 ==== Modifying a document before operation
 
 ~Added~ ~in~ ~`v8.8.2`~

docs/index.asciidoc

@@ -1,8 +1,5 @@
 = Elasticsearch JavaScript Client
 
-include::{asciidoc-dir}/../../shared/versions/stack/{source_branch}.asciidoc[]
-include::{asciidoc-dir}/../../shared/attributes.asciidoc[]
-
 include::introduction.asciidoc[]
 include::getting-started.asciidoc[]
 include::changelog.asciidoc[]
@@ -17,8 +14,7 @@ include::integrations.asciidoc[]
 include::observability.asciidoc[]
 include::transport.asciidoc[]
 include::typescript.asciidoc[]
-include::reference.asciidoc[]
+include::reference/main.asciidoc[]
 include::examples/index.asciidoc[]
 include::helpers.asciidoc[]
-include::redirects.asciidoc[]
 include::timeout-best-practices.asciidoc[]

docs/observability.asciidoc

@@ -16,6 +16,7 @@ features.
 All of these observability features are documented below.
 
 [discrete]
+[[o11y-otel]]
 ==== OpenTelemetry
 
 The client supports OpenTelemetry's https://opentelemetry.io/docs/zero-code/js/[zero-code