More Links Of This Posts:
This guide is especially handy if you haven’t done a lot of webdesign yet or if you are involved in webdesign but don’t do any of the real work. I hope to shed some light on some common interface elements and mistakes people often make with them.
A lot of books have been written in the past but the threshold for reading them, especially if you have never built a site, is quite big, hence this short guide. This is by no means a complete guide or solid set of rules, but it is definitely a good start.
Written by Aaron Cannon, blind web developer and accessibility consultant.Aaron explains in his article “The Accessibility Checklist I Vowed I’d Never Write”, that the problems with a “simple checklist that, when followed, will give you an accessible site without fail.” No such checklist exists or likely ever will. He believes that this list is not the perfect solution, nor is it the only solution, but believes it is a good first step, and it gives our developers and designers a place to start from.
A CSS System is a reusable set of content-oriented markup patterns and associated CSS created to express a site's individual design. It is the end result of a process that emphasizes up-front planning, loose coupling between CSS and markup, pre-empting browser bugs and overall robustness. It also incorporates a shared vocabulary for developers to communicate the intent of the code.
This ebook elaborates on this concept, and also describes a number of tricks used to preempt maintainability issues.
One aspect of designing for the web that almost immediately offends designers is the lack of fonts that are considered safe to use. While it is true that there are only a handful of web safe fonts, the ones we do have at our disposal can be quite powerful and diversely useful. On top of that, CSS gives us a nice little thing called a font stack.
Font embedding for the web is a great step in making the web look better and become more functional, but what about security and load times?
Bram Pitoyo’s ebook takes the top layer off font embedding and shows us how things work, and ultimately how to improve performance and make it more secure.
This book was originally written in 2001 for print designers whose clients want websites, print art directors who’d like to move into full–time web and interaction design, homepage creators who are ready to turn pro, and professionals who seek to deepen their web skills and understanding.
The dot-com crash killed this book. Now it lives again. While browser references and modem speeds may reek of 2001, much of the advice about transitioning to the web still holds true.
Put simply this book is the result of a series of emails sent back and forth between the two authors during the development of a library for the .NET framework of the same name. The conversation started of something like "Why don't we create a more aesthetically pleasing way to present our pseudocode?"
After a few weeks this new presentation style had in fact grown into pseudocode listings with chunks of text describing how the data structure or algorithm in question works and various other things about it. At this point we thought, "What the heck, let's make this thing into a book!"
Topics