Wireframes

[rhallac]

Wireframes for the Job Board

[GarthDB]

Excellent!

[rhallac]

[GarthDB]

@rhallac, this is great.

Could you do a page for the individual project? We don't have to have all the information on the list view. What do you think is most important?

For now let's sort by date/time posted; most recent first. We can do something fancier later. If you have a more useful way to sort it lets put it in github issues for now.

[GarthDB]

Let's not do tags quite yet. Another thing to add. Let's start with the mvp.

[Moodycomputer]

@rhallac-

As far as an MVP goes, I usually avoid adding in search or sorting functionality. I'd suggest going with a standard reverse-chronological sort for this pass.

For information architecture, it's sometimes helpful to draft up a few demo posts instead of using filler text in order to make sure you get the pertinent information right. Maybe try drafting a job post for this project in order to get a feel of info hierarchy?

It looks great- I'm excited to see it shaping up.

[rhallac]

Started making some of the updates and project page wire!

[GarthDB]

@rhallac leave the home button in - wireframes show information architecture and function more than layout.

We can leave in the full project summary, we can bring it in from the github api and truncate it if it's super long.

As far as the contact I'm not sure. That's kinda the goal - people should be wanting to contact the project owner next. Not sure how people would feel about their email address just posted publicly on a site though.

Any thoughts? @terracomma @ngovkevin @elaineyhwang @davidweinfls

[GarthDB]

@rhallac let's add the comments after MVP.

[davidweinfls]

@GarthDB I don't think its a good idea to leave user's email address there. Probably we can add a feature called "contact owner" which can send emails or github notifications to the owner.

[GarthDB]

@davidweinfls agreed. Sending out emails can be a little tricky to do correctly, but let's plan on it for now.

[Moodycomputer]

I agree with removing email addresses.

Sending notifications to Github sounds cool, but I know that I get so many in my notification center that I miss most of them. (ie: I have this repo set up to email me issue comments, but none others)

An email functionality is probably the best method.

[GarthDB]

GitHub Notifications isn't an option - there are set notifications and the api lets you do some things with notifications (i.e. mark as read), but you can't do custom ones.

[davidweinfls]

For each post, probably we can add a status tag to each post. Say a green light indicates this post is active and needs more contributors, and a grey light means this job is done and marked as closed.

[GarthDB]

@davidweinfls so this is something a project owner would log in and set to inactive or would a post expire after a certain amount of time?

[davidweinfls]

@GarthDB yeah. I think it is useful. Designers don't want to join a inactive project

[GarthDB]

@rhallac can you put in some active/inactive indication on the posts and let's close this issue to move on to final ui.

[rhallac]