PatternAims

I'd like this site to be a tool to help us share good practice and inform the design of ecommerce stores.

• Many pattern languages, to me at least, suffer from documenting TheBleedingObvious, which gets in the way of sharing real ideas and knowledge about the domain area. So patterns like "Make The Checkout Process Easy To Use" are banned.
• Many pattern languages exist in a vacuum, in that they don't "plug into" other existing patterns, I hope this one ends being more "connected" building on the great work that has been done already.If you know of a related "external" pattern please add a link to it.
• Many pattern languages are not collaborative, not letting the readers ask a question or contribute an example or counter some claim. I really don't claim to know it all, please share what you know.
• Many patterns, in my opinion are too purist. I would love it if this pattern also contained anecdotal evidence to back up ideas. Often research into this area is so humerous that most businesses couldn't handle publishing it. So if you want to add "Forces" etc then please do, but I'd hate you to have to consider what the forces are. If you have a good idea, or find yourself explaining a core concept to clients again and again, add it to the wiki.
• I assume you probably already understand a lot about UserCentredDesign, although if not, don't worry, we will hopefully explain things as we go. This pattern isn't all about usability though because it takes more than usability to run an ecommerce store successfully.

Goals of the Pattern

• Well defined patterns
• Well chosen (and preferably humorous) names
• Example of each pattern
• Example where each pattern has not been applied (possible anti-patterns)

What I'd Like You To Do

Add comments, stories, screenshots, anecdotes, examples that either agree with, extend the ideas contained.

TomSmith