improve user experience for onboarding to container schema #396
Description
(WIP to pull out next steps)
Below is a user's journey during usability testing.
I'm trying to go find information about whether the container resource lets you specify things like memory and scaling.
Based on the Table of Contents, I'll guess Developer Guides > Resources.
Ummm what do I do with this section? I guess of all these categories, container seems closest to "Services."
Oh ok, yep, that was correct. But you hadn't told me containers are services yet. They've been mostly called containers in the Concepts pages.
And why are you forcing users to have an extra step in their learning ("What is a Service Type?") when there's only one service type?
And now I wonder, "Is a Radius container different than a container?"
Ok on the container page I finally found the link to the schema
It seems like the phrase "More information" is actually important info.
It would've been nice if the app overview in Concepts linked out to this page, e.g. "follow this link to get more info about how you define this resource." Get people to the schema page faster.
- It's spec by example, it's not even the full spec. So I don't know if you've included all possible options or just a couple ones in the example. I'd rather see pseudo schema - "this is the top level of key things that make up an app, not with real values, so I can quickly wrap my head around the Radius container and map it to what I already know.
- An example pseudo-schema I like is here:
So back on the container main page why is the example first? The first experience should help them understand the important parts of what's possible with a container. Then, I also want a link to the schema details right next to it. "e.g. how do I set managedStore?" I want to solve for both.