For some listings, it may be useful to have phone and email contacts listed, particularly if the business in question doesn't have much of a direct web presence (as in local shops).

As a styling tweak, it shouldn't be hard to make links with appropriate icons (from the bootstrap glyphicon set) which actually pull up the dialer or send email when touched on a smartphone -- the tel: URL scheme is supported on both Android and iOS, and I believe mailto: is as well. (Current treatment of the google-maps links on address is one way for the styling to work; not the only way, but if we do something different, that should probably be dinked to stay consistent.)

Right now, anyone who signs up can edit the job listings. We should make a distinction between the admins who can edit the site, and the regular members who just have access.

If we start pulling in jobs automatically, we should have a place to put them where they aren't visible until a human looks at them to make sure they're appropriate for display.

It'd be nice to have a simple way to save a job for later, and then come back to see that list of jobs.

Maybe a simple ⭐ and list?

Blocked by #3

Right now, we have a bunch of jobs that are either made up, or pulled from sources we can't really use. We should remove them from the source and the production DB so we have a better sense of what we need.

We probably don't want listings just hanging around forever, or until someone explicitly decides to delete them. So...

Do they expire after a while? (If so, same lifetime for all listings, or do we let this get set per-listing?)

Also would there be use for a search form which allows designated users ("moderators" or whatever else) to see what listings are about to expire -- within 3 days or whatever -- to check on their status and possibly renew them?

A user may want to know how far the job is from them before applying

It's a word non-Rails people are more used to seeing.

currently the options are "full time" "part time" and "both". it may be more correct to say "either" or reword the question so that "both" makes more sense.

User testing indicated that it's unclear what's behind that. @rst suggested "...build my skills".

some job listings may be able to accept a submitted resume (for example a mom and pop shop where we are applying via email). In these cases we may be able to store a resume for the user and submit on their behalf.

Currently, the app is deployed on the Heroku free tier (web, DB, e-mail). We need to decide (along with the folks from YouthHub) what kind of budget/maintenance we're working with so we can figure out where it should go.