Slashdot Mirror
Retooling Slashdot with Web Standards
Joe Clark writes "Nearly a year after an interview with this correspondent highlighted a few problems with Slashdot's HTML, Daniel M. Frommelt and his posse have recoded a prototype of Slashdot that uses valid, semantic HTML and stylesheets. Frommelt projects four-figure bandwidth savings in the candidate redesign, were it adopted, not to mention better appearance in a wide range of browsers and improved accessibility. Next he needs volunteers to retool the Slashdot engine. And yes, he did it all with CmdrTaco's blessing." Slashdot has kept its HTML 3.2 design for a long time ("because it works"), but perhaps this effort will be a catalyst for change...
That's all well and good, but you don't want to break the old page. I read slashdot often with my "text zoom" on mozilla 1.0.1 at 120 or 150%.
Right now slashdot looks normal at any text zoom setting, but the version proposed in the article hides parts of words when I turn up my zoom to 200%. I don't often read with text that large, but I've done it before, and I'm sure there's users out there who do it regularily.
The bit that impresses me more is that the page rendered properly with Mozilla Firebird 0.7 on Win32. The real slashdot doesn't render particularly well at all with Firebird for me.
I find your ideas intriguing and I wish to subscribe to your newsletter.
If Slashdot is going to be recoded, I would like to ask for four features that are easy to implement, and that would be very nice to have.
1. When you click on your username, you see all of your comments, and next to your comments, you see the number of replies to your comments.
It would be really nice if this number would be clickable, so you could immediately read the replies to your comments. (It's quite complicated to get to the replies now, especially when you've put a high comment threshold in place)
2. Can story submissions be placed (more logically & more conveniently) on people's slashdot-homepages, instead of on the page that you get when you click on "submit story"?
3. It would be nice if you could see your own story submissions (not just the subject, but also the body & other details) when you click on them. Just to see them back.
4. Could the default comment-submission mode be changed to "plain old text" instead of "html-formatted"?
It is confusing that you have to write your own html in a text area on slashdot to get something as basic as newlines, where there is no other site that I can think of - not even a geeky one - that requires you to manually enter the BRs.
It's just not useful, not intuitive and not nice this way.
While you're updating the (X)HTML to be compliant, why don't you make the search engine actually search? As it is now it's almost completely random as to what you get when you click "search", no matter what you put in the box. I've gotten completely different results just by hitting reload.
- Sherman
Ok, I like ALA, I'm a bit of standards guy even, my whole website is XHTML 1.0 strict. Unfortuanately slashdot has a table based layout, which, to put it simply, CSS cannot handle. I've spent days researching correct CSS tables in the past and it is an impossibility. The problem? Font overlapping. Try a text zoom to as little as 200% (yes, doubling the text size is not that extreme) and most CSS table based designs instantly break. Much like this one. My site works fine with it as everything is position ed such that font size only breaks at absurdly high magnification, but if it were any more complex I'd HAVE to use tables. I don't know if this si a browser issue, or a problem with the CSS spec, but text overflow is a serious issue, one which breaks nearly every CSS page with complex layout in existance. There needs to be a way to style tables in CSS without having to use a table tag. In short, CSS boxes are just that, boxes, they don't link together to correctly handle font sizes. The new slashdot is more broken than the current slashdot in a functional sense.
Photos.
I like bandwidth savings but I am really curious: are any blind people (let's face it; we're not talking about "accessible" for paraplegics or the deaf) read Slashdot?
And do you do it with a reader that doesn't interface directly with IE's rendering engine rather than reading the HTML directly?
Despite running some very information-centric sites, I have yet to see a confirmed assistive technology surfing my site in the logs--yes, I know all about spoofing, which is why I ask...you'd think that some of them, given the Biblical proclamations about standards liberating the handicapped that come from ALA, would just be a HTML-slurpers that give a unique identifier to logs and simply break on IE-only sites.
So, any of you out there? Is the site unusable on JAWS or some such? I want real blind people who use it every day rather than somebody who once listened to JAWS read it in a lab or academic setting.
If page 1 has: thread A with 14 subcomments, thread B with 22 subcomments, and thread C which has 17 subcomments, but...
there's only room (based on the max page length) to show A, B, and 13 of C's comments...
Page 2 will start over with the first comment of thread C. So you get to reread the first 13 of C's comments.
All hell breaks loose if thread C has more comments than can be shown in a single page...
Each page wants to start at the top of thread C again.
The problem is slash won't start page N in the middle of a comment thread. Any comment thread that was only partially displayed in the previous page is reshown in its entirety.
very annoying.
the italic words on slashdot are rendered in bold on konqueror 3.1.4 no matter what font i use. also, the font for comments seem to depend on the general font of X and konqueror. i would prefer if slashdot specified a standard typeface for comments and other aspects of the website. while slashdot loads pretty quick here, i would welcome a fresh look to the website. a better way to view comments would be nice too. the threaded system is cumbersome when there are too many comments. just my $0.02
is that the default comment view (i.e., when you don't have an account) is non-threaded, oldest first. Which is just stupid. People visiting are treated to pages of whatever the current first-post troll is these days.
Switch the default to threaded, highest scores first, and then if a visitor wants a more chaotic view, they can deliberately ask for it.
You cannot apply a technological solution to a sociological problem. (Edwards' Law)
" Could you please make page 2 of comments actually be page 2 of the comments."
Easy: Leave the main page as it is and pipe the comments to NNTP.
Is it really just the advertisements that prevent this? Why not create alt.fan.slashdot and have the discussions a lot easier to read with your favorite newsreader?