doc for ZRS binary on PATH

[anaxceron]

Describe your pull request here: Adding doc on how to add ZRS binary to your PATH

List the file(s) included in this PR:

• docs\getting-started\ze-configuring-zowe-remote-ssh.md
• sidebars.js

After creating the PR, follow the instructions in the comments.

[github-actions]

😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these steps.

• Add the label review: sme if an SME needs to check your content.
• Identify your content topic with a label. (Examples: area: apiml, area: cli, area: install and config, etc.)
• Specify the major Zowe release(s) for your content. (Examples: release: V1, release: V2, release: V3)
  • If adding content that needs to be removed from V3 documentation, add the V3 N/A tag.
• Link any Doc Issues related to this PR.
• Fix broken links found in your content areas.
• Notify the SME to review this PR (if applicable).
• Merge to the master branch if your PR updates content that is on the live site. Merge to docs-staging if your PR updates content for a future release.

[github-actions]

🚀 Deployed on https://6a63ac1c7cac9a6e09505bf9--zowe-docs-master.netlify.app

[CBforZ]

Suggested change

	#### Editing the JSON file
	#### Editing the VS Code Configuration JSON file

[traeok]

Thanks for working on this Ana! I'm requesting changes around a missing verb, and I left a suggestion around ordering for the new sections.

[traeok]

Sentence "The path..." is missing a verb

Suggested change

	If you have not yet configured a server path, you are prompted for a path to deploy the server. The path saved in the `zowe.zowex.serverInstallPath` key in the VS Code `settings.json` file.
	If you have not yet configured a server path, you are prompted for a path to deploy the server. The path is saved in the `zowe.zowex.serverInstallPath` key in the VS Code `settings.json` file.

[traeok]

Suggested change

	If you have not yet configured a server path, you are prompted for a path to deploy the server. The path saved in the `zowe.zowex.serverInstallPath` key in the VS Code `settings.json` file.
	If you have not yet configured a server path, you are prompted for a path to deploy the server. The path is saved in the `zowe.zowex.serverInstallPath` key in the VS Code `settings.json` file.

[traeok]

I noticed this section was inserted before ## Configuration methods, which is what explains how/where the zowex binary gets deployed. Step 2 mentions to point $PATH at the "directory where the zowex binary was deployed," which may confuse a reader if they are deploying their own instance (and not a shared one).

Thoughts on moving this section after "Configuration methods" or adding an explicit line about the deploy path being defined?

[anaxceron]

Happy to relocate this to where it makes the most sense OR to add some context and not relocate content. Looking for the team to provide direction on this.

[traeok]

Personally, I'm in favor of moving it after the "Configuration methods" section, but open to other ideas 😋

[CBforZ]

Not 100% sure about before or after, since part of the point of the $PATH detection feature is for Zowe Explorer to find an instance of zowex on the $PATH if it has been deployed outside of Zowe Explorer (like manually extracting a pax file, or it was deployed in the past and the config for the server path was somehow deleted, we could detect it automatically on the $PATH).

If we put this after the sections about auto-deploying with Zowe Explorer, then folks might trigger an auto deploy first, then realize they should follow instructions for using a shared instance based on their site setup .

Maybe we can keep it where it is and further clarify the context of how zowex might be deployed? Like that you would add it to your $PATH before using Zowe Explorer to connect if you know you have a shared instance, and otherwise allow VS Code to deploy it

[traeok]

That's fair, plus I don't want that section to get glossed/skipped over either by being further down in the article. I think as long as we provide some clarity or use cases for why a user would pursue adding to PATH, they know to skip over the section if these pre-requisites do not apply to them

[anaxceron]

@traeok @CBforZ - Shifted some things around in an effort to add context earlier on about when/why a user would want to pursue the $PATH stuff. Lmk if that works or not.