Merge branch 'main' into azure-price-change-nov-2025

Author: demers-eric

.github/CODEOWNERS

@@ -9,7 +9,20 @@
 # The docs
 /cloud-account/                             @elastic/admin-docs
 /deploy-manage/                             @elastic/admin-docs
+
 /explore-analyze/                           @elastic/core-docs @elastic/experience-docs
+/explore-analyze/alerts-cases/              @elastic/experience-docs
+/explore-analyze/dashboards/                @elastic/experience-docs
+/explore-analyze/discover/                  @elastic/experience-docs
+/explore-analyze/elastic-inference/         @elastic/developer-docs @elastic/experience-docs
+/explore-analyze/find-and-organize/         @elastic/experience-docs
+/explore-analyze/machine-learning/          @elastic/developer-docs @elastic/experience-docs
+/explore-analyze/query-filter/              @elastic/developer-docs @elastic/experience-docs
+/explore-analyze/report-and-share/          @elastic/experience-docs
+/explore-analyze/scripting/                 @elastic/admin-docs
+/explore-analyze/transforms/                @elastic/developer-docs
+/explore-analyze/visualize/                 @elastic/experience-docs
+
 /extend/                                    @elastic/core-docs
 /get-started/                               @elastic/core-docs @elastic/project-docs
 
@@ -64,7 +77,7 @@
 /troubleshoot/security/                     @elastic/ski-docs
 
 # Raw migrated files
-/raw-migrated-files/                        @elastic/docs
+/raw-migrated-files/                        @elastic/admin-docs
 
 # Legacy serverless docs
 /serverless/                                @elastic/admin-docs

.vscode/extensions.json

@@ -0,0 +1,5 @@
+{
+  "recommendations": [
+    "Elastic.elastic-docs-v3-utilities"
+  ]
+}

cloud-account/index.md

@@ -9,6 +9,9 @@ applies_to:
 products:
   - id: cloud-hosted
   - id: cloud-serverless
+description: Manage your Elastic Cloud account settings, including email, password,
+  authentication methods, and personal preferences. Configure your user profile
+  and customize your interface.
 ---
 
 # Manage your Cloud account and preferences

extend/contribute/api-docs/checklist.md renamed to contribute-docs/api-docs/checklist.md

@@ -27,7 +27,7 @@ Use this checklist to verify the quality, completeness, and consistency of your
 
 ## Quality assurance
 
-- Preview your changes locally before submitting (see [Contribute locally: Elasticsearch quickstart](./quickstart.md))
+- Preview your changes locally before submitting (see [Quickstarts](./quickstart.md))
 - [Lint your API docs](guidelines.md#lint-your-api-docs) to identify and fix issues
 - Check all links to ensure they work correctly
 - Ensure examples are realistic and error-free

extend/contribute/api-docs/quickstart.md renamed to contribute-docs/api-docs/elasticsearch-api-docs-quickstart.md

@@ -1,23 +1,29 @@
 ---
-navigation_title: Contribute locally (Elasticsearch)
+navigation_title: Elasticsearch API docs
 ---
 
-# Contribute locally: Elasticsearch quickstart
+# Contribute to Elasticsearch API docs locally
+
+## Overview
 
 The Elasticsearch APIs are the foundation of the Elastic Stack and the largest API set we maintain. Because the workflow is quite complex, we created this quickstart guide to help you get started.
 
 This is a step-by-step local development workflow. While CI runs these steps automatically on PR branches in the `elasticsearch-specification` repo (see [Makefile](https://github.com/elastic/elasticsearch-specification/blob/main/Makefile)), working locally enables you to validate, preview and debug before submitting your changes. For a complete list of available make targets, run `make help`.
 
 For the official Elasticsearch specification contribution guidance, see [`CONTRIBUTING.md`](https://github.com/elastic/elasticsearch-specification/blob/main/CONTRIBUTING.md#contributing-to-the-elasticsearch-specification).
 
+## Quickstart
+
+Follow these steps to contribute to Elasticsearch API docs locally:
+
 :::::{stepper}
 
 ::::{step} Prepare your environment
 
 Run this command to set up your Node.js environment:
 
 ```shell
-nvm use 
+nvm use
 ```
 If you don't have Node.js installed, refer to the [setup guide](https://github.com/elastic/elasticsearch-specification/tree/main?tab=readme-ov-file#prepare-the-environment).
 ::::
@@ -78,6 +84,15 @@ The `transform-to-openapi` command (run by `make contrib`) is used for client li
 :::
 ::::
 
+::::{step} Apply overlays
+
+[OpenAPI overlays](https://github.com/OAI/Overlay-Specification?tab=readme-ov-file#overlay-specification) are used to handle publisher-specific requirements or work around rendering limitations. For example, they sort the list of tags alphabetically and apply `x-model` extensions to abbreviate deeply nested/recursive schema objects.
+
+```shell
+make overlay-docs
+```
+::::
+
 ::::{step} Lint your docs
 
 Run this command to lint your docs-specific OpenAPI files:
@@ -89,14 +104,6 @@ You should try to fix all linter warnings and not just errors. Fixing errors alo
 :::
 ::::
 
-::::{step} Apply overlays
-
-[OpenAPI overlays](https://github.com/OAI/Overlay-Specification?tab=readme-ov-file#overlay-specification) are used to handle publisher-specific requirements or work around rendering limitations. For example, they sort the list of tags alphabetically and apply `x-model` extensions to abbreviate deeply nested/recursive schema objects.
-
-```shell
-make overlay-docs
-```
-
 ::::{step} Preview your changes
 Generate a preview of how your docs will appear:
 ```shell
@@ -115,4 +122,4 @@ Once you're satisfied with your docs changes:
 3. Once approved, merge your changes and ensure they are backported to the appropriate branches
 ::::
 
-:::::
+:::::

extend/contribute/api-docs/guidelines.md renamed to contribute-docs/api-docs/guidelines.md

@@ -510,7 +510,7 @@ paths:
 :::{tab-item} Elasticsearch
 :sync: elasticsearch
 
-**External documentation links** use the `@ext_doc_id` annotation to connect to narrative guides. This is transformed into an OpenAPI `externalDocs` field in the [compilation process](overview.md#example-elasticsearch):
+**External documentation links** use the `@ext_doc_id` annotation to connect to narrative guides. This is transformed into an OpenAPI `externalDocs` field in the [compilation process](./overview.md#example-elasticsearch):
 
 ```ts
 /**
@@ -621,7 +621,7 @@ The [Elasticsearch API specification](https://github.com/elastic/elasticsearch-s
 - **Spectral**: Configuration in `.spectral.yaml`
 - **Redocly**: Configuration in `redocly.yaml`
 
-Refer to [the Elasticsearch quickstart](quickstart.md#lint-your-docs) to learn how to run the linter locally.
+Refer to [the quickstarts](quickstart.md) to learn how to run the linter locally.
 
 ::::
 ::::

extend/contribute/api-docs/help.md renamed to contribute-docs/api-docs/help.md

@@ -2,15 +2,15 @@
 
 The API docs workflow is pretty complicated, and there's lots of moving parts. It takes a village to produce excellent API docs, so don't hesitate to ask for help if you get stuck or have questions.
 
-If you're not sure who owns a specific API, check out the [API ownership table](workflows.md) to find the right team.
+If you're not sure who owns a specific API, check out the [API ownership table](./workflows.md) to find the right team.
 
 ## Report issues
 
 ### API docs issues
 
 When you find a bug or gap in the API docs:
 
-- If you're comfortable making the change, open a PR in the [relevant repo](workflows.md)
+- If you're comfortable making the change, open a PR in the [relevant repo](./workflows.md)
 - Alternatively, open an issue in either:
    -  [elastic/docs-content](https://www.github.com/elastic/docs-content/issues) (public repo)
    - [elastic/docs-content-internal](https://www.github.com/elastic/docs-content-internal/issues) (Elastic employees only)

extend/contribute/api-docs/images/api-docs-general-pipeline.png renamed to contribute-docs/api-docs/images/api-docs-general-pipeline.png

@@ -14,7 +14,7 @@ Learn how to contribute to Elastic's Open API docs across our various product re
 
 4. [**Organize and annotate**](./organize-annotate.md) - Learn how to group your APIs using tags and how to signal lifecycle status, deployment-type availability, and required permissions.
 
-5. [**Contribute locally: Elasticsearch**](./quickstart.md) - Follow a step-by-step guide to contribute to Elasticsearch API docs, including environment setup, local development workflow, and preview generation.
+5. [**Quickstarts: {{es}} and {{kib}}**](./quickstart.md) - Follow step-by-step guides to contribute to {{es}} and {{kib}} API docs, including environment setup, local development workflow, and preview generation.
 
 6. [**Find your workflow**](./workflows.md) - Find the workflow for the specific Elastic API docs you're interested in and learn how the OpenAPI docs are generated, validated, and published.