-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Google Form Banner #162
Comments
I created the initial banner design given the following criteria (taken from OCS: Communications Guide):
|
Feedback from Bonnie after 2/13/22 meeting:
|
Using the feedback, I initially suggested replacing the people in the hero illustration with a magnifying glass as that would convey the "survey" aspect of the form while making it easier to depict in a vector image, even at smaller sizes. However, per advice from @jenchuu , the banner design is meant to convey the purpose of Civic Tech Jobs itself rather than the surveying method, in which case the hero illustration would be more relevant. I attempted to alter the hero illustration with a magnifying glass rather than the central light bulb to no avail; this would also be inconsistent with the other illustrations presented on the Civic Tech Jobs page. I then removed the two people kneeling in the illustration and reorganized the floating elements. At the same time, I proportionally increased the illustration size so that the remaining people holding the upper half of the light bulb were clearly visible. After uploading the design to a test Google Form, I checked the visibility on both mobile and desktop formats. I found that the visibility was sufficient for users to understand the image completely. |
Closing as #125 has also been closed |
Dependency
N/A
Overview
As a designer, we need to ensure that the banner on our Google Form surveys conveys the concept of what Civic Tech Jobs is to users while being clearly visible on all platforms.
Action Items
Resources/Instructions
Resources
Banner for Google Survey Figma Page
The text was updated successfully, but these errors were encountered: