Open chillkang opened 3 months ago
Looks good, but specific example you've given here shows an issues with this. The product site is meant to be used for charms that have product pages outside of charmhub, like mySQL. (Product page for MySQL).
In most cases website is just the link to charm, which is useful in github docs, but less useful as a link within charmhub. If possible, if the product link could only be shown if it's not a link to charm in charmhub would be ideal. Not sure how possible, but would be much preferred.
Other than that all look really good!
I'm going to say the same thing. From what I understand the "product page" is meant to be a single link. But for https://charmhub-io-1843.demos.haus/mysql for example, there's a list with no way to discern what each link will do. I'm not sure how the design handles multiple links, or how we would differentiate between the upstream product page and a general link? In snapcraft we split it up into different link types: https://snapcraft.io/lukewh-test
We could have multiple solutions for this.
Happy to discuss, but need to make a decision on this before moving forwards
We could have multiple solutions for this.
- Either just display links that aren't labeled the way snapcraft does it (just show the domain and add to other links section)
- Or force a stricter structure on metadata.yaml/charmcraft.yaml where each link if named (like Charm repository, charm product page, etc.) has to be written in the correct format to be displayed, otherwise it won't be shown
- 2nd option but add other links section for every link that isn't following the preset links.
Happy to discuss, but need to make a decision on this before moving forwards
@lukasSerelis I'm happy with either option and let's discuss this next Monday :)
We've discussed how to deal with the multi link situation and this is where we've left it:
websites:
, displaying multiple product links makes no sense, and trying to make sense of which link is what sounds like a job for the charmcraft.yaml spec to standardize more.websites:
and display that as product page, as in most cases this is where the product page should livewebsites:
isn't a charmcraft.io link, and if it is, don't show it. We just need to be diligent that this is a temporary fix, and we are not going to forever try to make sense of inconsistent .yaml files. This check should be removed once we get some more movement on charmers using the proposed charmcraft.yaml template.There's a small UI issue here as well, where the space between icon and text isn't margin or padding, it's just to spaces. This is the spacing that should be followed
For whatever reason pgbouncer charm has a product link as first link in websites:
also has a source:
but show the github link as the product page link and no source link at all
For whatever reason pgbouncer charm has a product link as first link in
websites:
also has asource:
but show the github link as the product page link and no source link at all
You found the outlier! This is the metadata I'm getting so I'll dig into this issue.
Another one that follows the same mistake: https://charmhub-io-1843.demos.haus/kafka-k8s
Done
Charm details
section to includecharm repository
,charm product page
, andjuju version
frommetadata.yaml
Contacts
section to include maintainers and submit a bug link frommetadata.yaml
charm product page
, only include the first link and do not show the link staring with https://charmhub.ioHow to QA
Charm product page
link showing in the side-navigationCharm product page
link showingTesting
Issue / Card
Fixes https://warthogs.atlassian.net/browse/WD-10007 Fixes https://warthogs.atlassian.net/browse/WD-10933 Fixes https://warthogs.atlassian.net/browse/WD-10934 Fixes https://warthogs.atlassian.net/browse/WD-10935 Fixes https://warthogs.atlassian.net/browse/WD-10936 Fixes https://warthogs.atlassian.net/browse/WD-10937
Screenshots