This was a useful tutorial for designers once: http://glu.ttono.us/articles/2006/03/21/rails-for-designers
On 6/15/07, Rob Kaufman <[EMAIL PROTECTED]> wrote:
If you emphases is going to be on usability more than "fancy graphics or effects", then I would suggest going with a usability designer instead of a graphical designer. These fields are related, and there is a lot of bleed over, but someone with usability experience or training can often still give you an awesome look. The big thing you get from working with a usability specialist is a design that makes your website enjoyable to use. If you decide to go that route, expect any wire-frames you have to get tossed out and re-done (not that they don't still have worth by help you explain your core concepts). I've had success laying out a basic set of user stories and turning them over to the designer and I've had success with jotting down some basic concepts to help me explain what an app needs to do. You want to give your designer freedom to design, but you also want to inspire them by showing them clearly what you want to accomplish (you give what, they give how). Rob Kaufman On 6/14/07, Nathan Colgate Clark <[EMAIL PROTECTED]> wrote: > > Jesse James Garrett has nice guide for building solid foundations for websites. In his model, graphic design is the last step, and it is stacked on top of solid planning and information: > > http://www.jjg.net/elements/pdf/elements.pdf > > > > _______________________________________________ Sdruby mailing list [email protected] http://lists.sdruby.com/mailman/listinfo/sdruby
-- Kevin Clark http://glu.ttono.us _______________________________________________ Sdruby mailing list [email protected] http://lists.sdruby.com/mailman/listinfo/sdruby
