Synchronize documentation

Author: rjeberhard

documentation/3.4/content/_index.md

@@ -10,8 +10,8 @@ You can:
 * Deploy an operator that manages all WebLogic domains in all namespaces in a Kubernetes cluster, or that only manages domains in a specific subset of the namespaces, or that manages only domains that are located in the same namespace as the operator. At most, a namespace can be managed by one operator.
 * Supply WebLogic domain configuration using:
   * _Domain in PV_: Locates WebLogic domain homes in a Kubernetes PersistentVolume (PV). This PV can reside in an NFS file system or other Kubernetes volume types.
-  * _Domain in Image_: Includes a WebLogic domain home in a container image.
-  * _Model in Image_: Includes [WebLogic Deploy Tooling](https://oracle.github.io/weblogic-deploy-tooling/) models and archives in a container image.
+  * _Domain in Image_: Includes a WebLogic domain home in an image.
+  * _Model in Image_: Includes [WebLogic Deploy Tooling](https://oracle.github.io/weblogic-deploy-tooling/) models and archives in an image.
 * Configure deployment of WebLogic domains as a Kubernetes resource (using a Kubernetes custom resource definition).
 * Override certain aspects of the WebLogic domain configuration; for example, use a different database password for different deployments.
 * Start and stop servers and clusters in the domain based on declarative startup parameters and desired states.
@@ -31,7 +31,7 @@ using the operator to deploy and run a WebLogic domain container-packaged web ap
 #### Current production release
 
 The [current release of the operator](https://github.com/oracle/weblogic-kubernetes-operator/releases) is {{< latestVersion >}}.
-This release was published on February 18, 2022. See the [operator prerequisites]({{< relref "/userguide/prerequisites/introduction.md" >}}) and [supported environments]({{< relref "/userguide/platforms/environments.md" >}}).
+This release was published on April 21, 2022. See the [operator prerequisites]({{< relref "/userguide/prerequisites/introduction.md" >}}) and [supported environments]({{< relref "/userguide/platforms/environments.md" >}}).
 
 ***
 

documentation/3.4/content/developerguide/_index.md

@@ -2,11 +2,9 @@
 title = "Developer Guide"
 date = 2019-02-22T15:27:54-05:00
 weight = 7
-chapter = true
 pre = "<b> </b>"
 +++
 
-
-# Developer Guide
-
 The Developer Guide provides information for developers who want to understand or contribute to the code.
+
+{{% children style="h4" description="true" %}}

documentation/3.4/content/developerguide/asynchronous-call-model.md

@@ -2,6 +2,7 @@
 title: "Asynchronous call model"
 date: 2019-02-23T17:20:00-05:00
 draft: false
+description: "The operator employs an efficient, user-level threads pattern to implement an asynchronous call model for Kubernetes API requests."
 weight: 7
 ---
 

documentation/3.4/content/developerguide/backwards-compatibility.md

@@ -2,6 +2,7 @@
 title: "Backward compatibility"
 date: 2019-02-23T17:26:09-05:00
 draft: false
+description: "Review the operator's backward compatibility and maintenance."
 weight: 9
 ---
 

documentation/3.4/content/developerguide/branching.md

@@ -2,6 +2,7 @@
 title: "Branching"
 date: 2019-02-23T17:19:29-05:00
 draft: false
+description: "Understand the operator repository branching strategy."
 weight: 4
 ---
 
@@ -11,6 +12,6 @@ Because we want to balance separating destabilizing work into feature branches a
 
 All commits to `main` must pass the [integration test suite]({{< relref "/developerguide/integration-tests.md" >}}).  Please run these tests locally before submitting a pull request.  Additionally, each push to a branch in our GitHub repository triggers a run of a subset of the integration tests with the results visible [here](http://build.weblogick8s.org:8080/job/weblogic-kubernetes-operator-quicktest/).
 
-Please submit pull requests to the `main` branch unless you are collaborating on a feature and have another target branch.  Please see details on the Oracle Contributor Agreement (OCA) and guidelines for pull requests in [Contribute to the operator]({{< relref "/developerguide/contributing#contributing-to-the-oracle-weblogic-server-kubernetes-operator-repository" >}}).
+Please submit pull requests to the `main` branch unless you are collaborating on a feature and have another target branch.  Please see details on the Oracle Contributor Agreement (OCA) and guidelines for pull requests in [Contribute to the operator]({{< relref "/developerguide/contributing#contributing-to-the-weblogic-kubernetes-operator-repository" >}}).
 
 We will create git tags for each release candidate and generally available (GA) release of the operator.

documentation/3.4/content/developerguide/building.md

@@ -2,6 +2,7 @@
 title: "Building"
 date: 2019-02-23T17:19:24-05:00
 draft: false
+description: "Learn about the operator build process."
 weight: 3
 ---
 
@@ -32,7 +33,7 @@ We recommend that you use a tag other than `latest`, to make it easy to distingu
 
 #### Running the operator from an IDE
 
-The operator can be run from an IDE, which is useful for debugging.  In order to do so, the machine running the IDE must be configured with a Kubernetes configuration file in `~/.kube/config` or in a location pointed to by the `KUBECONFIG` environment variable.
+The operator can be run from an IDE, which is useful for debugging.  To do so, the machine running the IDE must be configured with a Kubernetes configuration file in `~/.kube/config` or in a location pointed to by the `KUBECONFIG` environment variable.
 
 Configure the IDE to run the class `oracle.kubernetes.operator.Main`.
 

documentation/3.4/content/developerguide/code-structure.md

@@ -2,6 +2,7 @@
 title: "Code structure"
 date: 2019-02-23T17:25:04-05:00
 draft: false
+description: "Review the project directory structure."
 weight: 6
 ---
 
@@ -11,7 +12,7 @@ This project has the following directory structure:
 * `documentation/<numbered directory>`: The archived documentation for a previous release
 * `documentation/charts`: Helm chart repository
 * `documentation/swagger`: The operator REST API swagger
-* `documentation/domains`: Reference for Domain resource schema 
+* `documentation/domains`: Reference for Domain resource schema
 * `json-schema-generator`: Java model to JSON schema generator
 * `json-schema-maven-plugin`: Maven plugin for schema generator
 * `kubernetes/charts`: Helm charts

documentation/3.4/content/developerguide/coding-standards.md

@@ -2,13 +2,14 @@
 title: "Coding standards"
 date: 2019-02-23T17:24:10-05:00
 draft: false
+description: "Review the project coding standards."
 weight: 5
 ---
 
 
 This project has adopted the following coding standards:
 
-* Code will be formated using Oracle / WebLogic standards, which are identical to the [Google Java Style](https://google.github.io/styleguide/javaguide.html).
+* Code should be formatted using Oracle / WebLogic standards, which are identical to the [Google Java Style](https://google.github.io/styleguide/javaguide.html).
 * Javadoc must be provided for all public packages, classes, and methods, and must include all parameters and returns.  Javadoc is not required for methods that override or implement methods that are already documented.
 * All non-trivial methods should include `LOGGER.entering()` and `LOGGER.exiting()` calls.
 * The `LOGGER.exiting()` call should include the value that is going to be returned from the method, unless that value includes a credential or other sensitive information.

documentation/3.4/content/developerguide/contributing.md

@@ -2,6 +2,7 @@
 title: "Contribute to the operator"
 date: 2019-02-23T17:19:19-05:00
 draft: false
+description: "Learn how to contribute to the operator project."
 weight: 1
 ---
 

documentation/3.4/content/developerguide/documentation.md

@@ -2,6 +2,7 @@
 title: "Documentation"
 date: 2019-03-19T07:13:22-04:00
 draft: false
+description: "Learn how to contribute to the operator documentation."
 weight: 9
 ---