Every Web site has flaws, including ours. And after every major change in a large-scale site, such as the one we made several months ago, when we not only did a major redesign but started using the (open source) Xaraya content management system, problems always crop up. Here's your chance to let us know what you think needs changing on the site, and why.
But first, let's get a couple of questions out of the way.
Q: Why do you allow those awful ads from "X" company on your site?
A: Because our editorial and advertising departments are totally walled off from one another. This means advertisers have no say in what articles we write (or don't write) and how we write them. The downside of our editorial freedom is that we -- editors, writers, and readers alike -- often see ads we don't like, just as advertisers often see stories here that they don't like.
Q: Why can't I view all comments at once instead of clicking on one at a time?
A: You can. Take 10 or 20 seconds to create a Linux.com login and you will have a number of comment-viewing options. We don't sell your email address or spam you, so it is risk-free (and free-as-in-beer) to create a user identity here.
Q: That article was totally biased (in favor of/against) (fill in here)! How dare you?! You suck!
A: Many years ago, I came up with this dictum: "The only unbiased journalist is one who agrees with me in every way." Note that we accept (and pay for) articles from people with many different opinions, as long as they are about Linux or FOSS. If you feel your viewpoint isn't adequately represented on Linux.com, write an article or commentary that explains your viewpoint and why you hold it. If it meets our specifications, we'll probably run it.
Now that we've gotten those few questions out of the way, please ask yours -- or make any suggestion you like on how we can improve Linux.com. Either post your comments below or (if you prefer a private conversation) email editors@linux.com. We are always eager to hear your comments and suggestions.
Note: Comments are owned by the poster. We are not responsible for their content.
Regarding speed, I'd suggest sticking <a href="http://nginx.net/">nginx</a> frontend web server to spare RAM and free up backend apaches to actually run CMS. Probably it's way too late to suggest not considering *Nuke clones at all and having a look at real CMS like <a href="http://typo3.com/">TYPO3</a> -- but we did drop PHPNuke and PostNuke in favour of that one (runner-up was Drupal, Java-based weren't considered for practical reasons) and I'd heartily recommend that if you [will have to] reconsider some day. Can also try to help with tuning these.
Regarding changes -- people don't usually welcome these by default; running to and fro with single sign on seems to have had decent impact on anonymous posting share.
Ah, and nl2br on comments would be really appreciated as mentioned probably daily.
I don't see why you need Javascript enabled to view comments. That's just weird.
I was trying out new themes for my desktop and that included changing colors.. when I viewed your site it was insanely hard to view.. if I remember correctly the white background stayed white, but the font changed to my themes font color which was unfortunately light grey. I'm just trying to say if you keep the background a fixed color so should the font.
I 100% agree with validating your pages. Please do. However, on that front, this may prove some good reading on that front, if you haven't found it already:
http://www.webdevout.net/articles/beware-of-xhtml
Kevin
Much of the CSS is screwed under firefox. Perhaps it looks good under IE, but what would be the point of that for a site called linux.com? Specifically, in the collapsed threaded view of the comments the lines of multiline headings overlap and he comment view controls show only half the contents of the dropdown. Even the "Print" and "Comments" links on the top right of the browser don't fit in the correct place, instead half-overlapping the black border. The line spacing in the comments is pretty ordinary too... it has been set to be somewhat less than the readable line spacing for the fonts that are used and the result is the ascenders and descenders overlap.
Normally, that's a sign that the CSS uses pixel sizes not relative sizes, with silly developers who've yet to realise that not everyone uses 72dpi monitors... it's really poor and amateurish and not what I had grown to expect from linux.com.
Oh, and you site claims that each page is XHTML1.0 compliant but it's not... just click the link at the bottom of any page to see why. e.g.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.linux.com%2Ffeature%2F120913
The new linux.com is a usability nightmare. I presume that this article was about getting feedback to find out why traffic has gone down substantially since the redesign... Well, that's why I spend less time on linux.com/newsforge than I used to.
Oh, and why do I need to type in
just to be able to start a new paragraph?
What's wrong with Linux.com?
Posted by: Anonymous [ip: 216.138.152.254] on November 05, 2007 07:24 PM#