documentation updates (#818)

*  updated readme to list references for 3.5.3 and 4.0.0 documentation  (#808)

* updated to list references for 3.5.3 and 4.0.0 documentation

* removed extra space and dash for bullet point

* README wording (#809)

* cleaning up wording to point users to particular sections of the documentation.

* updated link and hugo theme (#811)


* fixed link to Ansible install, updated hugo theme

* updated getting started and internal links (#812)

* updated links to point directly to current release version

* update link to 4.0.0 (#813)

* updated link

* removed hard coded links as links will be generated via hugo generation (#814)

* updated how to get Ansible roles (#815)

* updated how to get Ansible roles

*  updating location for pgo client binaries.  (#817)

* updating location for pgo client binaries.

Author: cahoonpwork

README.md

@@ -25,23 +25,52 @@ The Operator is validated for deployment on Kubernetes, OpenShift, and VMware En
 
 The Operator includes various components that get deployed to your
 Kubernetes cluster as shown in the following diagram and detailed
-in the [Design](https://crunchydata.github.io/postgres-operator/stable/design/).
+in the Design section of the documentation for the version you are running.
 
-![Reference](https://crunchydata.github.io/postgres-operator/stable/Operator-Architecture.png)
+![Reference](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/Operator-Architecture.png)
 
 The Operator is developed and tested on CentOS and RHEL linux platforms but is known to run on other Linux variants.
 
-## Documentation
-
- - [Getting Started](https://crunchydata.github.io/postgres-operator/stable/gettingstarted/)
- - [pgo CLI Syntax and Examples](https://crunchydata.github.io/postgres-operator/stable/operator-cli/)
- - [Installation](https://crunchydata.github.io/postgres-operator/stable/installation/)
- - [Configuration](https://crunchydata.github.io/postgres-operator/stable/configuration/configuration/)
- - [pgo.yaml Description](https://crunchydata.github.io/postgres-operator/stable/configuration/pgo-yaml-configuration/)
- - [Security](https://crunchydata.github.io/postgres-operator/stable/security/)
- - [Design](https://crunchydata.github.io/postgres-operator/stable/design/)
- - [Developing](https://crunchydata.github.io/postgres-operator/stable/developer-setup/)
- - [Upgrading the Operator](https://crunchydata.github.io/postgres-operator/stable/upgrade/)
+## Documentation 4.0.0
+
+If you are new to the Crunchy PostgreSQL Operator and interested in installing the Crunchy PostgreSQL Operator in your environment, please start here:
+ - [Installation via Bash](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/installation/operator-install/)
+ - [Installation via Ansible](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/installation/install-with-ansible/)
+
+If you have the Crunchy PostgreSQL Operator installed in your environment, and are interested in installation of the client interface, please start here:
+[PGO Client Install](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/installation/install-pgo-client/)
+
+If you have the Crunchy PostgreSQL and Client Interface installed in your environment and are interested in guidance on the use of the Crunchy PostgreSQL Operator, please start here: 
+- [PGO CLI Overview](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/operatorcli/pgo-overview/)
+
+Want to contribute to the product find more info here:
+ - [Developer Setup](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/installation/developer-setup/)
+   - Development for the 4.0 code base is on the develop branch.
+ - GitHub issues and Pull Request information
+   - [Submitting Issues](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/contributing/issues/)
+   - [Submitting Pull Request](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/contributing/pull-requests/)
+
+## Documentation 3.5.3
+
+If you are new to the Crunchy PostgreSQL Operator and interested in installing the Crunchy PostgreSQL Operator in your environment, please start here:
+ - [Installation via Bash](https://access.crunchydata.com/documentation/postgres-operator/3.5.3/installation/)
+
+If you have the Crunchy PostgreSQL Operator installed in your environment, and are interested in installation of the client interface, please start here:
+[PGO Client Install](https://access.crunchydata.com/documentation/postgres-operator/3.5.3/installation/#pgo-cli-installation)
+
+If you have the Crunchy PostgreSQL and Client Interface installed in your environment and are interested in guidance on the use of the Crunchy PostgreSQL Operator, please start here: 
+- [PGO CLI Overview](https://access.crunchydata.com/documentation/postgres-operator/3.5.3/operator-cli/)
+
+Want to contribute to the product find more info here:
+ - [Developer Setup](https://access.crunchydata.com/documentation/postgres-operator/3.5.3/developer-setup/)
+   - Development on 3.5 codebase is on the develop-3.5 branch.
+ - GitHub issues and Pull Request information
+   - [Submitting Issues](https://access.crunchydata.com/documentation/postgres-operator/3.5.3/contributing/issues/)
+   - [Submitting Pull Request](https://access.crunchydata.com/documentation/postgres-operator/3.5.3/contributing/pull-requests/)
+
+
+
+Documentation for previous releases can be found at the [Crunchy Data Access Portal](https://access.crunchydata.com/documentation)
 
 
 If you are looking for the latest documentation, please see the develop branch which is considered unstable. The development

hugo/content/Installation/install-pgo-client/_index.md

@@ -33,7 +33,7 @@ The following will setup the `pgo` client to be used on a Windows system.
 ### Installing the Client
 
 First, download the `pgo.exe` client from the
-[GitHub official releases](https://github.com/CrunchyData/postgres-operator/releases).
+[GitHub official releases](https://github.com/CrunchyData/postgres-operator/releases). Crunchy Enterprise Customers can download the pgo binaries from https://access.crunchydata.com/ on the downloads page. 
 
 Next, install `pgo` in `/usr/local/bin` by running the following:
 

hugo/content/Installation/install-with-ansible/_index.md

@@ -8,7 +8,7 @@ weight: 1
 # Crunchy Data PostgreSQL Operator Playbooks
 
 The Crunchy Data PostgreSQL Operator Playbooks contain [Ansible](https://www.ansible.com/) 
-roles for installing and managing the [Crunchy Data PostgreSQL Operator](https://crunchydata.github.io/postgres-operator/stable/).  
+roles for installing and managing the [Crunchy Data PostgreSQL Operator](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/installation/install-with-ansible/).  
 
 ## Features
 

hugo/content/Installation/install-with-ansible/prerequisites.md

@@ -44,40 +44,16 @@ can install:
 
 ## Obtaining Operator Ansible Role
 
-There are two ways to obtain the Crunchy PostgreSQL Operator Roles:
+The Crunchy PostgreSQL Operator Roles are available here:
+
+* Clone the [postgres-operator project](https://github.com/CrunchyData/postgres-operator)
 
-* Cloning the [postgres-operator project](https://github.com/CrunchyData/postgres-operator)
-* `postgres-operator-playbooks` RPM provided for Crunchy customers via the [Crunchy Access Portal](https://access.crunchydata.com/).
 
 ### GitHub Installation
 
 All necessary files (inventory, main playbook and roles) can be found in the `ansible` 
 directory in the  [postgres-operator project](https://github.com/CrunchyData/postgres-operator).
 
-### RPM Installation using Yum
-
-Available to Crunchy customers is an RPM containing all the necessary Ansible roles 
-and files required for installation using Ansible.  The RPM can be found in Crunchy's 
-yum repository.  For information on setting up `yum` to use the Crunchy repoistory, 
-see the [Crunchy Access Portal](https://access.crunchydata.com/).
-
-To install the Crunchy PostgreSQL Operator Ansible roles using `yum`, run the following 
-command on a RHEL or CentOS host:
-
-```bash
-sudo yum install postgres-operator-playbooks
-```
-
-* Ansible roles can be found in: `/usr/share/ansible/roles/crunchydata`
-* Ansible playbooks/inventory files can be found in: `/usr/share/ansible/postgres-operator/playbooks`
-
-Once installed users should take a copy of the `inventory` file included in the installation 
-using the following command:
-
-```bash
-cp /usr/share/ansible/postgres-operator/playbooks/inventory ${HOME?}
-```
-
 ## Configuring the Inventory File
 
 The `inventory` file included with the PostgreSQL Operator Playbooks allows installers 
@@ -217,7 +193,7 @@ database in a new PostgreSQL cluster is provisioned in the same zone as the node
 containing the PostgreSQL primary pod that will be using it.
 
 For instructions on setting up storage classes for multi-zone environments, see 
-the [PostgreSQL Operator Documentation](https://crunchydata.github.io/postgres-operator/stable/design/).
+the [PostgreSQL Operator Documentation](/gettingstarted/design/designoverview/).
 
 ### Examples
 

hugo/content/Installation/operator-install.md

@@ -14,8 +14,7 @@ A full installation of the Operator includes the following steps:
  - deploy the operator
  - install pgo CLI (end user command tool)
 
-Operator end-users are only required to install the pgo CLI client on their host and can skip the server-side installation steps.  pgo CLI clients are provided
-on the Github Releases page for Linux, Mac, and Windows clients.
+Operator end-users are only required to install the pgo CLI client on their host and can skip the server-side installation steps.  pgo CLI clients are provided for Linux, Mac, and Windows clients.
 
 The Operator can be deployed by multiple methods including:
 
@@ -240,7 +239,7 @@ created previously.
 
 
 ## pgo CLI Installation
-Most users will work with the Operator using the *pgo* CLI tool.  That tool is downloaded from the GitHub Releases page for the Operator (https://github.com/crunchydata/postgres-operator/releases).
+Most users will work with the Operator using the *pgo* CLI tool.  That tool is downloaded from the GitHub Releases page for the Operator (https://github.com/crunchydata/postgres-operator/releases). Crunchy Enterprise Customer can download the pgo binaries from https://access.crunchydata.com/ on the downloads page. 
 
 The *pgo* client is provided in Mac, Windows, and Linux binary formats, 
 download the appropriate client to your local laptop or workstation to work 

hugo/content/contributing/documentation-updates.md

@@ -7,8 +7,7 @@ weight: 901
 
 ## Documentation
 
-The [documentation website](https://access.crunchydata.com/documentation/postgres-operator/3.5.0/) is generated using [Hugo](https://gohugo.io/) and
-https://pages.github.com/)[GitHub Pages]().
+The [documentation website](/) is generated using [Hugo](https://gohugo.io/).
 
 ## Hosting Hugo Locally (Optional)
 

hugo/content/gettingstarted/_index.md

@@ -5,46 +5,12 @@ draft: false
 weight: 2
 ---
 
-Operator users typically will just need to install the *pgo* client
-in order to work with an already deployed Postgres Operator.
+If you are new to the Crunchy PostgreSQL Operator and interested in installing the Crunchy PostgreSQL Operator in your environment, please start here:
+ - [Installation via Bash](/installation/operator-install/)
+ - [Installation via Ansible](/installation/install-with-ansible/)
 
-For installing the Operator on the Kubernetes server, see
-the [Installation Guide](https://crunchydata.github.io/postgres-operator/stable/installation/).
+If you have the Crunchy PostgreSQL Operator installed in your environment, and are interested in installation of the client interface, please start here:
+- [PGO Client Install](/installation/install-pgo-client/)
 
-### pgo Client Installation
-
-The *pgo* binary is pre-compiled and available to download from the projects
-github repository [Releases](https://github.com/crunchydata/postgres-operator)  page.
-
-Add the *pgo* binary to your PATH and make it executable.
-
-Next, create a *.pgouser* file in your $HOME directory or 
-set the PGOUSER environment variable to point to a *.pgouser*
-file location:
-
-    export PGOUSER=/somepath/.pgouser
-
-Alternatively, if you create a *.pgouser* file in your $HOME, the *pgo*
-client will find the file there.
-
-Set the name of the Kubernetes namespace that you want to 
-access, on a Linux host you would enter:
-
-    export PGO_NAMESPACE=pgouser1
-
-Set the URL of the Operator REST API, in this example the Operator is running 
-on a host with IP address 192.168.0.120, see your administrator for
-the correct IP address, on a Linux host you would enter:
-
-    export PGO_APISERVER_URL=https://192.168.0.120:8443
-
-Next, add the TLS keys required for the *pgo* client to connect to the
-Operator REST API, see your administrator for access to these keys, on a Linux host you would enter:
-
-    export PGO_CA_CERT=/somepath/someserver.crt
-    export PGO_CLIENT_CERT=/somepath/someserver.crt
-    export PGO_CLIENT_KEY=/somepath/someserver.key
-
-Lastly, test out the connection:
-
-    pgo version
+If you have the Crunchy PostgreSQL and Client Interface installed in your environment and are interested in guidance on the use of the Crunchy PostgreSQL Operator, please start here: 
+- [PGO CLI Overview](/operatorcli/pgo-overview/)

hugo/content/operatorcli/pgo-overview.md

@@ -386,7 +386,7 @@ into your Postgres cluster pod as follows:
 Note: backend metric storage such as Prometheus and front end 
 visualization software such as Grafana are not created automatically 
 by the PostgreSQL Operator.  For instructions on installing Grafana and 
-Prometheus in your environment, see the [Crunchy Container Suite documentation](http://crunchydata.github.io/crunchy-containers/stable/examples/metrics/metrics/).
+Prometheus in your environment, see the [Crunchy Container Suite documentation](https://access.crunchydata.com/documentation/crunchy-containers/2.4.0/examples/metrics/metrics/).
 
 ### Scheduled Tasks