(#279) - Reorganise info between Building and Deployment pages.

Author: ccarouge

documentation/docs/pages/infrastructure/Building.md

@@ -1,22 +1,9 @@
 # Build infrastructure
 
-Most users of ACCESS-ESM1.6 will not need to build the model. Released versions of the model are deployed by ACCESS-NRI to Gadi and available to users. If you require your own build of the model, typically because you need to modify one or several model components, you will find the required information on this page.
+Most users of ACCESS-ESM1.6 will not need to build the model. Released versions of the model are deployed by ACCESS-NRI to Gadi and available to users. If you require your own build of the model, typically because you need to modify one or several model components, you will find the required information on this page. For more information on the available deployed builds, check the [Deployment](/documentation/docs/pages/infrastructure/Deployment.md) page. 
 
 ACCESS-NRI is using [Spack](https://spack.io/), a build from source package manager designed for use with high performance computing. Spack already contains support for compiling thousands of common software packages. 
 
-## Existing deployments
-
-ACCESS-ESM1.6 releases come with a pre-deployed executable on Gadi. Deployed builds are stored under the project `vk83` (hence requiring [membership to this project](https://my.nci.org.au/mancini/project/vk83/join) for access). You can see all deployed builds via:
-
-```bash
-module use /g/data/vk83/modules
-module avail access-esm1p6
-```
-
-There are development releases (identified with a `dev_` prefix to the date tag) and full releases (identified with only a date tag). We recommend new users start with the newest full release (i.e. with the most recent date tag). 
-
-These builds are optimised for the Sapphire-Rapid hardware from Intel (i.e., the *normalsr* queue), and may not run on Cascade-Lake (i.e., the *normal* queue) or older hardware.
-
 ## Software structure
 
 ACCESS-ESM1.6 being a Earth System model, it is constituted of several model components, each residing in its own repository on GitHub. In addition, some model components need other utilities at compilation time that are stored in separate repositories. This results in a complex software structure involving a large number of repositories:

documentation/docs/pages/infrastructure/Deployment.md

@@ -1,20 +1,29 @@
 # Deployment
 
-ACCESS-ESM1.6 is deployed automatically when a new version of the spack.yaml file is committed to the `main` branch or a dedicated `backport/VERSION` branch of the [ACCESS-NRI/ACCESS-ESM1.6](https://github.com/ACCESS-NRI/ACCESS-ESM1.6) repository. 
+All released versions of ACCESS-ESM1.6 come with a pre-deployed build on _Gadi_. Deployed builds are stored under the project `vk83` (hence requiring [membership to this project](https://my.nci.org.au/mancini/project/vk83/join) for access). You can see all deployed builds via:
 
-ACCESS-ESM1.6 is deploed in /g/data/vk83. It is necessary to be a member of vk83 project to use ACCESS-NRI deployments of ACCESS-ESM1.6. All deployed versions are available as modules to load. To check all the released versions of ACCESS-ESM1.6 on Gadi:
-
-```
+```bash
 module use /g/data/vk83/modules
 module avail access-esm1p6
 ```
 
-For users of ACCESS-ESM1.6 model configurations released by ACCESS-NRI, the exact location of the ACCESS-ESM1.6 model executables is not required. Model configurations will be updated with new model releases when necessary.
+There are development releases (identified with a `dev_` prefix to the date tag) and full releases (identified with only a date tag). We recommend new users start with the newest full release (i.e. with the most recent date tag). 
+
+These builds are optimised for the Sapphire-Rapid hardware from Intel (i.e., the *normalsr* queue), and may not run on Cascade-Lake (i.e., the *normal* queue) or older hardware.
+
+The ACCESS-ESM1.6 model configurations released by ACCESS-NRI are setup to use the proper model release and will be updated when necessary.
+
 
 ## Release information
 
 The deployment process creates a GitHub release with the same tag as the deployed module. All releases are available under the [Releases page](https://github.com/ACCESS-NRI/ACCESS-ESM1.6/releases). Each release has a changelog and meta-data with detailed information about the build and deployment, including:
 
 - paths on Gadi to all executables built in the deployment process (spack.location)
 - a spack.lock file, which is a complete build provenance document, listing all the components that were built and their dependencies, versions, compiler version, build flags and build architecture
-- the environment spack.yaml file used for deployment
+- the environment spack.yaml file used for deployment
+
+## More details
+
+The deployment is managed via GitHub Actions that are triggered when a new version of the spack.yaml file is committed to the `main` branch or a dedicated `backport/VERSION` branch of the [ACCESS-NRI/ACCESS-ESM1.6](https://github.com/ACCESS-NRI/ACCESS-ESM1.6) repository. 
+
+No manual deployments will be accepted.