Add more information on how to locate design issues in a project, for designers with no prior knowledge

[ifeneris]

Based on the assumption that many designers are not familiar at all with Github's organization of issues (and tags) and might feel overwhelmed when landing on a project's GitHub home page (Code), we can assist them by adding more information on what to do after finding a project in the "/projects" page. This could be achieved by adding information and learning material on the "/for-designers" page and/or on each project's page about how issues are organized based on tags.

[pavlosts]

Should we create a UI Kit or something? If multiple people are going to work on the designs, we need a way to keep everything consistent.

[ifeneris]

Should we create a UI Kit or something? If multiple people will work on the designs, we need a way to keep everything consistent.

@pavlosts Sure, this can be another separate issue: building a design system to maintain consistency as the design expands and more designers are involved.

However, for this issue, I think that the current design files, their structure, and their assets (which can be found at .design) cover our needs. Let's try those and find out the process we should follow.

[fivenp]

This could be achieved by adding information and learning material on the "/for-designers" page and/or on each project's page about how issues are organized based on tags.

I like this idea.... I could def. see the For designers section to expand over time and include not only best practises around GitHub but also communication hints, what to do, what not, setting "basic expectations" for designers and guide them how to participate / communicate :)