commonly used features in a side-by-side format

Database of HTTP status codes with their IETF and Wikipedia descriptions. Maintained by @citricsquid. Submit changes/corrections/comments via twitter or email.

Look up HTML5, CSS3, etc features, know if they are ready for use, and if so find out how you should use them – with polyfills, fallbacks or as they are.

How do I not already have this bookmarked?

Compatibility tables for features in HTML5, CSS3, SVG and other upcoming web technologies

These pages are provided as an outline for GRPH: 210 Typography. At right you will find links to the material covered each week throughout the course, as well as links to each weeks assignments, distributed via Adobe PDF files. Though this site is updated frequently, all materials and assignments are subject to change at Instructor’s (Todd Roeth’s) discretion.

Now that the Library of Congress and NASA and the New York Public Library all have their collections online, there are more copyright-free pictures around than you can shake a stick at.

Float is a CSS positioning property. If you are familiar with print design, you can think of it like an image in a layout where the text wraps around it as necessary. In web design, an image that is floated remains a part of the flow of a web page. That means that if it changes in size or if the elements around it change, the page will automatically adjust (reflow). This differs from page elements that are absolutely positioned. Absolutely positioned page elements are removed from the flow of a web page. Absolutely positioned page elements will not affect any other page elements, whether they touch each other or not.

There are two problems here. The first is that until HTML 4 came along, the web was missing almost all of these tools (it’s still missing many important ones).

But the larger problem is, now that they’re available, almost no one publishing on the web today knows how to use them—or often even knows of their existence.

Read this, though, and you’ll understand the answers to both problems far better than almost anyone else, including your English teachers.

In order to deal both with content written according to Web standards and with content written according to legacy practices that were prevalent in the late 1990s, contemporary Web browsers implement various engine modes. This document explains what those mode are and how they are triggered.

How to Size Text in CSS
by Richard Rutter

But Box Lessons didn't become a obscure historic artifact like it should have. Instead it's still a major starting point for thousands, and that leaves me with a bit of a problem. I simply don't have time to write a modern version, yet I'd be complete jerk to remove it just to save myself some embarrassment. Whatever I might happen think of the BL, it's still the all-important leg up for so many.

Hence this warning and explanation.

You're still most welcome to peruse the Box Lessons. Obviously it helps people in ways that I don't realize. Just please keep your eyes open. The reasons offered for WHY things are done are still good and will remain so. But almost all the browser workarounds listed here are useless today. You just don't need that stuff.

Please feel free to borrow, steal, abduct, and/or torture the documents contained in the Layout Reservoir. Though you need not give credit to BlueRobot.com, a comment in your source code would help other developers to find this resource. Enjoy.

POSH encapsulates the best practices of using semantic HTML to author web pages. Semantic HTML is the subset of HTML 4.01 (or XHTML 1.0) elements and attributes that are semantic rather than presentational. The best way to learn and understand POSH is to do it. Pick a page on your web site to begin with, and apply the POSH Checklist to it. Continue with the POSH Process. Read POSH Resources to learn more about POSH.

The pages listed here contain tests and experiments about features, possibilities, browsers’ bugs regarding CSS.

The following is NOT the Web Content Accessibility Guidelines (WCAG) 2.0. It is, however, a simple checklist that presents our recommendations for implementing HTML-related principles and techniques for those seeking WCAG 2.0 conformance. The language used here is significantly different from the official WCAG 2.0 specification (http://www.w3.org/TR/WCAG20/) to make it more easily implemented and verified for web pages.