This library collects contract design patterns – repeatable solutions to commonly occurring contract usability problems.
Design patterns are principle-driven guidelines accompanied by practical examples of how the patterns have been implemented in real life.
Patterns and pattern libraries have been successfully used in areas varying from architecture to software engineering and UX design, as a means of communicating and sharing design knowledge. Why not use them in the context of contract design?
A design pattern is not a template or a finished design that can be copy-pasted. Instead, it gives you a model approach and examples to recognize a problem and develop an effective solution. A design pattern is not a strict method you must follow – you are free to adapt it to your (and your readers’) needs and contexts of use.
We know that you would just love a ready-made solution and a quick fix, but sorry, that’s not the way design works. Design is, at its core, a method for problem-solving in context. We give you good models for approaching problems, but you need to add your own contextual knowledge and goals to the mix to create meaningful solutions.
This library is about: |
This library is not about: |
|
|
< Previous: Why use this Library? Next: Who is this Library for? >