Linked by Thom Holwerda on Wed 26th Dec 2012 00:32 UTC
Thread beginning with comment 546442
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/20/13 6:17 UTC, submitted by MOS6510
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
More News »
Sponsored Links



Member since:
2005-07-06
http://postimage.org/image/ds7xv1ahv/
Does that improve things? I really want to avoid going all-white for the background :/.
Maybe a bit. But actually, what I forgot to write in my previous feedback is the question: Why don't you just allow users to tweak the color scheme for themselves? If you're already offering a "night" mode, I imagine it shouldn't be too much trouble to offer a few more alternative color schemes or even to allow more detailed per-user/per-HTML-element customization.
Agreed on the idea of taking on an actual graphic designer. Unfortunately I am not one. Anyone else reading this want to volunteer their talents?
Anyway, at the very least I would suggest you could try filling the current logo with all-green and with the font size of the word "news" increased. I think that could look quite decent even at smaller sizes.
Fine and good, but seeing as you are playing the role of UI designer as well as graphic designer these things are important to define as best as you can *now*. Otherwise some technical "features" will in all likelihood fill in the blanks for you, in a manner that in all likelihood will be sub-optimally usable.
Think about what the actual needs of your users are, not about some abstract concept of "future proofing". Learn a lesson from KDE 4 and don't ignore current usability concerns in the name of an abstract ideal of future flexibility.
Why not space the menu items out more so you can fit more than one-word item names, and call it "Support OSNews"? Seems simple and unambiguous enough to me.
The current UI of having other news items listed along the right-hand side is much more useful, if a bit distracting/cluttered.
Won't happen
OK if you're that set against it. But please at least take a cursory look at e.g. Ars Technica and the Verge, both of which make good use of this extra space.
I just think it needs to be above the fold, and not necessarily at the top. Putting it at the top would introduce a non-standard item to the top-right menubar (they're all text links, not input fields), which I don't want (it would look hideous). I can play with moving it above the user menu, though. Made a note to try this out.
Above the menu sounds good. Or again, check out Ars Technica -- they make putting it in-line with the menu work visually even though it is indeed another kind of element.
Glad you are responsive to this. It would be more consistent with the rest of the web.
Why not only show avatar icons if they're available, otherwise don't show anything? That's how The Verge does it and it seems to work fine there.
One more thing: The "Submit News" link doesn't have anything to do with the user profile and so shouldn't be buried inside the user menu. In fact this is an incredibly important function that you want to encourage the use of, no? I should think it's at least as important as the "Support OSnews" function, seeing as content is the number one priority of a user-content-based news aggregation and editorial site. So why not put it in a highly visible position, for instance in the top-right menu, perhaps in a brighter color to emphasizes it (like the "Subscribe now" item on Ars Technica)?
Cheers for listening, looking forward to the next update.
Edited 2012-12-27 18:08 UTC