-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Create branding / style guide #84
Comments
@cecivieira @julianafalves I will add the assets for the new repo here : |
@marie-l is not exactly a new repo. I will update this one https://github.com/pyladies/pyladies-assets |
@cecivieira yeah sorry I referred to it as 'new' because there's nothing in it yet |
@cecivieira - that repo belongs to the |
yes, thanks @BethanyG ! |
We should also look at how we are going to manage image assets. Github has poor tools for diffing images. |
I spoke too soon! Turns out MS has added image diffing capability! 🎉 https://docs.github.com/en/github/managing-files-in-a-repository/rendering-and-diffing-images....just not for design files. |
@BethanyG it's a shame that it's not for design files, but I think we might have listed other options in another issue or notes. I'll have a look. @cecivieira @julianafalves I've added the social media banners and avatar. I haven't included the event promos etc because each file has many layers so we would need to save them separately to make it easier for people to edit |
@marie-l - version control for design files is either pegged to specific formats (abstract & kactus for Sketch, adobe experience manager for Adobe, some other really expensive ones pics.io & sympli that support multiple file formats. And then there is Folio, which is limited to Mac users -- and it's $49 a pop. There are others out there keyed to design pipelines and developer handoff -- each of course has its own subscription fees associated with it. Truth be told, design file formats are a can of worms because not everyone can afford design software, and the vendors have gone to great lengths to not cooperate with each other. All that being said, we can probably provide several different formats for people to use -- and as long as we provide banners and text in SVG, they can be resized without losing clarity. |
Perhaps, if we publish "branding colours, pyladies global avatars and pyladies global banners" in the Communication Assets Repository (https://github.com/pyladies/communications-assets) we'll duplicate the proposal of the general assets repository(https://github.com/pyladies/pyladies-assets), because one part of it description is "This repository is for all assets, logos, etc used for PyLadies.". So, maybe we could update the general repository with "branding colours, pyladies global avatars and pyladies global banners" and uses our Communication Assets Repository for to publish the editable graphics with instructions for translating the text beging the objective to facilitate the local communities its reuse. What do you think? |
@BethanyG we'll intend to publish temporarily the editable graphics, only during the context period. I didn't understand what kind of situation you tried to solved with the messages about tools for diffing images. Could you explain a little bit? |
Summary
To create branding guidelines (for reference purposes) to share within the community.
Acceptance Criteria
Do you want to work on this issue (Yes/No)?
Yes, alongside @BethanyG. We will share our work with @cecivieira @julianafalves .
cc / @pyladies/communications
The text was updated successfully, but these errors were encountered: