Add updated production deployment guidelines

Author: wgordon17

contributing_to_docs/docs_production_deployment.adoc

@@ -0,0 +1,51 @@
+[id="contributing-to-docs-docs-production-deployment"]
+= Production deployment of the OpenShift documentation
+:icons:
+:toc: macro
+:toc-title:
+:toclevels: 1
+:linkattrs:
+:description: How to deploy the entire set of documentation
+
+toc::[]
+
+== Source-to-image pipeline
+OpenShift documentation is built and deployed on an https://cloud.redhat.com/products/dedicated/[OpenShift Dedicated cluster]
+using a https://github.com/openshift/source-to-image[source-to-image] build pipeline.
+
+The source-to-image builder image is built from a https://github.com/openshift-cs/docs-builder/[community project in GitHub]
+and published to https://quay.io/repository/openshift-cs/docs-builder.
+
+== Documentation deployment
+Deploying the OpenShift documentation is simplified by using a
+https://github.com/openshift-cs/docs-builder/blob/main/template.yaml[pre-built OpenShift template YAML].
+
+You can use the following command to deploy the OpenShift Container Platform (commercial) documentation
+
+[source,terminal]
+----
+oc new-app https://raw.githubusercontent.com/openshift-cs/docs-builder/main/template.yaml \
+    -p NAME=docs-openshift-com \
+    -p PACKAGE=commercial \
+    -p APPLICATION_DOMAIN=docs.openshift.com \
+    -p BUILD_REPO=https://github.com/openshift/openshift-docs.git \
+    -p BUILD_BRANCH=main
+----
+
+You can use the following command to deploy the OKD (community) documentation
+
+[source,terminal]
+----
+oc new-app https://raw.githubusercontent.com/openshift-cs/docs-builder/main/template.yaml \
+    -p NAME=docs-openshift-com \
+    -p PACKAGE=community \
+    -p APPLICATION_DOMAIN=docs.openshift.com \
+    -p BUILD_REPO=https://github.com/openshift/openshift-docs.git \
+    -p BUILD_BRANCH=main
+----
+
+== Deployment customization
+It's possible to change the documentation source repository to another repository for development by changing the
+`BUILD_REPO` parameter in the `oc new-app` command.
+
+To change the builder image, provide the `BUILDER_IMAGE` parameter in the `oc new-app` command.

contributing_to_docs/tools_and_setup.adoc

@@ -135,55 +135,3 @@ edit existing content or create assemblies and modules.
 some basic guidelines to keep things consistent across our content.
 * link:create_or_edit_content.adoc[Create a local working branch] on your
 workstation to edit existing content or create content.
-
-=== How to deploy to your own OpenShift cluster for testing
-
-You can deploy to your own OpenShift cluster for development. This process will use your github repo to launch the website,
-and therefore your github repo must have all of the upstream branches. `main` is used for site changes,
-so assuming all your work is in `main`, you can remove all remote branches and then push the upstream branches.
-
-
-Removing remote branches and updating with upstream branches (this assumes remote repos called `origin` and `upstream`)
-[WARNING]
-====
-This is a destructive process, make sure that this is purely a development repo, as all local and remote branches will be deleted
-by performing the below commands.
-====
-----
-$ git fetch --all
-$ for branch in $(git branch -r | grep -v "main" | grep "^  origin"); do git push origin --delete $(echo $branch | cut -d '/' -f 2); done
-$ git branch -D $(git branch | grep -v 'main' | xargs)
-$ for branch in $(git branch -r | grep -v "main" | grep "^  upstream"); do git branch --track $(echo $branch | cut -d '/' -f 2) $(echo $branch | tr -d '[:space:]'); done
-$ for branch in $(git branch | grep -v "main"); do git push origin $(echo $branch | tr -d '[:space:]'); done
-----
-
-Deploying the docs site to an OpenShift cluster
-----
-$ oc process -f asciibinder-template.yml -p NAME=community-docs \
-    -p SOURCE_REPOSITORY_URL=$(git remote get-url origin) \
-    -p SOURCE_REPOSITORY_REF=$(git rev-parse --abbrev-ref HEAD) \
-    -p DOC_TYPE=community \
-    | oc create -f -
-$ oc process -f asciibinder-template.yml -p NAME=commercial-docs \
-    -p SOURCE_REPOSITORY_URL=$(git remote get-url origin) \
-    -p SOURCE_REPOSITORY_REF=$(git rev-parse --abbrev-ref HEAD) \
-    -p DOC_TYPE=commercial \
-    | oc create -f -
-----
-
-[NOTE]
-====
-If the build fails with "Fetch source failed" status, you can
-delete all the created objects and re-run above with an HTTP uri
-as the `SOURCE_REPOSITORY_URL`, or you can
-link:https://docs.okd.io/latest/dev_guide/builds/build_inputs.html#source-secrets-combinations[create a source secret]
-and add it to the stg1 build, `oc set build-secret --source bc/stg1-docs <secret name>`.
-====
-
-
-You can delete all created objects by running
-
-----
-$ oc delete all -l app=community-docs
-$ oc delete all -l app=commercial-docs
-----