Update Codeowners, Issues, and Project automation

.github/CODEOWNERS

@@ -1,5 +1,65 @@
-/.github/ @elastic/doc-leads
-/.github/workflows/ @elastic/docs-engineering
+# Unless a later match takes precedence, someone on the docs team must review all PRs to this repo
+*                                           @elastic/docs
 
-/serverless/ @elastic/platform-docs
-/serverless/serverless-changelog.asciidoc @elastic/docs
+# Templates, workflows, and config
+/.github/                                   @elastic/doc-leads
+/.github/workflows/                         @elastic/docs-engineering
+/acrolinx/                                  @elastic/doc-leads
+
+# The docs
+/cloud-account/                             @elastic/admin-docs
+/deploy-manage/                             @elastic/admin-docs
+/explore-analyze/                           @elastic/core-docs @elastic/experience-docs 
+/extend/                                    @elastic/core-docs
+/get-started/                               @elastic/core-docs
+
+/manage-data/                               @elastic/admin-docs
+/manage-data/data-store/                    @elastic/admin-docs @elastic/developer-docs 
+/manage-data/ingest/                        @elastic/ingest-docs
+
+/reference/                                 @elastic/docs
+/reference/apm-agents/                      @elastic/ingest-docs
+/reference/data-analysis/                   @elastic/docs
+/reference/data-analysis/observability/     @elastic/experience-docs
+/reference/data-analysis/kibana/            @elastic/experience-docs 
+/reference/data-analysis/machine-learning/  @elastic/developer-docs
+/reference/data-analysis/observability/     @elastic/experience-docs
+/reference/elasticsearch/clients/           @elastic/developer-docs
+/reference/fleet/                           @elastic/ingest-docs
+/reference/glossary/                        @elastic/docs
+/reference/ingestion-tools/                 @elastic/ingest-docs
+/reference/observability/                   @elastic/experience-docs
+/reference/search/                          @elastic/developer-docs
+/reference/security/                        @elastic/experience-docs
+
+/release-notes/                             @elastic/docs
+
+/release-notes/apm-agents/                  @elastic/ingest-docs
+/release-notes/elastic-cloud-serverless/    @elastic/admin-docs
+/release-notes/elastic-observability/       @elastic/ski-docs
+/release-notes/elastic-security/            @elastic/ski-docs
+/release-notes/elasticsearch-clients/       @elastic/developer-docs
+/release-notes/fleet-elastic-agent/         @elastic/ingest-docs
+/release-notes/intro/                       @elastic/docs
+
+/solutions/                                 @elastic/experience-docs @elastic/developer-docs 
+/solutions/observability/                   @elastic/experience-docs
+/solutions/observability/get-started/       @elastic/ski-docs
+/solutions/search/                          @elastic/developer-docs
+/solutions/security/                        @elastic/experience-docs
+
+/troubleshoot/                              @elastic/docs
+/troubleshoot/deployments/                  @elastic/admin-docs
+/troubleshoot/elasticsearch/                @elastic/admin-docs
+/troubleshoot/ingest/                       @elastic/ingest-docs
+/troubleshoot/kibana/                       @elastic/admin-docs @elastic/experience-docs 
+/troubleshoot/monitoring/                   @elastic/admin-docs @elastic/experience-docs
+/troubleshoot/observability/                @elastic/ski-docs
+/troubleshoot/security/                     @elastic/ski-docs
+
+# Raw migrated files
+/raw-migrated-files/                        @elastic/docs
+
+# Legacy serverless docs
+/serverless/                                @elastic/admin-docs
+/serverless/serverless-changelog.asciidoc   @elastic/docs

.github/ISSUE_TEMPLATE/community-request.yaml → .github/ISSUE_TEMPLATE/a-community-request.yaml

@@ -1,14 +1,14 @@
 name: "Community documentation request"
-description: Request a documentation change or enhancement.
-title: "[Request]: "
-labels: ["Request", "community"]
+description: An issue template for non-Elastic employees to request changes to the documentation.
+title: "[Community]: "
+labels: ["community"]
 body:
   - type: markdown
     attributes:
       value: |
-        Hi 👋. Thanks for taking the time to fill out this request!
-        This form will create an issue that Elastic's docs team will triage and prioritize.
-        You can also open a PR instead.
+        This issue template is for non-Elastic employees to request changes to the documentation. **If you are an Elastic employee, please use the internal issue template instead.**
+
+        This form will create an issue that Elastic's docs team will triage and prioritize. You can also open a PR instead. Thanks for taking the time to fill out this request!
   - type: textarea
     id: link
     attributes:

.github/ISSUE_TEMPLATE/internal-request.yaml → .github/ISSUE_TEMPLATE/b-internal-request.yaml

@@ -1,7 +1,6 @@
 name: "Internal documentation request (Elastic employees)"
-description: Request a documentation change or enhancement for any supported release.
-title: "[REQUEST]: "
-labels: ["request", "Team:Docs"]
+description: An issue template for Elastic employees to request improvements, additions, or changes to the documentation.
+title: "[Internal]: "
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/api-feedback.yaml → .github/ISSUE_TEMPLATE/c-api-feedback.yaml

@@ -1,7 +1,7 @@
 name: "API docs feedback"
 description: Tell us about your experience with Elastic API documentation.
-title: "[Feedback]: "
-labels: ["feedback", "community"]
+title: "[API]: "
+labels: ["api-feedback"]
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/issue-report.yaml → .github/ISSUE_TEMPLATE/z-issue-report.yaml

@@ -1,14 +1,12 @@
-name: "Docs issue"
-description: Report documentation issues such as inaccuracies, broken links, typos, or missing information.
-title: "[Issue]: "
-labels: ["triage"]
+name: "Website issue"
+description: This issue template should only be used when navigating directly from elastic.co.
+title: "[Website]: "
+labels: ["source:web"]
 body:
   - type: markdown
     attributes:
       value: |
-        Hi 👋. Thanks for taking the time to fill out this issue report!
-        This form will create an issue that Elastic's docs team will triage and prioritize.
-        You can also open a PR instead.
+        Hi 👋. Thanks for taking the time to fill out this issue report! This form will create an issue that Elastic's docs team will triage and prioritize. You can also open a PR instead.
   - type: dropdown
     attributes:
       label: Type of issue

.github/workflows/add-to-board.yml

@@ -12,6 +12,10 @@ jobs:
   route:
     runs-on: ubuntu-latest
     if: |
+      github.event.label.name == 'team:Ingest' ||
+      github.event.label.name == 'team:Experience' ||
+      github.event.label.name == 'team:Admin' ||
+      github.event.label.name == 'team:Developer' ||
       github.event.label.name == 'team:DocsEng' ||
       github.event.label.name == 'team:Obs' ||
       github.event.label.name == 'team:Platform' ||
@@ -21,12 +25,16 @@ jobs:
     env:
       PROJECT_ID_MAP: |
         {
-          "team:DocsEng":   "1625",
-          "team:Obs":       "649",
-          "team:Platform":  "1232",
-          "team:Projects":  "1415",
-          "team:Search":    "726",
-          "team:Security":  "1034"
+          "team:Ingest":      "649",
+          "team:Experience":  "1034",
+          "team:Admin":       "1927",
+          "team:Developer":   "726",
+          "team:DocsEng":     "1625",
+          "team:Obs":         "649",
+          "team:Platform":    "1232",
+          "team:Projects":    "1415",
+          "team:Search":      "726",
+          "team:Security":    "1034"
         }
     steps:
       - name: Remove needs-team label