Problem/Motivation
Many providers like to see their logo on the translator/provider settings page.
Originally we were unclear if we are allowed to add the Logo to the GPL code on drupal.org
The Drupal Association and Dries recently confirmed that the GPL only applies to Code and not to assets such as a company logo.
Thus projects are allowed to upload logos to the repository.
Proposed resolution
Add a provider logo to each provider definition.
The logo will be displayed
- In the provider list overview as separate column
- In the provider settings form, floated right
The bounding box will be limited with a max height / width to avoid breaking design.
Update the existing providers.
Remaining tasks
Unsure if this is custom to each provider or if we want to allow a logo reference in annotation or some other way such as an interface.
User interface changes
Show logo and through that make the user feel it is more official and services can be visually identified.
API changes
Annotation or interface?
Comment | File | Size | Author |
---|---|---|---|
#28 | interdiff-meta_add_provider-2713243-26-28.txt | 372 bytes | edurenye |
#28 | meta_add_provider-2713243-28.patch | 8 KB | edurenye |
| |||
#26 | interdiff-meta_add_provider-2713243-21-26.txt | 4.47 KB | edurenye |
#26 | meta_add_provider-2713243-26.patch | 8.02 KB | edurenye |
| |||
#26 | meta_add_provider-2713243-26-12.png | 17.89 KB | edurenye |
Comments
Comment #2
edurenye CreditAttribution: edurenye at MD Systems GmbH commentedComment #3
edurenye CreditAttribution: edurenye at MD Systems GmbH commentedWe will provide logo, preferably as svg, by annotation. The preferred aspect ratio is wide due to the overview output.
The test translator will also provide one to test cover it.
Neither XLIFF nor Local / Drupal translator will have a logo.
Comment #4
edurenye CreditAttribution: edurenye at MD Systems GmbH commentedHere is how looks like:
Comment #5
miro_dietikerThis looks great.
But we need the follow-ups in the individual projects with the logos added / annotated.
I think the logo column doesn't need a "Logo" label in the header.
Also i caught "TRANSLATOR NAME" in the column overview that should have been renamed to Provider already...
Anyway, if i edit, it's called "Label" instead of "Name" and IMHO "TRANSLATOR" is redundant anyways - so we should drop it and switch to "Label" only.
Label is doubled here. You should write a hardcoded "Logo" here because the label is just output the column before.
In the Settings form it is OK.
Alternatively (better?) you could output "@provider Logo" and pick the provider plugin label.
Comment #6
miro_dietikerAh, also, as stated above, the test translator should declare a logo and we should check it.
And i'm promoting it since it has been requested so many times by providers.
Comment #7
miro_dietikerComment #8
edurenye CreditAttribution: edurenye at MD Systems GmbH commentedDid the proposed changes and added test.
Now looks like this:
Comment #10
edurenye CreditAttribution: edurenye at MD Systems GmbH commentedComment #11
edurenye CreditAttribution: edurenye at MD Systems GmbH commentedCreated all the followup's:
thebigword: #2717311: Add logo to provider overview
oht: #2717295: Add logo to provider overview
gengo: #2717289: Add logo to provider overview
google: #2717283: Add logo to provider overview
microsoft: #2717233: Add logo to provider overview
Comment #12
edurenye CreditAttribution: edurenye at MD Systems GmbH commentedComment #13
miro_dietikerWe could refer on any core svg instead of adding a custom one.
Preferrable, instead of the $entity label, output the plugin label.
Comment #14
Berdir@Miro: We enforce that the svg has to be within the module that provides the plugin. So we can't use one from core.
What about, instead of naming this "Logo", we name this column "Provider" and fall back to just the label if nothing is provided?
I guess the text only versions would be weird by default as they'd duplicate the text. So even without text fallback Provider as label might make more sense?
Miro proposed no label at all, not sure about that. Could work if can combine the two columns together?
Why not use #theme image for this?
Iagree with Miro that it should be the plugin label.
Also, below you removed logo, I think that should also be done here?
Leading / usually implies an absolute path, I think those things are usually specified without and the / is added in the code that adds it.
theoretically, we could use the / to indicate an absolute path outside the module but I don't think that supporting the code for that is worth it, not if the only use case is the test plugin.
Comment #15
miro_dietikerI like the proposal with "Provider" as heading in the plugin label column.
However, the image then should no more contain "logo" in the text for accessiblity reasons. It's simply the provider plugin name.
Comment #16
edurenye CreditAttribution: edurenye at MD Systems GmbH commentedDone as discussed.
Comment #17
johnchqueIt seems the icons are a bit off-center in the providers list. Should be one extra line in css.
Comment #18
johnchqueComment #19
edurenye CreditAttribution: edurenye at MD Systems GmbH commentedYes, you are right looks better now:
Comment #20
miro_dietikerI think this looks great now and almost ready...
Why once image and once an inline template?
Comment #21
edurenye CreditAttribution: edurenye at MD Systems GmbH commentedI forgot about that sorry.
Testing again manually I fixed other things, like add the slash now that we don't want it in the definition of the provider.
Also fixed the CSS, is not the best solution, as is not really how I would like it to behave, but the proper solution would be add something like the EQCSS, or maybe add this directly to core as this could be needed in a lot of places like #2696933: Content overflow issue, and also could make things cleaner and easier in a lot of places.
Comment #22
johnchqueI like this css approach, we should also consider open a core issue related with that #2696933: Content overflow issue
Comment #23
miro_dietikerI can not believe we are unable to float it at 1024px full screen. I still do many screenshots for presentations at that resolution and i'm expecting a desktop look and not a mobile one at that size.
Comment #24
BerdirAlso, AFAIK we discussed showing it on the job checkout settings as well at some point? As a translation service provider, that's where I wanted my logo to be visible.. in a place that users will actually see when doing translations.
Comment #25
miro_dietikerYou are right that this makes sense to make it visible when working with the thing.
We completely forgot this location in the original issue scope definition.
Comment #26
edurenye CreditAttribution: edurenye at MD Systems GmbH commentedAdded the new icon in the checkout form.
Also considering that in the settings box we can not know what is inside we agreed to move the logo outside, as we can control how it looks there.
And finally the icons looks good and are responsible.
Thanks @yongt9412 for the tips with CSS.
Here some screenshots:
Comment #27
miro_dietikerSo!much!responsive! Awesome! ;-)
And yeah, we should recommend wide logos. The higher they are, the worse is the wrapping.
Hope we can commit this soon now, but..
!important will create trouble and i almost can't believe it's needed here.
Comment #28
edurenye CreditAttribution: edurenye at MD Systems GmbH commentedYou are right, it works without the !important.
Comment #29
BerdirCommitted including all logos.
Comment #30
BerdirNow committed correctly. Also this wasn't really a meta, just had related issues. metas usually don't have a patch on their own.