Organize Core & Tooling documentation

We don't sync the sitemap, so I removed all the strip tags.

PiperOrigin-RevId: 454226597
Change-Id: Ibb1ad248713180f71fdd0051c0a04a929fd540af

diff --git a/docs/build_infrastructure.md b/docs/build_infrastructure.md
deleted file mode 100644
index 4408353..0000000
--- a/docs/build_infrastructure.md
+++ /dev/null

@@ -1,30 +0,0 @@
-# Build infrastructure
-
-<!--*
-# Document freshness: For more information, see go/fresh-source.
-freshness: { owner: 'aurimas' reviewed: '2022-05-05' }
-*-->
-
-[TOC]
-
-## Build invocation scripts
-
-AndroidX uses
-[`busytown/`](https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:busytown/)
-directory to wrap build bot invocations to a single command per build target.
-Each one of these scripts receives `DIST_DIR`, `OUT_DIR`, and `CHANGE_INFO`
-enviroment variables. `DIST_DIR` is a directory for putting build artifacts that
-should be saved. `OUT_DIR` is a directory to write temporary build outputs.
-`CHANGE_INFO` points to a file that allows build system to know what changed for
-a given change that is being built.
-
-## Gradle Remote Build Cache
-
-AndroidX build bots use the
-[Gradle Remote Build Cache](https://docs.gradle.org/current/userguide/build_cache.html)
-to speed up build targets. We
-[configure](https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:buildSrc/remoteBuildCache.gradle;drc=dd99f75742c18a499110b979c7c25bf822113e3e;l=49)
-the
-[GCP build cache Gradle plugin](https://github.com/androidx/gcp-gradle-build-cache)
-to connect to the GCP Storage bucket `androidx-gradle-remote-cache` in the
-`androidx-ge` project.

diff --git a/docs/gradle_enterprise.md b/docs/gradle_enterprise.md
deleted file mode 100644
index 19cd12d..0000000
--- a/docs/gradle_enterprise.md
+++ /dev/null

@@ -1,19 +0,0 @@
-# Gradle Enterprise
-
-<!--* freshness: { owner: 'rahulrav' reviewed: '2022-05-02' } *-->
-
-[TOC]
-
-## Introduction
-
-Gradle Enterprise is used to speed up workflows that use GitHub actions for
-[playground](playground.md) projects.
-
-The Gradle Enterprise Server is running on AWS (`us-east-1`). This service is
-running on a Kubernetes cluster and can serve HTTP2 traffic. This service is
-managed by the Gradle team.
-
-The `FQHN` for the service is `hosted-ge-androidx.gradle.com` (port `443`).
-
-Note: The service will always use a `Location` header `ge.androidx.dev`. That is
-the only `hostname` it deems valid for a request origin.

diff --git a/docs/index.md b/docs/index.md
index 426fea4..b63faee 100644
--- a/docs/index.md
+++ b/docs/index.md

@@ -26,38 +26,6 @@
 2018, was the last feature release in the `android.support` package. There will
 be no further releases under Support Library packaging.
 
-## Team Purpose
-
-Enable high-quality libraries so that app developers can succeed.
-
-## Team mission
-
-Define, enforce, and enable a high quality bar that provides best-in-class
-library development workflow for Jetpack libraries.
-
-## Team Values
-
--   Communication (open, honest, constructive)
-    -   Discussing issues in public (e.g. chat)
-    -   Providing a safe space to give/receive feedback
-    -   Documenting and sharing knowledge
--   User Focus (meeting/exceeding our customer's needs and desires)
-    -   Listening to users, seeking out feedback
-    -   Taking user feedback seriously
-    -   Showing empathy for users
--   Quality (strive for excellence, continuous improvement)
-    -   Prioritizing quality over velocity
-    -   Building long-lasting solutions
-    -   Following consistent, codified principles
--   Integrity (honesty, sincerity, standing up for one’s beliefs)
-    -   Owning mistakes
-    -   Respecting others
-    -   Raising concerns when you have them!
--   Responsibility (accountability)
-    -   Monitoring and maintaining our products
-    -   Providing clear ownership and escalation paths
-    -   Following up to ensure resolution of issues
-
 ## Quick links
 
 ### Filing an issue

diff --git a/docs/team.md b/docs/team.md
new file mode 100644
index 0000000..0c61aa4b
--- /dev/null
+++ b/docs/team.md

@@ -0,0 +1,47 @@
+# Core & Tooling Team
+
+go/androidx/team
+
+<!--*
+# Document freshness: For more information, see go/fresh-source.
+freshness: { owner: 'alanv' reviewed: '2022-06-10' }
+*-->
+
+## What we do
+
+The AndroidX Core & Tooling team is responsible for the overall library
+development and release workflows, including defining and enforcing policies,
+owning the tools used for docs generation and API tracking, and ensuring the
+stability and performance of the build and test systems.
+
+## Team purpose
+
+Enable high-quality libraries so that app developers can succeed.
+
+## Team mission
+
+Define, enforce, and enable a high quality bar that provides best-in-class
+library development workflow for Jetpack libraries.
+
+## Team values
+
+-   Communication (open, honest, constructive)
+    -   Discussing issues in public (e.g. chat)
+    -   Providing a safe space to give/receive feedback
+    -   Documenting and sharing knowledge
+-   User Focus (meeting/exceeding our customer's needs and desires)
+    -   Listening to users, seeking out feedback
+    -   Taking user feedback seriously
+    -   Showing empathy for users
+-   Quality (strive for excellence, continuous improvement)
+    -   Prioritizing quality over velocity
+    -   Building long-lasting solutions
+    -   Following consistent, codified principles
+-   Integrity (honesty, sincerity, standing up for one’s beliefs)
+    -   Owning mistakes
+    -   Respecting others
+    -   Raising concerns when you have them!
+-   Responsibility (accountability)
+    -   Monitoring and maintaining our products
+    -   Providing clear ownership and escalation paths
+    -   Following up to ensure resolution of issues