A List Apart

Menu Issue № 165

Retooling Slashdot with Web Standards Part II

by Daniel M. Frommelt · 23 Comments

In Part I, we showed how Slashdot could save money and reduce bandwidth requirements by converting to semantic XHTML markup and CSS layout. In Part II, we explore how standards-compliant markup and deft use of CSS could make Slashdot and your sites play nicely in print and on handheld devices.

More from A List Apart


Rian van der Merwe on A View from a Different Valley

The Analog Revolution

Back in the day, when software was released (on physical media), it was considered done. In the present, some products could benefit from a limitation like that. To tie development to something immutable, such as a physical thing or a hard deadline, might just foster a sense of responsibility to design our product so it has what it takes to last a few years.

From the Blog

It’s Time We #FEDtalk

One person focuses on HTML, CSS, and JavaScript. Another writes JavaScript tests all day. And they both have the same job title: front-end developer. Mat Marquis talks about why that’s okay, and introduces our latest event, "The State of Front-End Dev."

Writing to Think

It's true, writing about your work can be tough. Putting your thoughts out there for everyone to see—and comment on—can be intimidating. But, as Susan Robertson shows, it's a great way to clarify your thinking on tough problems, and can lead to new opportunities in the process.