I've been meaning to post some books about design and user experience (UX)that I thought you might be interested in. There are many fine booksout there that you can read about UX and many that I have not readmyself - feel free to post your own suggestions here. My intent is notto make you a designer, but to provide you with some materials thatwill make your development projects better, whether you are inclinedtowards design or you are a developer.
InsideLotus - Lotus, Portal and Social Collaborative Software
Matching: design X
TedStanton 0600014754 Tags:  web design collaboration portal domino blog programming 2 Comments 3,724 Views
Lets bring the debate to Lotus customers. I'm not just talking about the large Lotus blogging community, but really looking for feedback on a strategic direction IBM should get involved in around syndication. The two most common methods to syndicate information are RSS 2.0 and Atom 1.0. While it is perfectly acceptable to use both of these methods, the past technologies will tell us that eventually one of these methods will prevail and be the standard. Whatever method is chosen, is usually based on the more advanced technology that has the ability to expand and grow as Web 2.0 evolves and continue growth into the 3rd generation of the internet.
While RSS is more commonly known and used by internet sites today, the code has been frozen so there does not seem to be growth within this syndication method. Some people view that as a weakness while other agree in freezing the code so that it does not become a complicated technology. On the other hand you have Atom. Another method of syndication that is designed to expand with technology. As Atom expands, so will it's complexity which may turn the avid user away from Atom and use a more simple method such as RSS.
P.S. RSS capabilities coming to Notes and Domino this fall.[Read More]
As a follow on to last Wednesday's post on CRAPy design, check out this new blog, Interface | matters, devoted to user interface design for Notes and Domino - written by Chris Blatnick.
User expectations have come a long way since Notes first came out. Make your apps, even the simplest ones, look good AND be functional. Don't make them, what I call - Dugly -> Developer-ugly. You know, the yellow background color, just to have something, giant buttons placed haphazardly on a form, action bars that provide actions you actually aren't allowed to use, etc, etc.
Chris Reckling, etc, etc...
I love a catchy headline! via Ned, this is a good, to the point, article about good web design. If you are one of those developers with no sense of style, then this quick read will get you on track, even if you don't see the difference between 12pt and 14pt fonts (or, at least, aren't bothered by having both in the same sentence).
How C.R.A.P is Your Site Design?
The acronym stands for Contrast Repetition Alignment Proximity. I would add Simplicity to that list, making it C.R.A.P.S. You can take that any way you like! The idea for me is to understand what the user is after in visiting your site, whether it's to read the news, do a search, or to buy something. These design guidelines help achieve those goals and don't let the design get in the way of the message (unless you want it to, of course).
I would be interested in how people apply these principles to a portal design scenario. For instance, as you add portlets to a page, it can really mess with the Alignment principle, when you have the portlet title bar and different content within each portlet body. The only solution might be to limit the number of portlets, or design the page so that you have a navigation area on the left or top, then a large area for content, and perhaps a smaller column on the side for narrow content. Any more columns than that for portlets and you run into a messy looking page. Thoughts?
As an aside, I wish he would have included, as a guideline, the annoying tendency these days for site designers to think that we really want to look at half a page worth of graphics, navigation, and banners, but no content, at the top of a page. If your banner takes up more than about 100 pixels at the top, you need to change it.
That's it for now - enjoy the article.
Sr. Product Manager, Application Development Tools