Fedora badges is a perfect place to start if you want to help out the Fedora Design Team. ‘I’m not a designer!’ ‘I can’t draw!’ ‘I’ve never opened Inkscape’ – you might say. And that is totally fine! Everybody can help out, and none of those reasons will stop you from designing your first badge (and getting badges for designing badges ;)).
So let’s look at how to get started! (all of these can be found in our presentation here)
Inkscape Download: https://inkscape.org/en/download/
Fedora Badges: https://badges.fedoraproject.org/
Fedora Badges Open Issues: https://pagure.io/Fedora-Badges/issues?status=Open
2. Anatomy of a badge
As you can see, badge consists of several elements, all of which will be different for different badges based on how you categorize them. More on those as we look at Resources.
So now go ahead and download the Fedora Badges design resources
ATTENTION! VERY IMPORTANT! Prior to designing check out the Style Guidelines that you can find inside the zip file. Couple of things to keep in mind here:
- background and rings colors: it is important to keep badges consistent – please categorize your badge and based on that choose colors from the palette. If you need help categorizing, ask on IRC #fedora-design or during our bi-weekly badges meetings every other Wednesday 7-8 US Eastern on email@example.com.
- pallette (pp 12-13): if you need some other color, pick one from the palette. You can even download and install it on your computer to use straight from Inkscape. To import them, save the .gpl files to the ~/.config/inkscape/palettes/ directory.
- fonts (pp 17-18): use Comfortaa and pay attention to do’s and don’ts listed there.
- do’s and don’ts: it is very important to keep those in mind while designing, so all our badges are consistent and beautiful.
Another tip for consistency: once you’ve have picked a badge, go look at ALL the badges here: https://badges.fedoraproject.org/explore/badges. If you are just starting, it’s a great place for inspiration; you can see how similar badges have been categorized, and what imagery and patterns have been used. Download one of these badge artwork files and use it as a template or starting point for your badge design. To do that, simply click on a badge and go to its ticket. Usually .svg can be downloaded from there.
- Look at similar badges on badges index.
- Choose a concept for your badge. Look at similar elements, consider suggested concepts from the ticket, or come up with something yourself if you feel like it!
- The easiest badges are Conference and event badges. They are all the same colors: purple ring, grey background for conferences and dark blue for presenters. Use the template or even re-use last year’s badge and put your conference logo / year on it – Congratulations! You’re done!
- Gather inspiration & resources. This means going on the internet and researching images and concepts. For example, if you want to draw a badger on a bike, you might want to search for a photo or an illustration of a person on a bike to use as a reference. No need to reinvent. This may not be necessary for the simpler badges.
- Categorize your badge using the Style Guide or ask one of us for help.
- Open the corresponding template, Save as… your filename and get designing! Here’s a link to some nice Inkscape tuts: Fedora and Inkscape. Keep it simple and pay extra attention to resizing stuff. You don’t want to change background size and positioning, so don’t move it around. That way all the badges look the same. When resizing other elements always hold CTRL to maintain proportions. Also don’t worry too much, we’ll review your badge and help if necessary.
- Feel free to reuse and remix other badges elements. Also remember to SAVE! Save all the time 🙂
- Once you’re done with the first draft, go to Export PNG image, select a place where to export, name your file and choose Export area – Page. Check that your badge is 256×256 and there! All done! Congratulations!
- Upload png to the ticket and ask one of us to review your design.
- Now work with a mentor to finish it and with a developer to push it.