Developing a template for a Ruby on Rails view. What and where to study?

I have a project and I am in charge of front-end design whereas my developers will be working back-end with Ruby on Rails.

I don't know Ruby on Rails and am developing front-end using XHTML, CSS, jQuery, 960.gs CSS Framework. My developer has to take my design and connect back-end elements to it as well as Ajax.

What are the things I need to know when designing a template / view so that I don't hit my developers with my design? How to help connecting elements painlessly? I understand that I must avoid. Some Ruby on Rails developers also prefer the Blueprint CSS Framework over 960.gs.

Any guidance? Thanks.

+2


a source to share


2 answers


In general, the Rails templating system is quite flexible and will allow developers to create even complex projects. CSS structure shouldn't make that difference. However, if they are using Rails 2.x, it is much easier to use Prototype instead of jQuery. However, Rails 3.x is also independent of the javascript library.



A relatively good overview is the official guide . You can also try this tool for cutting your views and layouts .

+1


a source


I can speak from a developer's point of view.

What annoys me is overly complex css structures, as simple and abstract as you can.



Other things are naming classes and identifiers, in general, trying to figure out which models the developer is using and name their classes and identifiers accordingly. For instance. for a blog post: #posts .post

for a post in index view and #post

for a post in view view. I don't care what css framework the designer is using as long as it works. And finally, if you are developing different html pages, keep in mind that we often only have one or two layouts, for example. /views/layouts/application.html.erb

and we usually try to keep this number as low as possible.

jQuery finds was ever my preferred choice over its own rails prototype.

+1


a source







All Articles