-
Notifications
You must be signed in to change notification settings - Fork 1
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
Branding guidelines? #2
Comments
Thanks, @acli, for this issue! To be honest, the current "branding" was a quick shot from the hip at a logo to disambiguate the GitHub organization repositories in the repo overview for us internally, mostly. I'd quite like to have a nice logo and branding that we can use here, on the website, and in slides, etc., but we're no graphic designers. I think to have branding guidelines, we should have a logo and a - what do you call it? - wordmark. FWIW, I like the CSL logo and the de-RSE logo. @jspaaks, as the creator, do you have any thoughts on licensing the current logo? |
Nah, @sdruskat, you don’t absolutely need a wordmark to have branding guidelines (in any case, I’d say the current logo is already technically a wordmark). I didn’t graduate from graphic design but I’d be pretty confident to say you just need a desire to lay down things like what it means to be (visually) consistent, how consistent you want things to be, etc. We could start with just a simple list (I know one-page branding guidelines exist out there) |
Thanks @acli, I think this sounds reasonable. Does it still make sense to create a new logo before drafting guidelines? |
@sdruskat I’m probably not the right person to answer that question (I usually don’t touch branding projects – it’s not my area), but as far as I understand this partly depends on whether the current logo already has “equity” (whether it’s well-known). |
I daresay it's likely either not well-known, or completely unknown 🙂. |
I think it is probably helpful to write down a couple of pointers on how we would like people to (not) use the CFF branding. Generally speaking the wording should give the impression of not being too restrictive. Maybe the GitHub octocat logo text could be an example? https://github.com/logos For now, I'll stick a |
I have forked the repo and created a branch to work on this. Please comment on the problem statement and the draft guidelines. Thanks. I’m going to create a separate branch to work on small tweaks to the logo (specifically the specific tint of blue, legibility checks, and visual centring, i.e. points 1, 2, 4 in the problem statement). |
Hi Ambrose,
Regarding the guidelines and problems statement:
Perhaps you can already make a Pull Request while you work on things? That'll make it easier to see the differences. Just mark it Draft so we'll know it's still a work in progress. |
Hi @jspaaks , Re bullet point 4, I mean centring the letters “CFF” within the rounded square. Currently it’s probably mechanically centred but I don’t feel it’s visually centred, and in logo design we would care more about visual centring. “CFF” is a little hard to visually centre because the curves on the left of the C and the whitespace on the right side of the F pull our attention in opposite directions, but in my judgement “CFF” should be moved slightly to the left. I’ll show you in a pull request once I have it ready. (The pull request will be just for demonstration; I don’t have the correct software.) Let’s treat this as an exercise in requirements analysis. |
I have created a demo at https://github.com/acli/branding/blob/20210830_LOGO_TWEAK_DEMO/doc/TWEAKS.md |
agree Re software, I used Inkscape https://inkscape.org/ I'll try to look at the demo later |
Latest thoughts from the discussion about governance:
|
Are there any branding guidelines? Should we create one?
Are there any restrictions on who can use the logo / how the logo should be used? Are they under some kind of CC license?
The text was updated successfully, but these errors were encountered: