University Web Developers

University Web Developers

I'm curious if anyone has guidelines or recommendations for best practices for print style sheets. We don't really have anything in place yet so I'm starting from scratch. I'm putting together a quick & simple sheet for one project but I would rather get it right so I can use this on the whole site eventually. Mainly so far it has been a project that points out all of the early mistakes I made when I designed our current site template.

Views: 178

Replies to This Discussion

We've hidden extraneous nav elements in our print CSS:
http://www.fredonia.edu
Here is an excellent article on print styles: http://www.alistapart.com/stories/goingtoprint/

What we do is eliminate nav elements and unnecessary images. We don't have a separate css page, but rather when we link to the stylesheet we use media="all". Within the stylesheet we do this:

@media print {
body {
background: white;
font-size: 12pt;
}
....
}

This eliminates an extra server hit.
Excellent advice. Thank you!
No problem!
This is initially what I planned to do on our new Web site, but I realized that quite a few of our users actually want to print things the way they look on the screen. Therefore, rather than just implementing a print stylesheet or using the print media declaration in our standard stylesheet, I went ahead and built a "printable" template for the site.

I know that some people consider that sort of old-school, but it's actually good practice.

Print stylesheets, by themselves, break one of the cardinal rules of good Web practices - they perform an action (in this case, reformatting the page) without the user asking it to do so. While it's not nearly as unnerving or annoying as playing music or resizing a browser window without the user explicitly choosing to do so, it's still a bad idea.

That's my opinion, anyway.
I understand your point and agree with it somewhat. However, in our case print styles include all of the content that the page normally contains plus adds to it in most cases. For instance (can't take credit for this...again, check out Eric's article),links show the url on most of our print pages.

It would be interesting to see what percentage of people would prefer to print what they see on the screen. Most of the time when printing what what the user sees it turns out messy when going to the printer plus web fonts don't necessarily make very legible print fonts. It almost seems to me that we should push for this (kind of kidding IE5 goodbye).

I wouldn't agree that it breaks one of the cardinal rules of good web practices. Printers are very different from screens and needed to be treated as such. I don't want a printer to print my black background with white text, for instance. I would be pissed if that happened to me and some designer / developer didn't account for that.

If a user wants what is on the screen they need to learn how to take screenshots ;)

Sorry if this comes across as harsh...i've been told that my replies on forums usually are. It's just my opinion.
Not harsh at all.

I see where you're coming from, and I agree to a certain extent. However, there are a few factors you have to take into account when making a decision like this:

1) How much are you planning to (or will you need to) change the page in order to make it presentable on a printer. - If you are planning to radically change the layout (such as removing the navigation, logos, etc.), you might not want to do all of that automatically. If you are just adjusting things like fonts, backgrounds and floats, then a print style sheet is probably ideal (especially since certain floats actually cause IE to freeze up when trying to print).

2) Who is your target audience? - If you're dealing with a mostly tech-savvy crowd, then using a print style sheet probably isn't a big problem. However, the less accustomed to the Web your target audience is, the less you want to do without them understanding why you did it.
I learned something new. That's pretty nifty, so in one master stylesheet, you're essentially nesting your styles within media rules? Have you tried it with @media handheld? or any other medias? And this works in all browsers?

^_^
It works in all browsers I have tested (IE6, 7, Safari, Opera, FF). I actually got the idea from Neal Grosskopf at http://www.nealgrosskopf.com. If you look at his stylesheet, you'll see that he embeds @media and @aural as well (http://www.nealgrosskopf.com/files/css/all.css).

So, yeah, I usually have one master stylesheet with everything in it. It's easier for me to go back to, and I don't have as many hits to the server then.
I would suggest taking out any elements that are only relevant to the web and concentrating on formatting the text so that it is simplified and makes since when printed. As it was mentioned before you can do at @media print and source a stylesheet to accomplish this. The easiest way to drop elements or tighten the page up on print is to just add a display: none; string too those divs in which you want to omit from the printing process. Example:

#advertisement {display: none;}

A List Apart does do a very good job about formatting the text.
Other than the usual -- setting the background to white, hiding nav, unfloating columns; I usually set the font to a larger serif font - because that's easier to read in print.

I also always add this little tidbit -- which prints out the URLS of links:

a:link:after, a:visited:after {
content: " (" attr(href) ") ";
font-size: 90%;
}
a[href^="/"]:after {
content: " (http://www.yourdomain.com" attr(href) ") ";
}
Thanks the link to the Dave Walsh script as well as your colleague's. I haven't worried about IE6 not printing out urls before, but perhaps I should.

RSS

Elsewhere

Latest Activity

Rachel Mele commented on Lynn Zawie's group OmniUpdate
"Fundamentally, a CMS allows you to publish and manage content for your website—but it has the capability to do so much more. "
yesterday
Rachel Mele commented on Lynn Zawie's group OmniUpdate
"Don’t begin a website redesign without first considering these trends! "
Tuesday
Rachel Mele commented on Lynn Zawie's group OmniUpdate
"Speaker call for proposals for #OUTC19 is officially open! "
Monday
Rachel Mele commented on Lynn Zawie's group OmniUpdate
"There’s a high school student who is a great fit for your institution, yet never engages with your institution online and enrolls elsewhere. Why? Find out during our next webcast with Lance Merker as he dives into the 2018 E-Expectations Trend…"
Aug 10
Rachel Mele commented on Lynn Zawie's group OmniUpdate
"Your website needs a redesign and the project is catching momentum. Woohoo! But wait… have you considered your school’s IT needs and concerns? #StartWithTheCMS"
Aug 10
Rachel Mele commented on Lynn Zawie's group OmniUpdate
"Now available for free download! "
Aug 8
Profile IconMiesha, Megan Gonzalez and Aaron Claycomb joined University Web Developers
Aug 8
Rachel Mele commented on Lynn Zawie's group OmniUpdate
"Everything that prospective students want to know about your college or university is at their fingertips. So what happens if they don’t find the info on your website?"
Aug 7
Rachel Mele commented on Lynn Zawie's group OmniUpdate
"Knowing common terms will make it easier to talk all things design related. "
Aug 2
Rachel Mele commented on Lynn Zawie's group OmniUpdate
"Directories should be easy to find on your website and easy to navigate. Here’s a showcase of schools with great faculty and staff directories: "
Jul 31
Rachel Mele commented on Lynn Zawie's group OmniUpdate
"Is your digital presence not up to par? Maybe it’s time to #StartWithTheCMS."
Jul 27
Rachel Mele commented on Lynn Zawie's group OmniUpdate
"Ready to optimize conversions on your website? "
Jul 25
Monique George is now a member of University Web Developers
Jul 23
Rachel Mele commented on Lynn Zawie's group OmniUpdate
"OU Mashup v2 is chock-full of features designed especially for higher ed. See what’s new! "
Jul 20
Rachel Mele commented on Lynn Zawie's group OmniUpdate
"Feeling overwhelmed about the idea of redesigning your college or university website? We’ve got you covered in our latest white paper! "
Jul 18
Rachel Mele commented on Lynn Zawie's group OmniUpdate
"Our OU Campus CMS allows you to prevent your content contributors from publishing a page unless it meets your preset accessibility requirements. "
Jul 13
Rachel Mele commented on Lynn Zawie's group OmniUpdate
"Another win for our customer support and training teams! "
Jul 12
Rachel Mele commented on Lynn Zawie's group OmniUpdate
"What’s going on behind the scenes with your website? That’s what the Workflow Gadget in our OU Campus CMS is designed to track. "
Jul 6
Rob Peterson is now a member of University Web Developers
Jul 5
Rachel Mele commented on Lynn Zawie's group OmniUpdate
"Aligning your website with visitor intent is key. Join Matt from Ruffalo Noel Levitz in our next webcast about how to structure IA to connect with prospects."
Jul 2

UWEBD has been in existence for more than 10 years and is the very best email discussion list on the Internet, in any industry, on any topic

About

© 2018   Created by Mark Greenfield.   Powered by

Badges  |  Report an Issue  |  Terms of Service