Introduce Use-Case oriented Install & Configuration

[RASakach]

Zowe Consumers struggle with understanding which components of Zowe need to be installed and configured for their specific use of Zowe and as a result, the implementation takes longer and can be more complicated than necessary. Several Vendors have introduced Products and Solutions that require Zowe as a prerequisite. When their consumers (installers) are directed to Zowe docs, they have no idea what they need to install and why.

Examples include:

• Desktop apps that require Zowe do not need any Zowe Client technology, how does the installer know this?
• Consumers interested in leveraging either of the Zowe Explorers (VSC or IntelliJ) in conjunction with a modern IDE, do not need to install the Zowe Desktop / WEB UI
• Vendor solutions that leverage the Zowe API ML, do not need to install the Desktop OR any of the Zowe Clients

How can we help Zowe consumers to quickly and concisely understand what needs to be installed and configured so that they can get Zowe up-and-running for their specific use case?