24 Oct 2006 12 pm eastern

Better community through printing

Readers read web pages. Readers print web pages. In 1999, the way to help readers print web pages was obvious to every major site owner: buy a proprietary, multi-million-dollar content management system avec service contract to generate multiple versions of every page. After all, you needed seven versions of every page to handle all the browsers out there; you might as well treat print the same.

In 2001, A List Apart started promoting print style sheets, and by 2003, all the cool kids were doing it. They were also mostly using free or low-cost, generally open-source, content management systems. Yay, open source! Yay, web standards!

But a problem remains: all those ponderous 1999 websites have trained readers to expect a “print this page” button and subsequent in-browser preview. How can you satisfy this basic user expectation while still enjoying all the benefits of web standards?

In Issue 226 of A List Apart, for people who make websites, Pete McVicar shows one very good way to do it. His “Print to Preview” combines alternate stylesheets and scripting to…

show how the page will look when it’s printed, perhaps display a preview message explaining what this new view is about, and then automatically print the page.

McVicar’s method isn’t the only way to do this—others will likely be mentioned in the comments—but his technique is straightforward and clean, and it takes care of users without making the mistake of trying to educate them about something in which they’re profoundly uninterested (namely, web development).

Also in this issue: “How to be a Great Host,” by John Gladding. These days, many people’s web business plan looks something like this: “Ajaxy goodness + ???? = Profits!” Other straw men seem to think five blog posts plus text ads by Google plus discussion board software guarantees a buyout by Google. It doesn’t.

Building a community takes time and work. No amount of social bookmarking and tagging can rush that process. But you can learn to avoid mistakes. And you can save time by following time-tested approaches. (Learning from your mistakes is overrated.) Gladding’s article is filled with smart, “first do this, then do that” tips that can help you grow your site’s audience with discussion that works.

Better printing. Better community-building. Better read A List Apart 226!

Tags: , , , , ,

  • Twitter
  • Facebook
  • del.icio.us
  • Digg
  • Google Bookmarks
  • NewsVine
  • RSS

Filed under: A List Apart, Blogs and Blogging, Design, Publishing, Standards, Tools, development

7 Responses to “Better community through printing”

  1. Mau said on

    That little media="print" string is indeed one of the coolest things that web standards have given to humankind.

  2. f berriman / blog said on

    Kramer auto Pingback[...] As if by magic, Jeffery Zeldman yesterday published an article about print style sheets, which just happened to be what I was tangentally ranting about in the car on the way to work the other morning. Most of us support printers about as badly as we support screen readers, and I don’t think the two devices are that far removed – both are mostly “out of sight, out of mind”. [...]

  3. Johan said on

    what about pdfs for print?

  4. Dominic Dirupo said on

    It is criminal to have a website that doesn’t print correctly, custom-designed or otherwise. Yahoo should hang their head in shame for this reason alone.

  5. Greg said on

    what about pdfs for print?

    Why, though? It seems like it’s adding an extra layer of hassle for the user, having to open Acrobat instead of printing from the browser. Not to mention the difficulty of dymanically generating PDFs compared to writing a print style sheet.

  6. Tuesday, 24. october 2006 | WDNews.net said on

    Kramer auto Pingback[...] Better community through printing [...]

  7. fberriman » Developing for others said on

    [...] if by magic, Jeffery Zeldman yesterday published an article about print style sheets, which just happened to be what I was tangentally ranting about in the car [...]

Speak up!

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

- Why ask? This confirms you are a human user!