Merge pull request #4050 from zowe/anax-v3.0-sync-branches-docs

Anax v3.0 sync branches docs

.github/workflows/build-docs.yml

@@ -36,14 +36,14 @@ jobs:
           # https://github.com/actions/checkout/issues/520#issuecomment-1320838255
           fetch-depth: 2147483647
 
-      - name: Use Node.js LTS
-        uses: actions/setup-node@v3
+      - name: Use Node.js 20
+        uses: actions/setup-node@v4
         with:
-          node-version: 18
+          node-version: 20
           cache: 'npm'
 
       - name: Cache Webpack Build
-        uses: actions/cache@v3
+        uses: actions/cache@v4
         env:
           TAR_OPTIONS: "--remove-files"
         with:
@@ -58,8 +58,8 @@ jobs:
 
       - name: Deploy to Netlify
         id: deploy
-        if: ${{ github.event_name == 'push' || github.event.pull_request.head.repo.full_name == github.repository }}
-        uses: nwtgck/actions-netlify@v2
+        if: ${{ github.event_name == 'push' || (github.event.pull_request.head.repo.full_name == github.repository && github.event.pull_request.user.login != 'dependabot[bot]') }}
+        uses: nwtgck/actions-netlify@v3
         with:
           publish-dir: build
           production-branch: master
@@ -74,13 +74,11 @@ jobs:
 
       - name: Compress Build Archive
         if: ${{ steps.deploy.conclusion == 'skipped' }}
-        run: |
-          echo "PR_NUMBER=${{ github.event.pull_request.number }}" > build/.env
-          tar --remove-files --zstd -cf build.tar.zst build
+        run: tar --label=${{ github.event.pull_request.number }} --remove-files --zstd -cf build.tar.zst build
 
       - name: Upload Build Artifact
         if: ${{ steps.deploy.conclusion == 'skipped' }}
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         with:
           name: preview-build
           path: build.tar.zst

.github/workflows/deploy-preview.yml

@@ -19,7 +19,7 @@ jobs:
     steps:
       - name: Download Build Artifact
         id: download-artifact
-        uses: dawidd6/action-download-artifact@v2
+        uses: dawidd6/action-download-artifact@v6
         with:
           workflow: build-docs.yml
           run_id: ${{ github.event.workflow_run.id }}
@@ -29,13 +29,14 @@ jobs:
       - name: Extract Build Archive
         if: ${{ steps.download-artifact.outputs.found_artifact == 'true' }}
         run: |
-          tar -xf build.tar.zst && rm build.tar.zst
-          cat build/.env >> "$GITHUB_ENV" && rm build/.env
+          tar -xf build.tar.zst
+          printf "PR_NUMBER=%d\n" "$(tar --test-label -f build.tar.zst)" >> "$GITHUB_ENV"
+          rm build.tar.zst
 
       - name: Deploy to Netlify
         id: deploy
         if: ${{ steps.download-artifact.outputs.found_artifact == 'true' }}
-        uses: nwtgck/actions-netlify@v2
+        uses: nwtgck/actions-netlify@v3
         with:
           publish-dir: build
           production-deploy: false

.github/workflows/link-checker.yml

@@ -22,7 +22,7 @@ jobs:
       - name: Create symlinks
         run: |
           find docs -name "*.md" -type f | while read f; do
-            ln -s $(basename $f) ${f%.*}
+            ln -s "$(basename "$f")" "${f%.*}"
           done
 
       - name: Restore lychee cache

.github/workflows/pr-comment-trigger.yml

@@ -25,7 +25,7 @@ jobs:
             const body = context.payload.comment.body;
             if (body.startsWith("/labels ")) {
               console.log("Comment body:", body);
-              const repoLabels = (await github.rest.issues.listLabelsForRepo(context.repo)).data.map((label) => label.name);
+              const repoLabels = (await github.rest.issues.listLabelsForRepo({ ...context.repo, per_page: 100 })).data.map((label) => label.name);
               const labelMapping = {};
               for (const label of repoLabels) {
                 if (label.includes(": ")) {

docs/appendix/zowe-api-reference.md

@@ -2,12 +2,8 @@
 
 Find and learn about the Zowe APIs that you can use.
 
-- **[REST API for the Data sets and z/OS Unix Files Services](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/zowe/docs-site/docs-staging/api_definitions/datasets.json)**
-
 - **[REST API for the API Gateway service](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/zowe/docs-site/docs-staging/api_definitions/gateway.json)**
 
-- **[REST API for the JES Jobs Service](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/zowe/docs-site/docs-staging/api_definitions/jobs.json)**
-
 - **[REST API for ZLUX Plug-in](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/zowe/docs-site/docs-staging/api_definitions/zlux-plugin.json)**
 
-- **[REST API for ZSS](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/zowe/docs-site/docs-staging/api_definitions/swagger-zss.json)**
+- **[REST API for ZLUX Plug-in](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/zowe/docs-site/docs-staging/api_definitions/zlux-plugin.json)**

docs/appendix/zowe-cli-command-reference.md

@@ -2,9 +2,10 @@
 
 View detailed documentation on commands, actions, and options in Zowe CLI. You can read an interactive online version, download a PDF document, or download a ZIP file containing the HTML for the online version.
 
-Currently, this reference documentation only contains the web help for 
-the Zowe CLI core component and CLI plug-ins maintained by Zowe. As third-party plug-ins are approved under the Zowe V2 LTS Conformance Program and contribute their web help to Zowe, we will update the documentation accordingly. To view the web help for V1 conformant plug-ins, click the version drop-menu on the top right corner of this page and click the link to any previous v1.xx.x version of this page.
+This reference documentation is organized to contain the web help for Zowe CLI, CLI plug-ins maintained by Zowe, and Zowe V3 LTS-conformant third-party CLI plug-ins. As third-party plug-ins are approved under the Zowe V3 LTS Conformance Program and contribute their web help to Zowe, we update the documentation accordingly.
 
-- <a href="/stable/web_help/index.html" target="_blank">Browse online</a>
-- <a href="/stable/CLIReference_Zowe.pdf" target="_blank">Download CLI reference in PDF format</a>
-- <a href="/stable/zowe_web_help.zip" target="_blank">Download CLI reference in ZIP format</a>
+To view the web help for V2 conformant plug-ins, click the version drop-menu on the top right corner of this page and click the link to any previous v2.xx.x version of this page.
+
+- <a href="/stable/web_help/index.html" target="_blank">Browse the interactive online version</a>
+- <a href="/stable/CLIReference_Zowe.pdf" target="_blank">Download the CLI reference guide in PDF format</a>
+- <a href="/stable/zowe_web_help.zip" target="_blank">Download the CLI reference guide in ZIP format</a>

docs/appendix/zowe-glossary.md

@@ -1,4 +1,4 @@
-# Glossary of Zowe terminology
+# Zowe glossary
 
 This glossary is part of a growing list of terms and concepts used throughout the spectrum of Zowe  projects, which includes both technical as well as organizational terms that are specific to Zowe.
 
@@ -10,7 +10,7 @@ Security is central to a wide range of functionalities in Zowe and includes nume
 For an overview of security in Zowe, see [the Zowe Security policy](https://www.zowe.org/security) on zowe.org.
 :::
 
-## Core Zowe Projects
+## All Core Zowe Projects
 
 ### Zowe API Mediation Layer (API ML)
 
@@ -47,11 +47,13 @@ Provides a command-line interface that lets you interact with the mainframe remo
 
 ### Zowe client projects
 
-Includes all the Zowe projects that are installed on the user's PC. Also known as *Zowe client-side projects*. 
+Includes all the Zowe projects, or components, that are installed on the user's PC. Also known as *Zowe client-side projects* or *Zowe client-side components*.
+
+Examples include Zowe CLI, Zowe Explorer for Visual Studio Code, Zowe Explorer for IntelliJ IDEA, and Zowe Client SDKs.
 
 ### Zowe Client SDKs
 
-Allow extenders to build applications on top of existing programmatic APIs such as z/OSMF. Currently supported client SDKs include Node.js (core), Kotlin/z/OSMF, Python, Swift, and Java.
+Allow extenders to build applications on top of existing programmatic APIs such as z/OSMF. Currently supported client SDKs include Node.js (core), Kotlin, Python, Swift, and Java.
 
 ### Zowe Explorer
 
@@ -169,9 +171,9 @@ Provides re-usable and industry-compliant JSON-formatted RMF/SMF data records so
 
 The set of programs (for example, `zwe` command) and utilities (for example, JCL, scripts) which manage the Zowe server configuration and components. The infrastructure standardizes the packaging of components and controls how they are started, stopped, and how configuration is provided to them.
 
-#### Zowe IntelliJ Plug-in
+#### Zowe Explorer plug-in for IntelliJ IDEA
 
-Uses the IntelliJ IDE to provide the ability to work with z/OS data sets and USS files, and to explore and manage JES jobs.
+Uses the IntelliJ IDEA platform IDEs to provide the ability to work with z/OS data sets, USS files, to explore and manage JES jobs and to work with TSO Console.
 
 #### Zowe Launcher
 
@@ -201,7 +203,7 @@ The Zowe Support Provider Conformance Program gives vendors the ability to showc
 
 #### Base profile
 
-A type of team configuration profile that stores connection information for use with one or more services. Your service profiles can pull information from base profiles as needed, to specify a common username and password only once.
+An object in a team configuration file that stores connection information for use with one or more services. Depending on your configuration file type, the base profile can be either a `global_base` or `project_base` profile. Your service profiles can pull information from base profiles as needed, to specify a common username and password only once, for example.
 
 The base profile can optionally store tokens to connect to Zowe API Mediation Layer, which improves security by enabling Multi-Factor Authentication (MFA) and Single Sign-on (SSO).
 
@@ -225,13 +227,17 @@ The standard z/OS Unix directory where Zowe logs are stored. It is specified in
 
 Use of z/OS UNIX services requires a z/OS UNIX security context, referred to as an OMVS segment, for the user ID associated with any unit of work requesting these services. To learn more consult [IBM Documentation](https://www.ibm.com/docs/en/zos/2.5.0?topic=profiles-omvs-segment-in-user).
 
+#### Parent profile
+
+An object in a team configuration file that groups service profiles together that share the same properties and values (for example, hostname or credentials). A parent profile makes it possible to define properties for its group of service profiles in one place rather than duplicating values throughout a configuration.
+
 #### Runtime directory
 
 The z/OS Unix directory for the [Zowe runtime](#zowe-runtime), specified in the Zowe configuration file via `zowe.runtimeDirectory`. Also the parent directory of the `zwe` command.
 
 #### Service profile
 
-A type of team configuration profile that stores connection information for a specific mainframe service, such as IBM z/OSMF. Plug-ins can introduce other service profile types, such as the CICS profile to connect to IBM CICS.
+An object in a team configuration file that stores connection information for a specific mainframe service, such as IBM z/OSMF. Plug-ins can introduce other service profile types, such as the CICS profile to connect to IBM CICS.
 
 #### SMP/E