Designer role in ROR development......

I am just starting with rails or to be precise web development..... I
just want to know... wats the role of a designer in ROR development(the
guy who works on dreamweaver and stuff)....?? does the designer works
only on layouts and css or does he work on views after the project is
completed?

Probably varies from project to project but for us it's a bit of both. Our guy works the html and css directly rather than using something like dreamweaver (which might not understand erb templates)

Fred

As Fred said, it depends on the project.

We don't do the design as such, but get Photoshop graphics
or pdf files from designers our customers chose. We could do
some of it and for the admin views and other technical things
we make the technical design. But if it comes to colors, logos
and other parts visible to the users we prefer to work with
professional designers. Though we try to work as close with
them as possible, since some design questions may influence
our work or some ideas simply can't be done or would be
too much work.

We then implement the designs by writing the views, html & css.
Some of it I do myself, but for the more complicated cases I
ask one of my colleagues, who has a very deep knowledge
of those things.

I don't think it makes much sense, to have a programmer doing
visible design stuff or specialize on the view part of a project.

thanks folks..

  i understood that there is no best practice involved.... and probably
its best to work along with the designer when it comes to the views!

Tarakeshwar

I'd argue that it depends on the designer more so than the project. In
my opinion... if a designer isn't doing the HTML/CSS than their just a
graphics designer and shouldn't be part of the process of designing
web applications. They need to understand the limitations... the web
isn't like the print world... nor is it a jpg.

Anyhow... that's my very opinionated view on the topic. :wink:

Cheers,
Robby

I'd argue that it depends on the designer more so than the project. In
my opinion... if a designer isn't doing the HTML/CSS than their just a
graphics designer and shouldn't be part of the process of designing
web applications. They need to understand the limitations... the web
isn't like the print world... nor is it a jpg.

Anyhow... that's my very opinionated view on the topic. :wink:

Sure, right. But then you have a customer who got his logo
and letterhead and don't know what from that designer and
wants him to "design" the web site too...

Has never heard of html (or worse, thinks he knows something...)

So you must make that a mutual process of explaining him
some basics of user interface design, like that it's no good
idea to let the user enter some data on page one that influences
the information five pages later, or how to use (what is) checkboxes
radio buttons etc and why endusers expect a checkbox for
yes/no decisions instead of whatever the designer thinks more fancy...

But then: Nobody said it would be an easy job :smiley:

A web designer that don't know how to make a good user interface
design with also good knowledge of XHTML/CSS...well it's not a web
designer, a "other thing" deisgner maybe.
So, in this case, I don't want him to make part of the team too.