Default signage (for sign generator micro-app)

[daguar]

Per discussion with @rduecyg @mollymcleod, here's the plan:

• Needed elements for CityVoice sign
  • Phone number
  • Box/space for call-in code to be written by printers
  • CityVoice logo/icon
  • Survey-runner's logo (or text, maybe both)
  • Call to action (needs to be customizable)
  • Good to provide examples or templates
  • Title of the project ("what is this for?")
  • URL for this specific survey's web site
  • Contact info
• The "sign-builder" app
  • Simple web form with the above fields and a picture of an example sign
  • Starting with one (big) size
  • 24x36
  • Should put in documentation that bigger signs are better (in Outreach section)
  • Black and white
  • Will need to provide some interface that has (a) the name of each thing, and (b) the call-in code
  • Going to put in instructions for a URL on the live instance that has this simple list (needs dev work)

[daguar]

Added that we're starting with black and white

[daguar]

Added note for the need to have CityVoice core app provide a list of names + call-in codes for each location

[daguar]

@mollymcleod will take a first stab with Illustrator + PDF files

[daguar]

Initial sketch

[migurski]

CSS print media/paged media might be a way to do this without generating a PDF?

[daguar]

I think that's right. My thought is @mollymcleod will be faster at putting together a quick design in Illustrator and then we can implement in CSS. But I defer to Molly on that point.

On Jul 31, 2014, at 4:40 PM, migurski notifications@github.com wrote:

CSS print media/paged media might be a way to do this without generating a PDF?

— Reply to this email directly or view it on GitHub.

[mollymcleod]

Here's my first quick attempt at a sign layout. I made an example sign, and template example where the form fields would be generated. If the character limits seem unrealistic given other example uses, happy to iterate on font sizes and such. (But for calls to action, probably best to keep it short.)

I even did a little research into typography and readability for larger format public signage. :grinning:

Let me know what you think, and once we get it to a solid place I can share files and style specifications.

[rduecyg]

This is great.

I think @migurski CSS suggestion is the right way to go.

Regarding graphic elements just some small initial suggestions.

• survey type and length field should just be a number field that asks "how long is your survey? *shorter is better, less than 2-3min is best", which populates "take an X min survey". Other graphic elements should make clear who it's from.
• toll free shouldn't be in the first iteration unless Dave is putting that in the builder app. Toll free numbers need to be specified in twilio and cost slightly more. Toll free numbers are better to use generally although you don't get a local area code

[daguar]

There's a basic version of a CSS-based sign generator live here: https://cityvoice-heroku-builder-dev.herokuapp.com/sign

[jmadans]

Closing this issue for now as Dave et al was able to get to a v.1 of our sign generator. Related findings from the CityVoice pilots thus far has been that city staff want to use larger, stake-in-the-ground signage. However, the sign generator offers a first stab mock up to share with the in-house shop or vendor they task with sign creation. As a result, spending time and materials on a more city-branded sign is worth their while.

thanks for the help @mollymcleod!

But IN THE FUTURE it could be interesting to put a template in something like Canva that gives them an easier, low-cost way to brand their signage themselves.

[daguar]

ooo, that's super interesting! Great to know!