Create a glossary for odo terminology

[yhontyk]

[kind/Documentation]

What did you find missing in the documentation?

Since we have feedback on odo being confusing sometimes, how about adding a glossary in "Understanding odo" which would elaborate on the important terms and explain the relationship/hierarchy between them as well as examples:

• project
• application
• component
• something else?

Maybe a visual representation - a diagram of some sorts could help?

Cc @kadel @cdrage @dharmit

What is the relevance of it?

Make docs better!

[dharmit]

+1 to having glossary. I remember asking @kadel about what a 'component' means during my initial days in the team and irrespective of how much he tried, I just couldn't understand the concept completely. Eventually I accepted it as something abstract. A group of things forming up a component. Even then, it used to confuse me if a URL should be a part of the umbrella that makes up a component or not.

+100 to having a visual representation or an architecture diagram for various things that make up odo.

[kadel]

diagram https://drive.google.com/file/d/1iNSZjEfNY5mdOcfBMGUR-mYaFdDZL85l/view?usp=sharing

[girishramnani]

@boczkowska @pmacko1 could you please add an update on this issue?

[ghost]

I was not working on this issue, @boczkowska could you provide an update, please?

[yhontyk]

Done here: openshift/openshift-docs#18477

[girishramnani]

As the PR was merged, we can close this issues