Clarify entity types and terminology in UI

[annavik]

After processing some of the user feedback, it seems to be some confusions around the entity types and also the terminology in some cases. For example, what defines a "deployment"? What is a "site"? What does a "collection" include?

To prevent this, I suggest we include some clarifications in the UI here. To not disturb seasoned users with information, I suggest we show this information on demand, for example using tooltips. We could show a short description and also include a link to more detailed information, when we have a wiki?

[joseepoirier]

Agree that the terminology causes confusion for users. We started defining some of the terms in the specs + manuals we're writing, but that to me feels like a bandaid that doesn't address the cause.

Should we consider a 3-step in-app tutorial for the public launch?

[annavik]

Here are some quick code sketches I made for a streamlined "entity header" where we can include such clarifications:

[annavik]

Also this header can be place for other "entity actions", such as create? Andre can probably refine this a bit though!

[annavik]

Agree that the terminology causes confusion for users. We started defining some of the terms in the specs + manuals we're writing, but that to me feels like a bandaid that doesn't address the cause.

Should we consider a 3-step in-app tutorial for the public launch?

Yes I agree just explanations is probably not enough in some cases. We might want to rethink some concepts and also introduce abstractions (for example for collections used in jobs?), but I suggest we keep this specific task about the clarifications only, to avoid it getting too large :)

[annavik]

Waiting on design spec here, blocked for now.