Print Style Sheets and URLs
Published on June 14, 2011 (↻ February 5, 2024), filed under Development and Design (RSS feed for all categories).
This and many other posts are also available as a pretty, well-behaved ebook: On Web Development.
Print style sheets are awesome. They’re easy to write, too. Site owners and developers who care about print typically know what to do. Alas there’s one thing that’s done rather the wrong than in any right way: printing URLs, typically via the content
property.
Figure: I’m (https://example.com/) so glad (https://example.com/happiness) we’re talking about this (https://example.com/present).
Popular Mistakes
Two.
-
Not obtaining any data on how many users actually print out documents and go to the length of memorizing or writing down URLs they saw on the print-out to then type those URLs into the next machine they find. (There may be neither users who do that nor data to prove it.)
-
Displaying URLs in the wrong context, namely copy text (see the figure above). While one may maintain some optimism that URLs are actually accessed later, expanded in regular text they do but one thing—disrupt the reading flow.
In other words, don’t expand URLs in print because you can. Then, as always, exceptions prove the rule: Special forms of content like link lists, for example, can still benefit from expanding all URLs in print; important URLs may even want to be shown on screen. We just need to exercise caution.
About Me
I’m Jens (long: Jens Oliver Meiert), and I’m a frontend engineering leader and tech author/publisher. I’ve worked as a technical lead for companies like Google and as an engineering manager for companies like Miro, I’m a contributor to several web standards, and I write and review books for O’Reilly and Frontend Dogma.
I love trying things, not only in web development (and engineering management), but also in other areas like philosophy. Here on meiert.com I share some of my views and experiences. (Be critical, interpret charitably, and send feedback.)
Comments (Closed)
-
On June 14, 2011, 11:40 CEST, Leon said:
Yes, it’s always a disappointment to find a site which consists of lots of articles neglecting print styles; as you say, it’s not difficult to implement.
Still, if you do find such a site, I’ve found the readbility plugin useful. It has a print button and produces a nicely formatted document.
-
On June 14, 2011, 16:57 CEST, a Mint.com user who wishes that site used print style sheets said:
if you wanted a project that unhappy users would probably kick in some money to pay for, the Mint.com money management site (owned by Intuit) doesn’t have a print style sheet, an epic fail for a personal money management site where people will want to print out reports.
-
On June 15, 2011, 17:27 CEST, Ben Buchanan said:
At a previous job a coworker came up with a solution that created numbered footnotes with the URLs. It’s a nice balance between losing the data and making the text hard to read.
-
On June 15, 2011, 17:32 CEST, Jens Oliver Meiert said:
I’ve seen such solutions, some of them quite smart, but they’ve usually been a pain with quite a toll on the markup. Did your coworker happen to write about or publish the solution?
Read More
Maybe of interest to you, too:
- Next: On Semantics in HTML
- Previous: Web Development Principles: Develop for What Is, Not What Could Be
- More under Development or Design
- More from 2011
- Most popular posts
Looking for a way to comment? Comments have been disabled, unfortunately.
Get a good look at web development? Try WebGlossary.info—and The Web Development Glossary 3K (2023). With explanations and definitions for thousands of terms of web development, web design, and related fields, building on Wikipedia as well as MDN Web Docs. Available at Apple Books, Kobo, Google Play Books, and Leanpub.