Agenda
- Discussion questions
- MISSION STATEMENT
- At http://wiki.fluidproject.org/display/fluid/Design+Patterns+Library+Proposal, our proposed goal reads: "The primary goal of the design pattern library will be to introduce design patterns as a way to design usable, high-quality user interfaces in specific contexts ("a proven solution to a common problem in a specified context"). The library will have a practical focus, intended mostly as a tool for junior/new designers as well as developers. It will not focus on creating a complete pattern language, or describing patterns in a more academic sense." Is this the best statement of our goal? Can we add to this and flesh it out more?
- DESIGN GOALS - AUDIENCES
- The OSDPL is a setting down of a portion of the body of knowledge that expresses the principles of good design. As such, it should serve as a reference work, as well as a repository for study. The library will be targeted towards a diverse set of audiences, including:
- MISSION STATEMENT
Junior designers & designers who are new to the communities - they will likely both want to peruse the library to learn best practices as well as look for specific design solutions to problems.
Developers who need to design the UIs they build - will most likely be looking for specific design solutions to problems, want more concrete solutions, and even code samples, pattern comparisons, demos, or components related to the pattern.
Experienced designers - will probably browse the pattern library for inspiration, or to come up with innovative solutions to complicated problems.
Pattern Authors, which may fall into any of the 3 categories above.
We will design the library for two primary audiences, meaning each of them will have their own interface (in this case, their own form of the pattern):
Pattern Users: Junior Designers (who may want fairly deep explanations of patterns)
Pattern Users: Developers (who may want more succinct patterns and code examples)
Pattern Authors
We expect there will be some secondary audiences as well (meaning design will not be focused on them, but their needs should be covered in the interface which addresses the primary audiences' needs, perhaps with just a few additional enhancements):
Experienced Designers (should be covered by Junior Designers' interface)
As mentioned above, although Pattern Authors may fall into either the designer or developer category, they will have a completely separate interface to add and edit patterns (which others who are simply users of the library will never see). We believe designers and developers will have slightly different needs as users of the patterns. This could be as simple as presenting the full version of the pattern to designers and a more "stripped-down" version to developers. We believe designers will want to understand why a pattern is the right pattern, who else has used it, what other design considerations they need to think about when using the pattern, etc. They will want interaction consistency with some flexibility for innovation and different contexts. Developers may just want to "cut to the chase," "just tell me how to solve this interaction problem" or "tell me how to implement this solution, don't give me a bunch of different options;" in other words, they may prefer a much more prescriptive style. Developers will likely also want to have code examples or actual code to use. Additionally, the 2 disciplines' search strategies may also be quite different from one another. We'd like to confirm all of these assumptions in the future by doing user interviews/research.
- How should we update patterns as we come up with more information? Review by this group, or just update? (http://issues.fluidproject.org/browse/FLUID-3310)
- Sign up for work