Wanted: Raku Branding Guide

[sjn]

Could we (stepwise/slowly) move towards creating a complete and generic branding guide for all Raku things?

Here are a few tasks this repo could be improved with...

• [ ] Visual identity guide – For helping contributors create works that have a common recognizable expression.
• [ ] Color guide – including acceptable color combinations, readability/contrast, themes and recommendations for creating anything from "regular branded content" to text with emphasis.
• [ ] Color specifics – for digital/online use (RGB) and print (CMYK) and apparel (CMYK/Pantone).
• [ ] Font guide – for creating headings and other texts in a style that fits well with the logo, branding, colors or other styling.
• [ ] Illustration guide – for creating other images, icons and symbols in the same style as the logo or in it's own style.
• [ ] Pattern guide – for adding background patterns and other repeated imagery.
• [ ] Branding usage guide – for showing how the all branding elements should be used together, and with other elements; Including margin, placement and variation dos and don'ts.
• [ ] Document design guidelines – for creating professional-looking prints and presentations within the constraints of the branding guide
• [ ] Core assets library – with all necessary and useful images, vector graphics, templates and other assets easily found.
• [ ] Asset license & terms – with instructions and conditions on how to contribute improvements to anything related to branding.

Example of a well-made and complete branding guide: Internet Society's Branding Guidelines.

(I'm really impressed by what ISOC did with their branding guide, so I hope others also can find it inspiring!)

(the text above is a copy of https://github.com/metacpan/perl-assets/issues/5)

[finanalyst]

This is something that needs doing. For example, we don't have a canonical source for the Camelia image or favicon.

[sjn]

This is something that needs doing. For example, we don't have a canonical source for the Camelia image or favicon.

Yeah, a core assets library would be the right way to address this. It's also something that can be easily done, e.g. by stating somewhere central (e.g. in the rakudo repo) that this repo contains is the canonical source for assets like these. :-)