Rather than you needing to get involved during design I'd flip it and say get the designer involved during build stage, actually working on front-end code too. Pretty soon they'll be doing Rails-friendly design work, and they can see the holes in the design and plug them or modify the design as necessary. The longer you work with them in this way the better you'll get at collaborating and the easier things will be to integrate.
That's how I like to work with dev teams anyway, not just throwing designs over the fence. – tim On 24/11/2010, at 11:07 AM, dnagir wrote: > Hi, > > I am just wondering how you guys deal with working from having UI > design to the actual Rails implementation? > (e.g.: 37signals - Interface First) > > Sometimes we get the design of a web site from a "professional > designer" which (in 99.999%) of cases looks very nice and usable. > (And way better that I could possibly come up with). > > Unfortunately such designs often do not follow a lot of Rails > conventions (REST is ignored, Flash messages are not used, Validation > errors presented in an absolutely different way etc). > > This is often a barrier to using some Rails goodness (for example, > form builders - formtastic, simple_form). > > So I, as a developer, either have to change the design bits to fit > into the Rails conventions or try to live with the design as-is. > > Unfortunately I am pretty bad at UI design and prefer to trust the > designer. > > What are your opinions on that? > > > Thanks, > Dima. -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
