> > The guys in the office <3 it, but we have three rare people that are > designers that can code (like really well), so it’s perfect for them. > > If you are working with frontend devs that have a decent grasp of > programming it would work. If you are working with designers that do > frontend, it probably won’t work. > You've hit the nail on the head IMO. If your designers can code and aren't afraid of some if statements etc in the code and like HAML, then it's win win win for everybody. Give your designers access to the repo, and let them have at your views directly. That is the best.
If your designers aren't comfortable, go HTML across the board I personally never use SASS btw. Too many great tools like firebug, CSSEdit, etc that let me do so much of the CSS work quickly and easily that SASS just gets in the way. It's a nice idea though. I'd love to see some editor support for it. --~--~---------~--~----~------------~-------~--~----~ 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 rails-oceania@googlegroups.com To unsubscribe from this group, send email to rails-oceania+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~----------~----~----~----~------~----~------~--~---
