Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the installation diagrams #704

Open
1 task done
fharper opened this issue May 21, 2024 · 0 comments
Open
1 task done

Update the installation diagrams #704

fharper opened this issue May 21, 2024 · 0 comments
Assignees
Labels
P1 - Important Needed for our users to be able to properly use our product. wrong Some information in the documentation is wrong

Comments

@fharper
Copy link
Contributor

fharper commented May 21, 2024

What type of suggestions?

Wrong Information

What page is concerned?

No response

What version of the docs?

2.4+

What is the issue?

We have an opportunity to update the installation diagram. Here are the results of our discussions on Slack including all points from @johndietz & myself:

  1. Update the Argo Workflow logo: right now it's the Argo project logo in black to make an unclear distinction from Argo CD.
  2. Make a GitOps repository logo that represents it better than what we have right now with the mash-up of Argo CD + Terraform + Git. We could use this in all our diagrams.
  3. Update the cloud logos for their colored versions (some are colored, some are just white).
  4. Get rid of the star-ish thing on arrows where there is a text next to them. It was a Kubeshop thing, but we want those diagrams to be simplified.
  5. Remove background on technology logos (some have none, some have black ones).
  6. Add the Metaphor logo when it's missing. If it's there, replace with the one including the text "Metaphor" since it's an unknown logo, and cannot be easily recognized.
  7. Add Crossplane logo.
  8. Add vcluster logo.
  9. Add kubefirst console or a better representation of cluster management (point from @johndietz, discussion will need to be done to clarify the need and design solution)
  10. Align the diagrams from the dark and light theme versions (see the first video below).
  11. Standardize how we use technology logo. As a first one, with or without names/text. Example, the GitHub logo is used with the text "GitHub", but not the GitLab one (see the second video below). As a second one, use stacked or unstacked logos.
  12. Standardized color used for background (see the third video below).
  13. Make those diagram horizontal instead of vertical so it's easier to consume on a computer without having to scroll too much.
  14. Merge GitHub & GitLab diagram for all clouds (except k3d, or it will need more work to do the same as there are some noticeable differences) to use one image for both Git providers. We could represent GitHub/GitLab as a sliced box. It will be easier to maintain the diagrams, the docs, and better information display for the users.
  15. I didn't check them all, but I'm pretty sure most logos are images and not SVGs as it's the case of most diagrams created by Kubeshop.

First video:

CleanShot.2024-04-04.at.17.01.04.mp4

Second video:

CleanShot.2024-04-04.at.17.06.05.mp4

Third video:

CleanShot.2024-04-04.at.17.10.33.mp4

Code of Conduct

  • I agree to follow this project's Code of Conduct
@fharper fharper added the wrong Some information in the documentation is wrong label May 21, 2024
@fharper fharper changed the title Update the installation diagrams Update the installation diagramss May 23, 2024
@fharper fharper changed the title Update the installation diagramss Update the installation diagrams May 28, 2024
@fharper fharper added the P1 - Important Needed for our users to be able to properly use our product. label Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 - Important Needed for our users to be able to properly use our product. wrong Some information in the documentation is wrong
Projects
None yet
Development

No branches or pull requests

2 participants