Merge branch 'main' into issue-362-auto-extract-observeables

Author: nastasha-solomon

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

@@ -28,6 +28,6 @@ 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))
-- [Lint your API docs](guidelines.md#lint-your-api-docs) to identify and fix issues
+- [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/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 Elasticsearch quickstart](./quickstart.md#lint-your-docs) 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

@@ -3,10 +3,10 @@
 This page explains at a high-level how API docs work at Elastic today, with context on how this differs from our previous approaches and where we're heading. Use this page to understand the core primitives and workflows that apply across all Elastic teams, so you can contribute effectively.
 
 :::{tip}
-The API docs use a different system to the main Elastic docs. Refer to [Contribute to Elastic docs](../../contribute/index.md) for an overview of the two systems.
+The API docs use a different system to the main Elastic docs. Refer to [Contribute to Elastic docs](../index.md) for an overview of the two systems.
 :::
 
-While the implementation details [vary significantly across teams](workflows.md), at a high level:
+While the implementation details [vary significantly across teams](./workflows.md), at a high level:
 
 - We use [OpenAPI](https://spec.openapis.org/oas/latest.html) files to generate REST API documentation
 - Our API docs are hosted by [Bump.sh](https://bump.sh/)