HOHOHO on 2006-08-04
just testing diigo
This link has been bookmarked by 152 people . It was first bookmarked on 02 Mar 2006, by Torsten Rox.
-
Stanton TetersGuidelines for chunking user interface areas and designing the usage of those.
-
Brent SordylThe biggest challenge for web designers is the unthinkably huge number of possible ways to solve any given problem.
-
-
The biggest challenge for web designers is the unthinkably huge number of possible ways to solve any given problem
-
-
-
So this includes what info the page should get across, what actions it should support, important attitudes of the users, and so on. Do not prioritize, group, or categorize.
-
Put the bits into chunks based on whether they impact each other — not based on any conceptual or graphic ideas.
- 1 more annotations...
-
-
Jon AstonWow! What a terrfific approach!!
-
-
An Introduction to Using Patterns in Web Design
-
-
-
-
To make better sites â sites that are functional, beautiful, and "usable" â we have to break our design problems up into small independent chunks based on the real issues within our requirements. Christopher Alexander, who came up with this stuff, calls these chunks patterns.
-
To make better sites â sites that are functional, beautiful, and "usable" â we have to break our design problems up into small independent chunks based on the real issues within our requirements. Christopher Alexander, who came up with this stuff, calls these chunks patterns.
-
-
-
I'm going to show you how to sidestep your habits and assumptions and use patterns to make better design decisions. A lot of fancy stuff has been written about patterns. To be simple and clear in this introduction, I'll just call them chunks.
-
-
Carol Isaksonbreak old habits by chunking info first
-
-
An Introduction to Using Patterns in Web Design
by Ryan Singer, October 5 2004
The biggest challenge for web designers is the unthinkably huge number of possible ways to solve any given problem. We usually don't think of this because we have our habits and traditions to fall back on, but there are literally billions of possible pixel combinations for each page we make.
There is a better way to manage this vast complexity than by making big decisions up front and hoping for the best. To make better sites — sites that are functional, beautiful, and "usable" — we have to break our design problems up into small independent chunks based on the real issues within our requirements. Christopher Alexander, who came up with this stuff, calls these chunks patterns.
I'm going to show you how to sidestep your habits and assumptions and use patterns to make better design decisions. A lot of fancy stuff has been written about patterns. To be simple and clear in this introduction, I'll just call them chunks. -
An Introduction to Using Patterns in Web Design
by Ryan Singer, October 5 2004
The biggest challenge for web designers is the unthinkably huge number of possible ways to solve any given problem. We usually don't think of this because we have our habits and traditions to fall back on, but there are literally billions of possible pixel combinations for each page we make.
There is a better way to manage this vast complexity than by making big decisions up front and hoping for the best. To make better sites — sites that are functional, beautiful, and "usable" — we have to break our design problems up into small independent chunks based on the real issues within our requirements. Christopher Alexander, who came up with this stuff, calls these chunks patterns.
I'm going to show you how to sidestep your habits and assumptions and use patterns to make better design decisions. A lot of fancy stuff has been written about patterns. To be simple and clear in this introduction, I'll just call them chunks. - 1 more annotations...
-
-
-
The biggest challenge for web designers is the unthinkably huge number of possible ways to solve any given problem...There is a better way to manage this vast complexity than by making big decisions up front and hoping for the best. To make better sites — sites that are functional, beautiful, and "usable" — we have to break our design problems up into small independent chunks based on the real issues within our requirements. Christopher Alexander, who came up with this stuff, calls these chunks patterns.
-
-
-
I'm going to show you how to sidestep your habits and assumptions and use patterns to make better design decisions. A lot of fancy stuff has been written about patterns. To be simple and clear in this introduction, I'll just call them chunks.
-
-
-
There is a better way to manage this vast complexity than by making big decisions up front and hoping for the best. To make better sites — sites that are functional, beautiful, and "usable" — we have to break our design problems up into small independent chunks based on the real issues within our requirements. Christopher Alexander, who came up with this stuff, calls these chunks patterns.
I'm going to show you how to sidestep your habits and assumptions and use patterns to make better design decisions. A lot of fancy stuff has been written about patterns. To be simple and clear in this introduction, I'll just call them chunks.
-
-
-
An Introduction to Using Patterns in Web Design
by Ryan Singer, October 5 2004
The biggest challenge for web designers is the unthinkably huge number of possible ways to solve any given problem. We usually don't think of this because we have our habits and traditions to fall back on, but there are literally billions of possible pixel combinations for each page we make.
There is a better way to manage this vast complexity than by making big decisions up front and hoping for the best. To make better sites — sites that are functional, beautiful, and "usable" — we have to break our design problems up into small independent chunks based on the real issues within our requirements. Christopher Alexander, who came up with this stuff, calls these chunks patterns.
I'm going to show you how to sidestep your habits and assumptions and use patterns to make better design decisions. A lot of fancy stuff has been written about patterns. To be simple and clear in this introduction, I'll just call them chunks.
Step one: List your bits
Start by making a list of all the specific bits that must fit together for the web page to succeed as a whole. By "bits" I mean any kind of design consideration. So this includes what info the page should get across, what actions it should support, important attitudes of the users, and so on. Do not prioritize, group, or categorize. If you start by grouping and organizing you'll just end up with your original habits and preferences in the end.
Here are the bits for a "My Account" page that I recently designed:
1. Company info
2. Insurance info for company
3. My (current user) info
4. Other users on this account
5. My sales rep contact info
6. Current account plan
7. Link to change search preferences
8. Date account was created
9. People rarely view or change insurance info
10. Any user can edit anything except other users' info
11. Changing password is the most likely action
12. People might come here to change se
-
Public Stiky Notes
Page Comments
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.