-
Notifications
You must be signed in to change notification settings - Fork 308
change the visual design of gittip #66
Comments
I think the initial goal here should be creating 2 Gittip logos, large and button-sized. |
You don't like the heart-coin favicon? :-) |
nope. |
Thanks for the effort. I think the design is good enough for the current phase of growth. My ideal would be to "hire" a professional designer to own the Gittip visual design for the next phase of growth (whatever "hiring" turns out to look like for an open corporation ;-) ). I'm going to keep this ticket in the icebox for now. |
I fully agree. |
For lack of more specifics, I interpret comments like this as +1's for this ticket. |
A few notes on this as I believe Damon from Balanced is going to give this some attention:
|
I like the current design. The icon is nice, but you may want to tweak the heart a bit - it looks a little squished to me. I might also suggest a different color scheme. The neutral colors are relaxing but you might want something a little brighter. Maybe a browse option of some sort would be helpful? Perhaps associating users with their projects (or primary/most recent project?) more readily? |
Would love everyone's feedback on the design for Gittip. Thanks!
|
This is really exciting, @dmdj03, thank you! Will review more fully tomorrow. |
One quick question: could you post a bigger pic of the logo for us, and maybe say a few words about it? |
Sure. You can use this same link to access the logo: With the logo, I wanted to create a separate bug that could be used independent of the wordmark - as a button perhaps. I modified the "G" to incorporate a bow/ribbon as a subtle reference to the idea of gifting / giving thanks. |
Inline images ftw :) |
I really like the bow/ribbon, because it looks a bit like an infinity sign, which implies the ongoing nature of donations. (Of course I'm in the middle of a math class right now, so me seeing infinity signs everywhere may be unusual). |
@dmdj03 Ah, now I see the bow, not sure what that was. Very cool! @kennethreitz Thank you! @chmullig Good call! |
I like it. Although there was something nice and unique about the Green/Teal(?) color combination that Chad began with... I am partial to those colors, it's an attractive scheme that you don't see very often. |
Really a step up! The colors are a little bland, but still surprising... Two verbal critiques:
|
Yeah I don't know. "Fund people"? "Fund people building the commons"? We lost the heart ... |
Sponsor People |
Does "fund" have currency at the moment? Crowd fund ing? Is that a hook? |
What's wrong with the current name that already has people's attention? |
gittip is pronounceable and easy to remember. gfftd is not. |
I can't even tell what letters are in gftftfd. |
It would be pronounced "gifted." |
|
@whit537 are you looking for the AI file? or just a jpg of the design? |
@whit537 I may feel inspired to rework some of the front end to match that design once rubygems stuff is done, but one thing at a time. |
@dmdj03 I was looking for the AI files. |
@whit537 I wasn't able to attach the AI here since it's not an image. Here's the link to the folder: |
Thanks @dmdj03! :-) |
Whatever we do here needs to be responsive. |
I agree, also on another note looking into mobile apps wouldn't hurt in the future. |
@clone1018 as long as @whit537 only ever uses HTTPS, the mobile app (assuming it is well designed) will be the better way to go. Currently the API wouldn't allow for good mobile application development. (A RESTful API would make that way easier.) |
Mobile apps: Sure, just had a non-geek friend on Facebook ask me when to expect the iPhone app. |
@nicksergeant has expressed interest in picking this one up(!). |
Hopefully will be able to get started on the front-end by early next week. Looking forward to it :) |
@nicksergeant Reticketed conversion to markup as #516. Let's discuss further there and elsewhere. |
At our hangout on Tuesday, we talked about using GitHub milestones more effectively, and I think this is a great case for that. I've created the following milestone to track this instead of continuing to load up this ticket with everything: https://github.com/zetaweb/www.gittip.com/issues?milestone=26&state=open |
Gittip homepage redesign (for #66).
Here's what I did: - Took out redundant getters and modified tests to expect ints - Standardized on 'expiration' instead of 'expiry' - Reverted to former FORM width, tweaking only expiration field - Stuck with pixels for FORM layout (a switch to em should be done as a whole, and #66 surely affects this) - Show expiration error before CVV to match order in UI
Fuck. Yeah. |
woah! |
:-) |
Scroll down for comps.
The text was updated successfully, but these errors were encountered: