Idea: Live Logo

A lot of brands do seasonal or topical themes with their logos and branding, one popular example of this is Google Doodle (https://www.google.com/doodles)

However Google Doodle does not replace the Google logo itself which generally remains the same. Google Doodle also does not employ any governance process, which means the community has little say in this aspect of Google.

Polkadot announced a rebranding process that will involve a branding agency using their on-chain governance processes to guide the process: https://decrypt.co/53325/leading-design-agency-koto-is-giving-polkadot-a-rebrand

One interesting idea would be in the future to have the Joystream logo become "live"--this means that new variations of the logo can be voted in somehow, and most importantly the logo can become "just another line of code" that can be updated via the governance process or some other voting mechanism.

It may be that the rules surrounding updating the Joystream branding are very strict or very relaxed, this is not possible to predict. Ideally there would be some consistency between logo variations in the form of typography or colors used.

It is probably far too early to experiment with such an idea from a branding perspective as the community is still in early stages, however there appears to be no projects that exist that have the concept of a "live" logo that is community voted and can change reactive to how the community is feeling or thinking at a given point in time. On a long enough timescale, the previous iterations of the logo would serve as a rich history of the Joystream community.

How exactly a new logo would be voted in would have to be decided, but it could use a system like this: https://github.com/Joystream/joystream/issues/1966 or https://github.com/Joystream/joystream/issues/1094

On a technical level this raises the question of how the logo would be stored/updated in a mainnet scenario.

┆Issue is synchronized with this Asana task by Unito

No files or tests are identified. Start by reviewing the governance examples in issues #1966 and #1094, then determine the requirements for voting on logo variations and for storing and updating the approved branding on mainnet. Done would require an agreed technical and governance design, not just a logo concept.