-
Notifications
You must be signed in to change notification settings - Fork 192
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
Implement homepage mockup #128
Comments
TODO:
@calexity I see a "Closed" category here in the mockup, is the intention to only show this for "Submitted by Me"? |
|
After spending a few days on this (and thinking about it more over the weekend), I'm going to change strategy a little bit and do the following:
I plan on revisiting EmberJS when we build out the rest of Issues, for those who are sad now. |
Just pushed this live. \o/ Thanks again @calexity for the awesome design on this. |
Hey @miketaylr! Sorry for being so MIA. Yes, closed is only for issues you (as the user) submit. Looks great live! Thank you! I couldn't tell if I missed a meeting yesterday am, but I'd like to identify a next sprint and place a goal date on it. I'm going to mark a couple issues and you guys can add feedback? |
Sounds great @calexity. There actually wasn't a meeting yesterday. :) I was hoping to plan a few days to work out of the SF office in the next few weeks, maybe we could plan a jam session during the evening or something. |
Rock on! Would love that. Let me know when you'll be here and we'll make On Thu, May 29, 2014 at 9:00 AM, Mike Taylor notifications@github.com
|
We can build this easily and deploy it before having 100% of
/issues/
figured out, even if it just links to GitHub. I think it's a win to show sooner than later.Working on this now.
The text was updated successfully, but these errors were encountered: