- Accidental Creative
- Adapting to Web Standards: CSS and Ajax for Big Sites
- Art of Non-Conformity
- Art of Readable Code
- Back to the User: Creating User-Focused Web Sites
- Beginning PHP6, Apache, MySQL Web Development
- Books to Read
- Born For This
- Complete E-Commerce Book
- Core PHP Programming
- CSS3: Pushing the Limits
- Dealing with Difficult People
- Defensive Design for the Web
- Deliver First Class Web sites
- Design for Hackers: Reverse-Engineering Beauty
- Designing Web Interfaces
- Designing Web sites that Work: Usability for the Web
- Designing with Progressive Enhancement
- Developing Large Web Applications
- Eat That Frog
- Economics of Software Quality
- Elements of User Experience
- Extending Bootstrap
- Flexible Web Design
- Flexible Web Layouts
- jQuery Pocket Reference
- Letting Go of the Words
- Manage Your Day to Day
- Official Ubuntu Book
- Organized Home
- PHP In a NutShell
- PHP Refactoring
- PHP5 CMS Framework Development
- PHP6 and MySQL Bible
- Responsive Web Design
- Responsive Web Design with HTML and CSS3
- Rules of Thumb
- Saleable Software
- Securing PHP Web Applications
- Seed Underground
- Simple and Usable Web, Mobile and Interaction Design
- Smart Organizing
- Submit Now: Designing Persuasive Web sites
- The Life-changing Magic of Tidying up
- Web site Usability
- Web Site Usability: A Designer's Guide
- Web Word Wizardy
- Work for Money, Design for Love
By Matthew Linderman, published in New York by New Riders in 2004.
Avoid reset buttons.
Adjust settings on server to allow for common typos and misspellings for URLs (for example ww instead of www). Setup wildcard domains (*.yourdomain.com).
Eliminate extraneous navigation elements during a multi-step process such as a checkout or registration. Avoid distracting the user.
Study customer support inquiries
Analyze server logs
Look outside for help
Put someone in charge
Build a contingency design knowledgebase (track issues and solutions)
Prepare to fail (admit things will go wrong)
Indicate availability immediately
If unavailable, provide a backup plan.
Notify by email when in stock
Plan for imperfect searchers
Study previous search results to identify problems
If search returns an avalanche of results, offer means of narrowing results.
If no results return, offer an easy way to expand results
Explain how search works, give examples and tips.
Indicate required fields with an asterisk and/or include the word 'required' or 'optional' next to each field.
Indicated required field titles in bold.
Provide formatting examples for data
Provide pulldowns or lists to ensure accurate data.
Offer contextual help right on the form.
Custom 404 Pages
Include the company's name and logo.
Include an explanation of why visitor is seeing the page
A list of common mistakes that explain the problem
Links back to home page and/or relevant pages
A search engine to help find right information
An email link for visitors to report errors/problems
Use tracking numbers as a reference
Provide a clear and accurate subject line
Explain what to do next if issue is unresolved
Sign the email.
Clearly state the error at the top of the page and the problem area that needs to be corrected.
Indicate problem are with bold red text
Draw attention to the problem with an alert icon or graphical cue
Offer possible solutions to the problem.
Do not force visitors to retype data correctly, accept alternative formats.
Accept all valid data and only ask for problem info (do not send them back to the same form).
Be consistent in all error messages.
Lead with a clear heading and the most important information
Offer bullet points not blocks of text
Use bold red text and color variations to highlight crucial information
Edit copy so that it is brief and meaningful.
These are notes I made after reading this book. See more book notes
Just to let you know, this page was last updated Wednesday, Mar 21 18