update docs for separate ECR repos and releases (#884)

Updates our documentation in order to have our new ECR Public
repositories exposed in appropriate links.

Removes the "Work in Progress" user documentation navigation and
adds our install, IRSA and Authorization user docs to the navigation
sidebar.

Updates the Services matrix with the most up-to-date links and statuses.

Finally, replaces the wording in the documentation index/homepage about
"Developer Preview" and "Not to use in production" with explanation
about our release process and maintenance phases and links to the
install docs.

Issue #829 

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.

Author: jaypipes

README.md

@@ -58,20 +58,25 @@ resources on your behalf.
 
 ## Getting Started
 
-Currently, there are a set of ACK [service controllers][services] that have
-been released in a `Preview` [maintenance phase][maint-phases]. You may
-[install][install] these controllers in binary form using the Helm charts
-published on our ACK public artifact repository.
+Please see the list of ACK [service controllers][services] currently in one of
+our [project stages][proj-stages].
+
+[proj-stages]: https://aws-controllers-k8s.github.io/community/releases/#project-stages
+
+You can [install][install] any of the controllers in the `RELEASED` project stage using
+Helm (recommended) or manually using the raw Kubernetes manifests contained in
+the individual ACK service controller's source repository.
 
 [services]: https://aws-controllers-k8s.github.io/community/services/
-[maint-phases]: https://aws-controllers-k8s.github.io/community/releases#maintenance-phases
-[install]: https://aws-controllers-k8s.github.io/user-docs/install/
+[install]: https://aws-controllers-k8s.github.io/community/user-docs/install/
+
+Once installed, Kubernetes users may apply a custom resource (CR) corresponding
+to one of the resources exposed by the ACK service controller for the service.
 
-If you are comfortable building Go code yourself and working with static
-Kubernetes manifests, you are also free to [test-drive][testing] various
-controllers using our KinD-based end-to-end test suite.
+To view the list of custom resources and each CR's schema, visit our
+[reference documentation][ref-docs].
 
-[testing]: https://aws-controllers-k8s.github.io/community/dev-docs/testing/
+[ref-docs]: https://aws-controllers-k8s.github.io/community/reference/overview/
 
 ## Help & Feedback
 

docs/contents/index.md

@@ -6,13 +6,36 @@ managed services for your Kubernetes applications without needing to define
 resources outside of the cluster or run services that provide supporting
 capabilities like databases or message queues within the cluster.
 
-This is a new open source project built with ❤️ by AWS and available as a
-**Developer Preview**. We encourage you to try it out, provide feedback and
-contribute to development.
-
-*Important: Because this project is a preview, there may be significant and
-breaking changes introduced in the future. We encourage you to try and
-experiment with this project. Please do not adopt it for production use.*
+This is a fully open source project built with ❤️  by AWS. The project is
+structured as a set of source code repositories containing a
+[common runtime][rt], a [code generator][code-gen], some
+[common testing infrastructure][test-infra] and a series of individual service
+controllers that correspond to AWS services (e.g. the
+[RDS service controller for ACK][rds-controller]).
+
+[rt]: https://github.com/aws-controllers-k8s/runtime
+[code-gen]: https://github.com/aws-controllers-k8s/code-generator
+[test-infra]: https://github.com/aws-controllers-k8s/test-infra
+[rds-controller]: https://github.com/aws-controllers-k8s/rds-controller
+
+Individual ACK service controllers are installable as separate binaries either
+manually via raw manifests or via a Helm chart that corresponds to the
+individual service controller.
+
+!!! note **IMPORTANT**
+    Individual ACK service controllers may be in different
+    maintenance phases and follow separate release cadences. Please read our
+    documentation about [project stages][proj-stages] and
+    [maintenance phases][maint-phases] fully, including how we
+    [release and version][rel-ver] our controllers. Controllers in a `PREVIEW`
+    maintenance phase have at least one container image and Helm chart released to
+    an ECR Public repository. However, be aware that controllers in a `PREVIEW`
+    maintenance phase may have significant and breaking changes introduced in a
+    future release.
+
+[proj-stages]: https://aws-controllers-k8s.github.io/community/releases/#project-stages
+[maint-phases]: https://aws-controllers-k8s.github.io/community/releases/#maintenance-phases
+[rel-ver]: https://aws-controllers-k8s.github.io/community/releases/#releases-and-versioning
 
 ## Background
 
@@ -49,16 +72,30 @@ those applications depend.
 
 Read more about [how ACK works][how-it-works].
 
-[gh]: https://github.com/aws/aws-controllers-k8s/
+[gh]: https://github.com/aws-controllers-k8s/community
 [controller]: https://kubernetes.io/docs/reference/glossary/?fundamental=true#term-controller
 [crd]: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/
 [how-it-works]: https://aws-controllers-k8s.github.io/community/how-it-works/
 
 ## Getting started
 
-Until we've graduated ACK [service controllers][services] we ask you to [test-drive](https://aws-controllers-k8s.github.io/community/dev-docs/testing/) them.
+Please see the list of ACK [service controllers][services] currently in one of
+our [project stages][proj-stages].
+
+You can [install][install] any of the controllers in the `RELEASED` project stage using
+Helm (recommended) or manually using the raw Kubernetes manifests contained in
+the individual ACK service controller's source repository.
 
 [services]: https://aws-controllers-k8s.github.io/community/services/
+[install]: https://aws-controllers-k8s.github.io/community/user-docs/install/
+
+Once installed, Kubernetes users may apply a custom resource (CR) corresponding
+to one of the resources exposed by the ACK service controller for the service.
+
+To view the list of custom resources and each CR's schema, visit our
+[reference documentation][ref-docs].
+
+[ref-docs]: https://aws-controllers-k8s.github.io/community/reference/overview/
 
 ## Getting help
 

docs/contents/releases.md

@@ -134,29 +134,35 @@ This is by design, and [per the Semantic Versioning specification][semver-zero]:
 [semver-zero]: https://semver.org/#spec-item-4
 
 For ACK components that have a binary distributable -- i.e. a Docker image --
-the creation of a new SemVer Git tag on the source code repository will trigger
+the creation of a new SemVer Git tag on the source code repository triggers the
 automatic building and publishing of a Docker image with an image tag including
-the SemVer version. For example, if a Git tag of `v1.2.6` was created on the
+the SemVer version.
+
+For example, if a Git tag of `v1.2.6` was created on the
 [github.com/aws-controllers-k8s/s3-controller][s3-ctrl] repository, a Docker
-image with a tag `s3-v1.2.6` would be published to the
-[aws-controllers-k8s/controller][ecr-ack-ctrl] ECR repository.
+image with a tag `v1.2.6` would be published to the
+[public.ecr.aws/aws-controllers-k8s/s3-controller][ecr-ack-ctrl] ECR Public
+repository.
 
 [s3-ctrl]: https://github.com/aws-controllers-k8s/s3-controller
-[ecr-ack-ctrl]: https://gallery.ecr.aws/aws-controllers-k8s/controller
+[ecr-ack-ctrl]: https://gallery.ecr.aws/aws-controllers-k8s/s3-controller
 
 !!! note
-    Binaries for ACK components are published in our Amazon ECR
-    Public [registry][ecr-ack-ctrl].
+    Binaries for individual ACK service controllers components are published in
+    separate Amazon ECR Public repositories.
 
 For ACK components that have a Helm Chart distributable -- i.e. an ACK service
 controller -- the creation of a new SemVer Git tag on the source code
-repository will trigger automatic building and publishing of a Helm Chart with
-an artifact tag including the SemVer version. For example, a Git tag of
-`v1.2.6` on the [github.com/aws-controllers-k8s/s3-controller][s3-ctrl]
-repository means a Helm chart with a tag `s3-v1.2.6` would be published to the
-[aws-controllers-k8s/chart][ecr-ack-chart] ECR repository.
+repository triggers automatic building and publishing of a Helm Chart with
+an artifact tag including the SemVer version.
+
+For example, a Git tag of `v1.2.6` on the
+[github.com/aws-controllers-k8s/s3-controller][s3-ctrl]
+repository means a Helm chart with a tag `v1.2.6` would be published to the
+[public.ecr.aws/aws-controllers-k8s/s3-chart][ecr-ack-chart] ECR Public
+repository.
 
-[ecr-ack-chart]: https://gallery.ecr.aws/aws-controllers-k8s/chart
+[ecr-ack-chart]: https://gallery.ecr.aws/aws-controllers-k8s/s3-chart
 
 #### A Word About Dependencies
 
@@ -189,14 +195,16 @@ a specific version of the ACK common runtime.
 [recommend-helm]: https://aws-controllers-k8s.github.io/community/user-docs/install/#helm-recommended
 
 Some ACK service controllers will have Helm Charts with a
-`$SERVICE-v$MAJOR_VERSION-stable` tag, referred from here out as just a
+`v$MAJOR_VERSION-stable` tag, referred from here out as just a
 "`stable` artifact tag". There will only be one of these tags for the ACK
-service controller **in a major version series**. For example, the `stable`
-artifact tag for the ElastiCache ACK service controller's "v1" major version
-series would be `elasticache-v1-stable`.
+service controller **in a major version series**. For example, the full
+`stable` artifact tag for the ElastiCache ACK service controller's "v1" major
+version series would be
+`public.ecr.aws/aws-controllers-k8s/elasticache-chart:v1-stable`.
 
 This `stable` artifact tag points to a Helm chart that has configuration values
 that have been tested with a specific SemVer Docker image.
+
 Typically these tests are "soak" tests and allow the team maintaining that ACK
 controller's source code to have a high degree of confidence in the
 controller's long-running operation.
@@ -212,17 +220,17 @@ service controller may update the configuration values and associated SemVer
 Docker image tag for the controller binary to point to a newer image.
 
 For example, consider the ElastiCache ACK service controller maintainer team
-has executed a series of long-running tests of the controller image tagged with
-the `elasticache-v1.2.6` SemVer tag. The maintainer team is confident that the
-controller is stable for production use. In the `stable` Git branch of the
-ElastiCache service controller's source repository, the team would update the
-Helm Chart's Deployment, setting the
-`Deployment.spec.template.spec.containers[0].image` to
-`public.ecr.aws/aws-controllers-k8s/controller/elasticache-v1.2.6`.
+has executed a series of long-running tests of the
+`public.ecr.aws/aws-controllers-k8s/elasticache-controller` image tagged with
+the `v1.2.6` SemVer tag. The maintainer team is confident that the controller
+is stable for production use. In the `stable` Git branch of the ElastiCache
+service controller's source repository, the team would update the Helm Chart's
+Deployment, setting the `Deployment.spec.template.spec.containers[0].image` to
+`public.ecr.aws/aws-controllers-k8s/elasticache-controller:v1.2.6`.
 
 They then package the Helm Chart and publish it as an OCI Artifact to the
-`public.ecr.aws/aws-controllers-k8s/chart` registry, using an OCI artifact tag
-of `elasticache-v1-stable`.
+`public.ecr.aws/aws-controllers-k8s/elasticache-chart` registry, using an OCI
+artifact tag of `v1-stable`.
 
 A couple months later, the maintainer team has added a few minor, non-breaking
 features to their controller along with a number of bug fixes. The latest
@@ -233,10 +241,10 @@ the `v1.3.2` controller image and are confident that this release is
 appropriate for production use. The maintainer team would update the Helm Chart
 in their `stable` Git branch to have its
 `Deployment.spec.template.spec.containers[0].image` set to
-`public.ecr.aws/aws-controllers-k8s/controller/elasticache-v1.3.2`. They would
+`public.ecr.aws/aws-controllers-k8s/elasticache-controller:v1.3.2`. They would
 then package this Helm Chart and push overwrite the
-`public.ecr.aws/aws-controllers-k8s/chart:elasticache-v1-stable` OCI Artifact tag
-to point to this newly-updated Helm Chart that refers to the `v1.3.2`
+`public.ecr.aws/aws-controllers-k8s/elasticache-chart:v1-stable` OCI Artifact
+tag to point to this newly-updated Helm Chart that refers to the `v1.3.2`
 controller image.
 
 ## Maintenance Phases