Help Beta Test Slashdot CSS

After almost 8 years, Slashdot's HTML is finally getting an overhaul. For now the changes are almost entirely under the hood, as we migrate the current skin to CSS. Slashdot itself will migrate in the next few weeks, but for now, we'd appreciate it if people who understand CSS could take a look at Slashcode. If you use a browser that lets you select a stylesheet, you can take a look at that site with the Slashdot CSS Skin. Keep in mind that Slashcode doesn't look exactly like Slashdot, so there will be some differences between that site, and the final version that will appear on Slashdot. We're mainly looking for feedback on compatibility issues and blatant bugs. You can use our our SF bug tracker to submit bug reports. Thanks for your help. Once we move Slashdot, work will begin on a new look & feel. If you have ideas, you could start playing with the CSS stylesheets now!

Comments

next you'll be telling us

[Anonymous Coward]

you fixed the american flag icon with the wrong number of stripes.

Wonderful

[Master of Transhuman]

Now the dupes will be prettier.

Is there such a thing as CSS for Zonk?

Times New Roman SUCKS!!!

[ndrtkr]

Get rid of it please!!!
Bring Verdana or something more pleasant in...

Re:Who is Making the Changes?

[eno2001]

Before you start criticizing people who do this stuff for a living, why don't you wake up and smell the coffee? In case you're not aware, there have been a lot of developments in content management systems since Slashcode was created. A lot of the innovation (thanks to Sharepoint Portal and Frontpage) has happened on the Windows platform where completely overhauling a site is something that can be accomplished in minutes by any decent Windows admin. Hell. You don't even need coders, or HTML designers. All you need is to train your network admin on the use of FrontPage and provide him with a decent media library to choose looks and feels from. But, since you and your buddies here are stuck in the bad old days where everything is tweaked in a text based config file, you've got to make a big deal out of this switch to CSS and claim that it's a big event. It's not and it shouldn't be treated as such. It's just another document and if you really know what you're doing, you'll be able to make the changes from within MS Word. The key is to cut non-essential staff (all Unix admins are non-essential these days). But you keep trying to drag us back to 1970. We'll get you eventually. It's only a matter of time.