So we know there’s a backlash of the list article format going on. And we know that the general cure to the “disease” is to go for quality, not quanity. Discussions instead of a bombardment of links and screen grabs. Though of course, that’s debatable since if I’m a designer looking for these resources in the first place, I’d find them indispensable anyway.
The thing is though, if I am looking for that perfectly tiled background pattern or that brilliant CSS3 button tutorial, how do I scour through oodles of these lists to find exactly what I need? How would I know from my list of bookmarks or starred Google Reader items that the blog post titled “50+ Fresh CSS Techniques, Tutorials and Resources” is the one I need, and not “5 Useful Coding Solutions For Designers And Developers”? These titles are super vague and because the posts are super long, it’s now finding a needle in a haystack.
List article authors need to raise the stakes and add more useful features. A table of contents, for example, that summarizes all the items in the list. Tags too, that should describe the article with keywords as specific as possible.
Perhaps someone can even create an aggregator of these lists, with proper categorization and search. It could even be—gasp—the next “CSS gallery”.
Why fan the flames and tolerate list articles? Again, I know what they’re useful for. They’re a convenient way to check up on what’s new in the design blogosphere, and you can never have too many resources. They’re certainly taking up space for thought-provoking discussions, but the demand is high and we need them too. We might as well rally to improve the format instead of banish it.
The same goes for CSS galleries and image bookmarking sites. I welcome the large amount of sites because sometimes you can never have enough. But how I browse through and experience their content can definitely be improved.
I’m not just talking about aesthetics or readability here. I’m talking about what can be considered new forms of content with sub-content that can describe and classify them:
- the list article as a type of resource list that contains different downloadable files (e.g., brushes, vectors, photos), tutorials, screenshots, etc.
- the CSS gallery as a type of website list that contains different websites classified according to style, site type, color, CMS, topic, number of pages, designer, etc.
- the image bookmarking site as a type of image list that contains different images classified according to style, image type, color, resolution, designer, etc.
Is it possible to create new content formats for these? People have managed to do so many things with Twitter tweets, and Microformats are moving forward at a steady pace, so why not see if we can remix and mashup larger types of content, like ones contained in blog posts?
One of the biggest problems on the Web is that we’re marking things up on such a low level, while tapping into XML structures isn’t as easy to do yet. But imagine if we can make all these resources so much more organized and findable. Maybe people wouldn’t need to complain about list articles and CSS galleries as cliches then.
Google is throwing its own hat into the web fonts ring with the Google Font Directory and the Google Font API. While it appears it doesn’t have any partnerships with the big names in typography like TypeKit does, just a handful of open fonts, it does have a partnership with TypeKit itself (as you’ll see below).
How the Google Font API works
Once you pick a font, you can embed it on a webpage by grabbing code that looks like this:
<link href='http://fonts.googleapis.com/css?family=Josefin+Sans+Std+Light' rel='stylesheet' type='text/css'>
And use it in your stylesheet like this:
h1 { font-family: 'Josefin Sans Std Light', arial, serif; }
You can also use other fonts using the WebFont Loader, which is a JavaScript library developed by Google and TypeKit.
Bane or Boon?
Although I won’t be ditching Font Squirrel anytime soon, one great thing about this new development is that the fonts are hosted on the most reliable servers in the world, just like the different JavaScript libraries are. The even greater thing is that this is Google, one of the strongest forces on the Web, is placing a stake another aspect of web standards.
Of course those things are scary at the same time. Google can just pick any endeavor under the sun, spend resources on it, and possibly dominate, if not dictate the market in no time. It may not get the purist designer types on board, since Google doesn’t exactly have the best reputation for great design, and its presentation has a bit of a developer slant, but it knows its web design technologies well. And in the case of web standards, where new practices are being adopted and old browsers are being discarded at a snail’s pace, Google’s massive resources and influence can only do well to speed things up.
Dribbble is just one approach to the feedback web app “genre”; I’ve noticed that they’re making it easier than ever to receive and leave feedback on designs, as you’ll discover when you go down this list:
Usabilla
Usabilla has the most features out of the lot, letting you test both images and live websites with click markers, notes, and heatmaps. There’s a free plan but you’ll enjoy more test participants and pages with the premium plans.
ConceptFeedback
ConceptFeedback anchors on a thriving community and and offers special perks for both individual designers and businesses, including compensation for giving feedback. Not only can you get reviews for your current work and inspiration for your next one, your profile, design, or product can get featured to earn better exposure and business—but you need to jump in with both feet and register.
fivesecondtest
As the name implies, fivesecondtest focuses on first impressions as a test-takers look at designs for no more than five seconds and answer custom questions from test-makers. This means judgments can be rash, but the barrier to entry is very encouraging. For extra good measure, the app runs on a karma system where the more tests you do, the more test results you can make.
FineTuna
The Flash-based FineTuna creates a link for every image you upload, which you can send to specific people for feedback. That link is a space where one can insert notes and doodle on the image. You won’t have a community of users at your disposal, but you have complete control and privacy over the feedback process. It’s also available as a Firefox add-on.
CritiqueTheSite
CritiqueTheSite uses hackable URLs, iframes, and JS-Kit’s Echo to let visitors leave comments on a currently loaded site. Append a URL of any website (like Aviary Screen Capture does) after the slash and it loads that site, ready for critique. Public, no-registration-necessary feedback makes the service prone to abuse, but it also means it has a low barrier to entry.
No clear winner here!
If you want a more detailed level of testing, Usabilla is the way to go; if you need something lighter and more accessible, the likes of CritiqueTheSite, FineTuna, and fivesecondtest may be better for you. If you’re all about building your reputation and relationships as an added bonus, pick ConceptFeedback. Or why not use all of them? Using all these tools for online critiquing lets you reap the unique benefits for each.
So Mark Boulton decided to release his book, A Practical Guide to Designing for the Web, online and without cost. It’s not the only web design book available for free on the web, which this list and a previous encounter with two other online books prove, but all of them make me wonder, again, about the electronic book format.
In the examples above, said “books” don’t adapt official e-book formats, but stick with plain old semantic HTML and PDFs. Joe Clark, in an A List Apart article, explains that both standard and proprietary e-book formats are just more specialized versions of HTML/XHTML, so is there anything gravely wrong with creating webpages instead of actual e-book files?
As one who knows her way around HTML, taking an extra step into e-books (e.g. ePub) feels clunky and unnecessary. However, that is hasty judgment without first considering factors like audience. For web design books, perhaps it makes more sense to not bother with anything else and keep them as webpages because web designers work on sites all day long. That’s not to say they wouldn’t enjoy reading web design books in their e-book readers, but they may mind less having a book in one tab alongside other web design resources in other tabs.
Using proper formats also seems like a natural extension of web standards philosophy. If one were to publish a book online, why not go for the suitable format? There are scripts, extensions, and converters available. And with the ePub Zen Garden following in the steps of the CSS one, it may become the next worthy cause to root for.
*/
