Improve the product menu with contextual descriptions

[Gman0909]

Context

Context

Our Product Menu is currently a flat list of configuration options, lacking any real context. This makes it difficult for Business Development to suggest ideal configurations to customers based on their understanding of the customer's specific needs and use cases. In effect, we want the product menu to be a "cheat sheet" to our configuration options.

What we want to do

We want to re-work the product menu that is more human-readable. We can start by adding a Description column to the product menu adding cotextual descriptions to each configuration option, to provide some guidance as to why someone would choose any option versus another, to help BD have those conversations and reduce the need for someone from P&S to follow up with the customer for further clarification.

We can also re-format the whole product menu as a new document with features structured by Outcome/Value rather than technical area (e.g. Make, Read, Access, Monitor, Manage, Share).

For example, the descriptions should allow anyone browsing the menu to understand

• why someone would choose GitHub Auth vs CILogon,
• What's in a Julia Notebook vs, Rocker with RStudio, and which types of communities would want to use them
• What each of the different home storage options mean and why someone might choose one over another.

Definition of Done

• Each feature in the product menu has a contextual description explaining what it is and why it should be used.

[Gman0909]

@jmunroe and I discussed this and feel this should be made a sub issue of #1962

[Gman0909]

@jmunroe do you still feel the above comment holds true?

[jmunroe]

I think so. I've add it as a subissue of the Interactive Computing service design intiative

[Gman0909]

I feel that this can be deprecated now we have the web configurator with clearer questions for each feature. Closing.